Subject:Acid Pro 6a crash logs for devs

Posted by: riley4reason

Date:7/28/2006 6:00:53 AM

Maybe this should be a sticky and it could help the developers troubleshoot what causes AP6 to crash and get fixes out sooner or post work arounds.

I have just started using it and it crashes allot.

I just tried to drag a midi file to an existing track and got this crash error.

Sony ACID Pro 6.0
Version 6.0a (Build 263)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x7C350428
In Module 'MSVCR71.dll' at Address 0x7C340000 + 0x10428
Thread: GUI ID=0xFF0 Stack=0x12D000-0x130000
Registers:
EAX=000000c4 CS=001b EIP=7c350428 EFLGS=00210202
EBX=7c35043c SS=0023 ESP=0012db20 EBP=00000000
ECX=0012df6c DS=0023 ESI=001ea3b8 FS=003b
EDX=00000000 ES=0023 EDI=7c350420 GS=0000
Bytes at CS:EIP:
7C350428: 66 8B 02 66 89 01 41 41 f..f..AA
7C350430: 42 42 66 85 C0 75 F1 8B BBf..u..
Stack Dump:
0012DB20: 0057EAD2 00400000 + 17EAD2 (acid60.exe)
0012DB24: 0012DF6C 00030000 + FDF6C
0012DB28: 00000000
0012DB2C: 00000000
0012DB30: 041CC210 03FE0000 + 1EC210
0012DB34: 001EA3B8 00140000 + AA3B8
0012DB38: 00000024
0012DB3C: 00000001
0012DB40: 00000004
0012DB44: 00000000
0012DB48: 00000001
0012DB4C: 00000050
0012DB50: 000000C4
0012DB54: 00000000
0012DB58: 00000000
0012DB5C: 0045004D 00400000 + 5004D (acid60.exe)
> 0012DB60: 00410054 00400000 + 10054 (acid60.exe)
> 0012DB64: 005C003A 00400000 + 1C003A (acid60.exe)
> 0012DB68: 0065004D 00400000 + 25004D (acid60.exe)
> 0012DB6C: 006F006D 00400000 + 2F006D (acid60.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 00788D4A 00400000 + 388D4A (acid60.exe)
0012FFFC: 00000000

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: pwppch

Date:7/28/2006 8:26:59 AM

Can you email me the midi file that caused this, or is it ANYand ALL MIDI files that do this for you?

Please fill out your system specs.

Posting a sticky of these kinds of things would not 1) help things 2) make the turn around/update go any faster. Information and details of what your system is like and exactly what you did and how ACID is configured, the project looks like is what helps us to reproduce the problem.


Peter

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: pwppch

Date:7/28/2006 11:17:50 AM

You didn't provide enough details as to what you did prior to the drag of the MIDI file, so I am having to guess/assume what you have done.

From what I can tell from the dump, this is caused by the renaming or removing of the name of a clip. That is some how - by user action or some other means - the name of a clip on the track was set to empty.

The work around is to not name a clip to nothing.

If you did not purposely set a clip name to nothing, then could please give me the step you did that led to this problem.

We will address this in and update.

If you did set the name of a clip to nothing, why did you do this? Why would you want an un-named clip? (Not saying this isn't a bug, I am just curious as to your desired workflow.)

Peter

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: riley4reason

Date:7/28/2006 11:52:02 AM

I was dragging midi files already named by Groove Monkee, I was dragging a fill to be placed after the 1st groove. As soon as I let go of the mouse, I got the above error.

I updated my system specs.

Thank you for the help.
Riley

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: pwppch

Date:7/28/2006 3:42:29 PM

I downloaded some of the samples from Groove Monkee. They drag to new or existing tracks just fine for me.

'after the 1st groove' means what?

The crash dump you provided indicates that you have renamed a clip to nothing. Did you set the name of existing clips on any track to nothing?

Could you provide a step by step simplest case, starting from scratch, to reproduce the problem?

Peter

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: riley4reason

Date:7/29/2006 10:44:17 AM

I didn't rename anything. I dragged a midi part one up, then a fill, I let go of the fill and it crashed.

I just tried to browse to open a song from the file menu and it locked up my system. Had to reboot.

isn't there a way I can get the logs and post them here for you to see? Maybe you can see why it crashed opening a song from the file menu.

Riley

Subject:RE: Acid Pro 6a crash logs for devs

Reply by: pwppch

Date:7/29/2006 2:01:45 PM

There are no logs you can send us.

To be clear on exactly what you are doing:

- Start ACID
- Drag a MIDI file from Groove Monkee to the timeline.
- A track is created and an event containing the MIDI data is created
- Drag another MIDI file from the explorer to the same track and you crash.

If this is not what you are doing, can you please provide a step by step account? Please be specific as the problem usually is with in a detail that seems trivial.

What synth are you using? The DLS Synth, a specific VSTi, or external hardware?

When you say "open a song from the file menu" are you opening an ACID project file, wave file, or MIDI file?

Could you email me the file that causes you problems?

Peter