Subject:File opening problem

Posted by: Tripwire

Date:9/4/2002 12:10:53 PM

If I save a new Acid 4.0 project when I try and open it by clicking on it in the folder I have saved it to, it won't open, I get an error message saying
'The file could not be opened. Make sure the file exists and that you have access to the file/folder.'

If I open Acid first then open the project using the open command it loads fine?

What gives?

Subject:RE: File opening problem

Reply by: SonyNateM

Date:9/4/2002 12:15:04 PM

Tripwire,

It sounds like Windows is giving you trouble, or handling the filetype improperly. I would try using the Repair function in ACID's entry in the Add/Remove Programs control panel, or perhaps removing and reinstalling ACID clean.

HTH,
Nate

Subject:RE: File opening problem

Reply by: Tripwire

Date:9/4/2002 12:40:32 PM

Hi Natem,

thanks yes you were right their was a file association problem probably caused by installing 4.0 without removing 3.0 I re-installed and the problems has gone away :)

While I have your attention could I ask you to read this thread:

http://www.sonicfoundry.com/forums/ShowMessage.asp?MessageID=119365&Replies=13&Page=3

I have been in contact with my sound card manufacturer and they say it must be an issue with your software not their usb interface which has withstood extensive testing with the likes of cubase/sonar etc etc..

What now will there be a fix?

Thanks

Subject:RE: File opening problem

Reply by: SonyNateM

Date:9/4/2002 1:51:25 PM

Not within one of my areas of expertise, unfortunately, but I will forward the link to our development team.

Subject:RE: File opening problem

Reply by: Iacobus

Date:9/4/2002 2:07:13 PM

Hi Tripwire,

I have an M-Audio USB Duo, which can do 24-bit/96 kHz max. WDM drivers are not a problem when using it in conjunction with ACID Pro 4.0. When using the ASIO drivers, I can use 24-bit/96 kHz up until the project gets really busy, which I'll then get some popping and clicking but nothing life stopping. Dropping the project down to 16-bit/44.1 kHz clears the problem up. Can you use the same resolution and sample rate or is it any resolution/sample rate this happens to you?

I want to say it's a driver issue, as I can use ASIO but in a limited way. I've heard but can't confirm that ACID 4.0 utilizes ASIO in a way the other apps don't, thereby exposing a new problem for audio interface manufacturers. Look at the Delta ASIO driver issue and ACID 4.0. M-Audio confirmed it was their fault and are working on a new set to fix the issue.

In a related issue, I've since completely graduated to ACID Pro 4.0 and have uninstalled ACID Pro 3.0. Since then, I've noticed I don't have that much trouble with Delta ASIO drivers anymore. (I have an M-Audio Audiophile 2496 as well.) I get the occasional "you should save your work" message but that's about it thus far. Has anyone else in the same boat tried this? Have yet to try ASIO with VSTi and recording MIDI though.

Iacobus

Subject:RE: File opening problem

Reply by: Tripwire

Date:9/5/2002 4:03:00 AM

Iacobus,

at 24-bit/96 kHz and my latency at the maximum of 19ms it is horrendous!! Simply Unlistenable! Since upgrading to 4.0 I have also added 128mb of ram taking the total upto 256mb but this had made no noticable difference. The default track still only says its using 11mb of ram. I have also tryed the 48KHz setting and that too is unusable with the ASIO setting. At 44.1KHz it plays fine with 19ms latency up until 12.1 on the timescale where theres that weird fill (On the default Hybrid track that is) If I Set the drivers back to WDM it plays fine.
Like I said in the thread mentioned above the reason I upgraded was to gain the use of the vsti's and midi functionality but at present this just ain't workable, with my usb interface. I guess I'll just have to wait and see if it gets fixed in the next update, because my sound card maufacturer ain't excepting any responsibilty at present :( I am inclined to agree with them though if there product was tested with and is proved to work reliably with the likes of Cubase, Sonar, Cakewalk etc then why should it be any different with Acid? If Sonic Foundry are using a different method of communicating with the sound card, using ASIO, and its causing problems then why not just ditch that method and use the standard way that works? Thats what the end user wants at the end of the day, a working system so they can concentrate on writing music.

Steve.