Community Forums Archive

Go Back

Subject:Acid 7.0c Playback Problem
Posted by: Kit
Date:11/11/2009 5:49:09 AM

I select three or four some files in Explorer right-click and open them in SoundForge. I run a script on the files in SoundForge to convert the files to oneshot. I close SoundForge. At this point Acid won't preview files in Explorer and won't play on the main time line. I'm forced to close and reopen Acid to get it to play and audition tracks properly. Is this a know bug?

Thanks,

Kit

Subject:RE: Acid 7.0c Playback Problem
Reply by: pwppch
Date:11/11/2009 10:10:21 AM

Please fill our your system specs in your user profile and expose them

It sounds like a driver contention issue, but until I know what hardware and driver model you are using in ACID and Sound Forge, I can't do anything but guess.

What version of Forge are you using?

Do you get any error msgs when playback does not start?

Are you using ASIO? Mapper? Wave Classic driver mode in ACID/Forge?

What audio hardware are you using?

Peter

Subject:RE: Acid 7.0c Playback Problem
Reply by: Kit
Date:11/11/2009 4:31:04 PM

Thanks for the reply. I have SoundForge 10a though Acid was opening up SoundForge 8d despite having the checkbox to identify latest software ticked. I manually added SoundForge 10a as another audio editor and tried that - got the same result.

Currently I don't have a separate sound card installed. I'm using the onboard sound that came with the motherboard - a Gigabyte P35-DS3R. But Acid is set to use an external Roland UA-100 box. As an experiment I switched the audio device to Microsoft Sound Mapper and after closing and reopening Acid tried again. I still lost playback. I have discovered that if I select just one file and open SoundForge (either version) and run the script to convert it to a one shot sound and playback are fine. The problem only occurs if I select more than one file.

I've exposed my system specs. I don't get an error messages.

Thanks again,

Kit

Subject:RE: Acid 7.0c Playback Problem
Reply by: pwppch
Date:11/11/2009 8:08:50 PM

I have reproduced the problem.

This is caused by opening multiple files from the explorer as you discovered. There is no workaround other than to open one file at a time.

I have entered into our bug tracking system.

Thanks
Peter

Go Back