Community Forums Archive

Go Back

Subject:acid bug
Posted by: mr_williams
Date:1/12/2004 11:22:15 AM

i found a bug in acid and im able to reproduce it all the time. when you try to record a new midi track (the record window is set on audio initially), switch to midi and it will crash if the midi file already exists. it does crash very badly on my machine, this time i got even a bluescreen. i found this bug already in older versions so now is the time to report it ;-)

OS: XP
Music: Pulsar

Subject:RE: acid bug
Reply by: Iacobus
Date:1/12/2004 11:26:30 AM

I'm trying to reproduce this but can't seem to get it to crash. The dialog just keeps telling me that a MIDI file with the same name already exists and to choose a new name.

Could it be the MIDI drivers relating to your audio interface? (A blue screen is indicative of a device driver failure.) Have you tried other drivers?

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: acid bug
Reply by: mr_williams
Date:1/12/2004 12:03:57 PM

thanks for the reply..

there arent other drivers for my card.. unfortunately. i got pulsar 1 with newest software and drivers installed - sfp v3.1c

today it even reportet me an error in rewire - i dont even use that feature. sometimes it just messes up my asio drivers and mostly i need to reboot to get it working again. the really strange thing is, that i dont even start to record.. it throws an exeption just in the record dialog ehwn switching to midi radiobutton. heres the exeption:


Sony ACID Pro 4.0
Version 4.0f (Build 446)
Exception 0xC0000005 (access violation) READ:0x6E206120 IP:0x6E206120
In Module 'acid40.exe' at Address 0x0 + 0x6E206120
Thread: GUI ID=0x650 Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=6e206120 EFLGS=00010216
EBX=00000000 SS=0023 ESP=0012f9cc EBP=00000000
ECX=00000001 DS=0023 ESI=000801d0 FS=0038
EDX=7ffe0304 ES=0023 EDI=00000001 GS=0000
Bytes at CS:EIP:
6E206120: .. .. .. .. .. .. .. .. ........
6E206128: .. .. .. .. .. .. .. .. ........
Stack Dump:
0012F9CC: 00000000
0012F9D0: 00070308 00030000 + 40308
0012F9D4: 01FC14A8 01F30000 + 914A8
0012F9D8: 00000000
0012F9DC: 00000000
0012F9E0: 00000000
0012F9E4: 00000000
0012F9E8: 01FC14A8 01F30000 + 914A8
0012F9EC: 00000001
0012F9F0: 0144C0C8 013F0000 + 5C0C8
0012F9F4: 00000003
0012F9F8: 005F7CCD 00400000 + 1F7CCD (acid40.exe)
0012F9FC: 000801D0 00030000 + 501D0
0012FA00: 00000001
0012FA04: 0012FBD4 00030000 + FFBD4
0012FA08: 005F7700 00400000 + 1F7700 (acid40.exe)
> 0012FA1C: 010989A1 01000000 + 989A1 (acid40k.dll)
0012FA20: 00000400
0012FA24: 00000000
0012FA28: 0012FCD8 00030000 + FFCD8
0012FA2C: 00000005
> 0012FA30: 77E56111 77E40000 + 16111 (kernel32.dll)
> 0012FA38: 77E564AB 77E40000 + 164AB (kernel32.dll)
> 0012FA3C: 00657590 00400000 + 257590 (acid40.exe)
0012FA40: 0012FA34 00030000 + FFA34
> 0012FA44: 0120C094 01000000 + 20C094 (acid40k.dll)
0012FA48: 0012FF0C 00030000 + FFF0C
> 0012FA4C: 77E74809 77E40000 + 34809 (kernel32.dll)
> 0012FA50: 77E632A0 77E40000 + 232A0 (kernel32.dll)
0012FA54: FFFFFFFF
> 0012FA58: 005F7700 00400000 + 1F7700 (acid40.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 005F356A 00400000 + 1F356A (acid40.exe)
0012FFFC: 00000000



after that it reports:

ReWireDLL
D:\projects\ReWire\ReWireDLL\Portable\ReWireDLL.cpp(994) : VERIFY failure

Subject:RE: acid bug
Reply by: Iacobus
Date:1/12/2004 12:25:01 PM

If anything, have you tried uninstalling and then reinstalling ACID?

A kernel32.dll error could be caused by anything. Is anything else running in the background other than ACID?

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: acid bug
Reply by: mr_williams
Date:1/12/2004 12:43:15 PM

i had this error on win2k already and with older versions of acid. so yes i did reinstall.. even my computer since i saw this bug the first time. it doesnt matter what im running in the background.. usually just nothing. maybe its caused by the drivers, but it makes no sense for me that it crashes just when i should select the name.

btw: it does report the message about the existing file.. but when i click ok, the exeption occures.

Subject:RE: acid bug
Reply by: Iacobus
Date:1/13/2004 2:00:25 PM

I do believe a blue screen is caused by a device driver failure of some sort.

Is there any info on the blue screen? And what's your soundcard and video card? (Try different drivers for each if possible; be sure to follow instructions for uninstalling older drivers before installing new ones.)

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: acid bug
Reply by: pwppch
Date:1/13/2004 7:48:11 PM

What does the Blue screen say?

In general, an app can't cause a blue screen unless the app has installed a kernel level device or service driver.

Peter

Subject:RE: acid bug
Reply by: mr_williams
Date:1/14/2004 12:11:43 PM

i have latest drivers for my audio and gfx card. my audio card is pulsar 1 and there arent newer drivers for it. my gfx card is a msi geforce 4 with latest drivers, i did change them recently.

unfortunately i cannot tell what the bluescreen does say. in fact it happens as follows: i change from audio to midi in record dialog and then the error appears which i pasted above. acid.exe crashes, sometimes it just hangs and i can kill it with taskmanager. until that point there isnt a bluescreen. but if i do something after all that (like klick on a link in this forum) the bluescreen appears.. just for a very short time and then my pc reboots. ;-(

Subject:RE: acid bug
Reply by: Iacobus
Date:1/14/2004 12:50:57 PM

Hi again mr_w,

Did this happen just recently, after you installed the newer GeForce drivers?

Try also reducing or turning off video acceleration to see if that helps any.

To prevent XP from rebooting on you after a crash: Hit the Windows logo key+Pause/Break on your keyboard. Click the Advanced tab. Under "Startup and Recovery", click the Settings button and uncheck the "automatically restart" option under "system failure".

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: acid bug (me, too)
Reply by: gunhed
Date:1/16/2004 9:22:24 AM

You're not the only one...

This is a bug I have also noticed ever since Acid Pro 4.0a. On the Record panel, If a file already exists (like "Record Take 1"), and I switch from MIDI to Audio or vicea versa, I will get an exception and Acid will crash. The fix for me (after restarting) is to change the filename in the dialoge box before swtching.

It can be pretty annoying sometimes, because I can't always know if a file already has that name, and I sometimes loose work because my changes weren't saved before the crash. Also, it would seem to me the "take number" updating routine should be more intelligent when picking a new filename (it doesn't always choose a number that's unique based on what's in the currently browsed directory). It interferes with the flow of creativity and trying to nail down that vocal or MIDI recording.

More checking should be done to prevent a crash or popping up a message "File already exists." It ought to increment the take number until there's a unique filename instead of complaining. Of course, if the default filename "Record Take x" has been changed, then it should not attempt to increment, and, instead go ahead and give the "File exists" warning.

Subject:RE: acid bug (me, too)
Reply by: Iacobus
Date:1/16/2004 1:06:29 PM

In any case, do you get a blue screen like mr_williams does? Do you have the same audio interface and OS?

Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: acid bug (me, too)
Reply by: mr_williams
Date:1/18/2004 12:37:54 PM

hm gunhead, please post your os and audio/video card.

i didnt get a bluescreen in earlier versions. also i never faced it on win2k system. this behavior is kinda new, i think since the swich to sony version.

but i totally agree with gunheads suggestions, that is exactly what i think. ;-)

Subject:RE: acid bug
Reply by: MacMoney
Date:1/18/2004 4:18:29 PM

Same here, not able to reproduce on XP and MOTU or Digi hardware.

Sorry, George Ware

Go Back