Subject:HELP! Acid update results in Sound Forge problems!

Posted by: drbam

Date:5/14/2007 3:24:38 PM

Last nite, with encouragement from jr, I updated Acid Pro 6.0a to 6.0d. It seemed to work fine so I continued working on the project mixes I'm doing and in my haste and foolishness, I trusted that it would be fine to save the existing projects in 6.0d. However, now I discover that when I try to open SF8.0d from within AP6, and attempt playback of SF8 I get an error saying that my audio output channels Layla 24 1&2 don't exist. If I open SF8 by itself and try to play a file, an error stating that the sample or bit rate isn't supported. If I then change the driver to classic wave from ASIO (or vice versa) I get a full on crash of SF8 with the dump data below. Now I'm in a real bind because I have no way of editing my files and I'm in the middle of mixing an entire project! I uninstalled/reinstalled SF8 and it worked until I opened AP6 and the errors/crashes began again. Also, I can't get SF7 to work either so right now I'm pretty screwed until this is sorted out.

Sony Sound Forge 8.0
Version 8.0d (Build 128)
Exception 0xC0000005 (access violation) READ:0x102398 IP:0x1023B0AE
In Module 'forgek.dll' at Address 0x10000000 + 0x23B0AE
Thread: GUI ID=0xDA0 Stack=0x12E000-0x130000
Registers:
EAX=00000003 CS=001b EIP=1023b0ae EFLGS=00210206
EBX=00000000 SS=0023 ESP=0012e2d0 EBP=00000000
ECX=00102398 DS=0023 ESI=001d1060 FS=003b
EDX=00000001 ES=0023 EDI=001d27d8 GS=0000
Bytes at CS:EIP:
1023B0AE: 8B 11 50 8D 86 3C 07 00 ..P..<..
1023B0B6: 00 50 56 FF 92 40 01 00 .PV..@..
Stack Dump:
0012E2D0: 00000000
0012E2D4: 001C2518 00140000 + 82518
0012E2D8: 00000000
0012E2DC: 00000000
0012E2E0: 00000001
0012E2E4: 00000001
0012E2E8: 7C839AA8 7C800000 + 39AA8 (kernel32.dll)
0012E2EC: 7C80FCD8 7C800000 + FCD8 (kernel32.dll)
0012E2F0: FFFFFFFF
0012E2F4: 7C80FCCF 7C800000 + FCCF (kernel32.dll)
0012E2F8: 1023AA31 10000000 + 23AA31 (forgek.dll)
0012E2FC: 00000000
0012E300: 00000000
0012E304: 00000000
0012E308: 001C2518 00140000 + 82518
0012E30C: 00000000
> 0012E314: 10224CC3 10000000 + 224CC3 (forgek.dll)
0012E318: 001C2518 00140000 + 82518
> 0012E31C: 1023B5CF 10000000 + 23B5CF (forgek.dll)
0012E320: 00000000
0012E324: 00000000
0012E328: 001C2518 00140000 + 82518
0012E32C: 00000000
> 0012E338: 10229AE9 10000000 + 229AE9 (forgek.dll)
0012E33C: 00000000
0012E340: 80004002
> 0012E344: 77D4BF58 77D40000 + BF58 (USER32.dll)
> 0012E348: 10229CA3 10000000 + 229CA3 (forgek.dll)
> 0012E34C: 00562869 00400000 + 162869 (Forge80.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 005A0BC8 00400000 + 1A0BC8 (Forge80.exe)
0012FFFC: 00000000

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: drbam

Date:5/14/2007 4:55:44 PM

Update: I uninstalled/reinstalled Echo Audio drivers - no change.

Update 2: Uninstalled/reinstalled AP6.0d - no change. Uninstalled AP6.0d and reinstalled 6.0a - back to normal except that I'll need to rebuild this current mix and have lost about 4 hrs trying to resolve this frustrating BS!

Does someone have any clue what this might be? Thanks!

Edit: Thankfully I discovered that I did not have to rebuild the mix. Backwards incompatibility apparently only applies to versions - not updates. At least I learned something positive about Acid 6 during this fiasco.

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: Iacobus

Date:5/15/2007 12:13:55 PM

Not sure what caused things to go kablooey. Did you try installing using only the updates (rather than updating your existing install)?

Iacobus

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: drbam

Date:5/15/2007 1:12:17 PM

"Did you try installing using only the updates (rather than updating your existing install)?"

I'm not exactly sure what you're asking but if you mean did I try installing 6.0d by itself then the answer is yes. During this process I uninstalled 6.0d and then reinstalled it. No other version of AP6 was installed at that point (although I did/do have AP5 installed, which I haven't used in over a year). The only thing that allows me to use Sound Forge is to stay with AP6.0a and so that's where I'm at.

Thanks

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: Iacobus

Date:5/16/2007 11:03:32 AM

Yes, that's what I meant. (The "update" can actually act as a full install, provided you have your serial key handy.)

Don't really know what's up. If you don't have any really big issues with 6.0a right now, finish the project then do some experimenting. (Did you try ACID Pro 6.0d and Sound Forge 8.0d on another system?)

I was having this really odd problem with Sound Forge 9 not being able to open MPEGs (though Sound Forge 8 could do so with no problems). The only thing that fixed it? A system format. (Not suggesting you do the same, but sometimes the harshest brute force methods are the only solution.)

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: drbam

Date:5/16/2007 3:15:00 PM

Thanks mD. No I haven't experimented on a different system. I just need to stay focused on getting this project completed. Screwing around with software glitches is the worst kind of groove buster and totally pulls the rug out from the creative juices for me. Since no one from Sony has replied to this here, today I sent a formal message to tech support - it will be interesting to see what their reply is. Frankly, if I had to reformat my system drive to resolve this, it'd probably be the final straw that moves me into giving Reaper a full-on trial. My system is lean, custom made and dedicated to my studio. I NEVER install anything that hasn't been tested on my secondary system (except for AP6.0d) so having to reformat the drive is beyond extreme IMO. I can see how your situation is different however, given that you're using SF9. I don't install any new versions of Sony apps (or anyone else's) until the "public beta" is over, meaning that I wait until at least until the 2nd or 3rd update is posted.

Thanks again for your input and support - I do appreciate it.

Subject:RE: HELP! Acid update results in Sound Forge problems!

Reply by: Iacobus

Date:5/23/2007 12:25:34 PM

Take note that my situation was unique—I couldn't find anyone else that was having the same exact problem as I had. Everyone else could open MPEGs just fine with Sound Forge 9.

So the problem was wholly mine. As draconian as I am with my system, the problem was most likely caused by me somewhere along the way (or by the OS). As I noted, the problem went away with a system format, so there was something definitely there that Sound Forge 9 wasn't kosher with—what it exactly was I have no idea. Just the nature of the digital beast, I guess.