Subject:frequent exceptions in ACID Pro 6

Posted by: pmm

Date:7/26/2006 10:26:10 PM

I am getting frequent exceptions in ACID Pro 6.

The dialogue says .\Portable\ReWireDLL.cpp(895): VERIFY failure.

I think I'm a little too new to ACID to understand what is happening, but it seems like I didn't see this nearly as much before I started using CakeWalk's Rapture with ACID.

Used to, a cold boot solved the problem, but not lately.

And even when things are working okay, I can only get 3 instances of Rapture going. Trying to insert a 4th results in a crash.

I can't imagine either is a memory problem, though. I have oodles of it, almost more than Windows XP32 generally knows what to do with, i.e., 4G.

Any advice or ideas?

Oh, and if this is strictly a Rapture issue, feel free to say so and I will go and ask there. Don't want to be a bother. Thanks.

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pwppch

Date:7/27/2006 10:48:23 AM

Are you using the 6.0a update?

What version of Rapture are you using?


Note:
The ReWire.DLL.cpp warning is misleading. This message is produced by the ReWire system dll provided by Propellerheads and indicates that something has failed in the host app (ACID) that uses the ReWire system. It does not indicate a problem related to ReWire.


Peter

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pmm

Date:7/27/2006 10:41:48 PM

Yes. I am using the 6.0a update.

As for Rapture, I thought there was only one version for WinXP. Is that not right? In any case, the rapture.dll says the version # is 1, 0, 0, 80

This exception is getting to be extremely frequent.

By the way, I also recently installed Emulator X2, which appears to be completely incompatible with ACID. It just locks up when I try to load it. And it has some other problems, too. Don't know if this could have anything to do with it or not, but I have essentially invested a small fortune now in audio hardware and software that hardly works at all. Very frustrating.

Hope you can help at least a little bit.

The full details of the latest exception incident follow:

Sony ACID Pro 6.0
Version 6.0a (Build 263)
Exception 0xC0000005 (access violation) READ:0x2B776D28 IP:0x2B776D28
In Module 'acid60.exe' at Address 0x0 + 0x2B776D28
Thread: GUI ID=0x10C Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=2b776d28 EFLGS=00010202
EBX=000104b2 SS=0023 ESP=0012f370 EBP=0012f3b8
ECX=0012f414 DS=0023 ESI=01705f50 FS=003b
EDX=2e296270 ES=0023 EDI=000104ae GS=0000
Bytes at CS:EIP:
2B776D28: .. .. .. .. .. .. .. .. ........
2B776D30: .. .. .. .. .. .. .. .. ........
Stack Dump:
0012F370: 00010400 00010000 + 400
0012F374: 01705F50 01580000 + 185F50
0012F378: 38212EB0 38210000 + 2EB0 (sfvstisynth.dll)
0012F37C: 000104AE 00010000 + 4AE
0012F380: 01705F50 01580000 + 185F50
0012F384: 01705F50 01580000 + 185F50
0012F388: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
0012F38C: 00000000
0012F390: 77D48734 77D40000 + 8734 (USER32.dll)
0012F394: 000104AE 00010000 + 4AE
0012F398: 00000110
0012F39C: 000104B2 00010000 + 4B2
0012F3A0: 01705F50 01580000 + 185F50
0012F3A4: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
0012F3A8: DCBAABCD
0012F3AC: 000104B2 00010000 + 4B2
> 0012F3B4: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F3BC: 77D545E4 77D40000 + 145E4 (USER32.dll)
> 0012F3C0: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F418: 77D70467 77D40000 + 30467 (USER32.dll)
> 0012F41C: 77D541B0 77D40000 + 141B0 (USER32.dll)
> 0012F428: 77D53FD9 77D40000 + 13FD9 (USER32.dll)
> 0012F430: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F450: 77D541E2 77D40000 + 141E2 (USER32.dll)
> 0012F460: 77D484FC 77D40000 + 84FC (USER32.dll)
> 0012F464: 77D485A4 77D40000 + 85A4 (USER32.dll)
> 0012F470: 77D54204 77D40000 + 14204 (USER32.dll)
> 0012F48C: 77D48734 77D40000 + 8734 (USER32.dll)
> 0012F4A0: 77D541E2 77D40000 + 141E2 (USER32.dll)
> 0012F4B0: 77D541E2 77D40000 + 141E2 (USER32.dll)
> 0012F4B8: 77D48816 77D40000 + 8816 (USER32.dll)
> 0012F4BC: 77D541E2 77D40000 + 141E2 (USER32.dll)
> 0012F4F4: 77D70467 77D40000 + 30467 (USER32.dll)
> 0012F510: 77D70467 77D40000 + 30467 (USER32.dll)
> 0012F514: 77D48830 77D40000 + 8830 (USER32.dll)
> 0012F520: 77D4B89B 77D40000 + B89B (USER32.dll)
> 0012F528: 77D541E2 77D40000 + 141E2 (USER32.dll)
> 0012F54C: 3837A684 38210000 + 16A684 (sfvstisynth.dll)
> 0012F55C: 77D54E28 77D40000 + 14E28 (USER32.dll)
> 0012F574: 3837A590 38210000 + 16A590 (sfvstisynth.dll)
> 0012F57C: 38210000 38210000 + 0 (sfvstisynth.dll)
> 0012F590: 38379000 38210000 + 169000 (sfvstisynth.dll)
> 0012F598: 38210000 38210000 + 0 (sfvstisynth.dll)
> 0012F5A4: 3837A680 38210000 + 16A680 (sfvstisynth.dll)
> 0012F5AC: 38210000 38210000 + 0 (sfvstisynth.dll)
> 0012F5D4: 3837A682 38210000 + 16A682 (sfvstisynth.dll)
> 0012F608: 3837012B 38210000 + 16012B (sfvstisynth.dll)
> 0012F614: 77D5514C 77D40000 + 1514C (USER32.dll)
> 0012F628: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F638: 77D58537 77D40000 + 18537 (USER32.dll)
> 0012F63C: 38210000 38210000 + 0 (sfvstisynth.dll)
> 0012F640: 3837A590 38210000 + 16A590 (sfvstisynth.dll)
> 0012F648: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F65C: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F664: 38228423 38210000 + 18423 (sfvstisynth.dll)
> 0012F668: 38210000 38210000 + 0 (sfvstisynth.dll)
> 0012F674: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F68C: 3821CAE7 38210000 + CAE7 (sfvstisynth.dll)
> 0012F69C: 38212D50 38210000 + 2D50 (sfvstisynth.dll)
> 0012F6B4: 004B2B6E 00400000 + B2B6E (acid60.exe)
> 0012F6B8: 004B2B85 00400000 + B2B85 (acid60.exe)
0012F6BC: 01705F50 01580000 + 185F50
0012F6C0: 077A6AA8 07690000 + 116AA8
0012F6C4: 027B4A98 02710000 + A4A98
0012F6C8: 01668FA0 01580000 + E8FA0
> 0012F6E4: 310C258F 30EC0000 + 20258F (acid60k.dll)
> 0012F6E8: 004B2FC8 00400000 + B2FC8 (acid60.exe)
0012F6EC: 0779BE00 07690000 + 10BE00
0012F6F0: 00000000
0012F6F4: 00000001
0012F6F8: FFFFFFFF
> 0012F7F0: 004B308F 00400000 + B308F (acid60.exe)
0012F7F4: 00000001

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pwppch

Date:7/28/2006 3:47:46 PM

>>As for Rapture, I thought there was only one version for WinXP. Is that not right? In any case, the rapture.dll says the version # is 1, 0, 0, 80<<

I don't know, I am not an expert of all VST Instruments that exist and we don't have Rapture in house. I just wanted to know which version you are using.


I have EmulatorX V1 and 2. There are known problems with these, and EMU is aware of them. I don't know if they have released an update to either yet. Generally they work, but the don't permit saving of their state in ACID, which makes them pretty much useless. I will contact them again, but you may also want to contact their tech support.

What do you mean by:

"And it has some other problems, too"

If it locks up when you try to load it - I assume that by load you mean to add it to your ACID project - then how can it have other problems if it locks up?

Thanks,
Peter

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pwppch

Date:7/28/2006 7:02:58 PM

I have installed an tried the Rapture Demo. It is not causing any problems for me at all.

Can you provide some specifics on what you are doing to cause any problem to occur.

The more detailed and step-by-step your description is, the better I will be able to help.

Have you contacted Cakewalk with this issue?

Peter

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pmm

Date:7/29/2006 8:52:43 PM

Hello again.

I did not have any troubles with Rapture at first. What I am seeing now is that I have a project with 3 MIDI tracks and 3 instances of Rapture, and another with 2 MIDI tracks and instances that have given me troubles. The former, with 3, always throws this exception now when I try to load/show the window for the 1st Rapture instance for one of the tracks. It does not do this with the other 2 tracks, but it does throw the same exception from time to time when I try to do something else, like assign a different sound program to one of the other Rapture instances. For a good little while, it did not do this all the time, but it has lately been doing it nearly every time.

As for the one with the 2 tracks, it too has given me this exception, again seemingly related to Rapture, but more randomly and not as often.

I have also seen this exception when first loading projects with one or more Rapture tracks -- and not just with the 2 above-mentioned projects. But this again seems more random, very unpredictable, and after a reboot, I can usually load these projects and do okay.

As for Emulator X2, what I meant was that there are 2 versions. It has now locked up on me as a VSTi about 50% of the time so far. When I wrote what I wrote, it had just locked up on me the first time I had tried to use the VSTi version, and I had just had other and similar troubles with the stand-alone version. But I had just got it, so it was too early I suppose to make such a harsh judgment, which is clearly what I did. Nevertheless, as a stand-alone, it has also locked up on me, a time or two when first loading the stand-alone program, but not usually. There is also a specific problem if I try to use the (can't think of the name right now, but the middle tree tab) explorer like thing and click on 'My Computer.' Any time I do that, I lose the video sync with my monitor permanently and the system becomes useless and I have to reboot. I am referring here to the stand-alone version; I have not even tried this in the VSTi version. EMU says this is a specific problem to my system that they have not seen elsewhere. Their techs are looking at my system specifications and have assured me they are working on it and will try to get back to me sometime soon, so . . .

As for contacting Cakewalk about my trouble with Rapture I have not yet done so. As Rapture worked so well for me at the outset, and as EMU seems convinced there is something specifically unusual about my system that may be causing some troubles with their product, I wanted to get opinions here first.

Subject:RE: frequent exceptions in ACID Pro 6

Reply by: pmm

Date:8/2/2006 2:20:48 AM

The problem has *not* gone away.

Brand new project. Dragged a few wav sample files from the browser and painted to create a few tracks. Inserted a MIDI track with Rapture as synth. Did not actually record anything. Just a little testing. Closed the Rapture window. When tried to re-open it by double clicking on the 1 icon, ACID 6a threw the aforementioned exception.

Not happening to anyone else, eh?

Looks like not much more help here. Guess I'll go talk to Cakewalk now. Or maybe try reinstalling everything. Ugh.