Subject:AP7 demo - strange things

Posted by: drbam

Date:11/23/2009 6:26:50 AM

I've been trying out the AP7.0c demo, really putting it through some complex projects and am wondering if the following are related to the demo version only or just buggy-ness:

1. Even though I have "External Control" checked for my MCU Pro (which is set up properly and seems to work fine so far), when I quit and then re-launch AP7, it is unchecked and I have to again check it in the options menu to make the MCU fully functional. Note - the MCU is not being used by a different app for this to occur. Sound Forge was the only other app being used.

2. When rendering new clips or loops within a project, there is no consistency regarding what folder AP7 directs me to for saving the file. Sometimes its the AP7 folder on the C drive - other times it might be a project folder on my media drive that I worked on a few days earlier and has nothing to do with the current one, or it could be the current one. It is clear that the behavior is random. AP6 does not behave this way.

I'm hoping that these are simply related to the demo, but if not, then # 2 is a deal-breaker for sure.

Thanks!

Subject:RE: AP7 demo - strange things

Reply by: pwppch

Date:11/23/2009 6:53:01 AM

I am unable to reproduce #1.

I am looking into #2, but it sounds like a bug.

Peter

Subject:RE: AP7 demo - strange things

Reply by: drbam

Date:11/23/2009 7:11:24 AM

Peter - thanks for your quick response!

#2 seems like such a workflow block (for me at least) that I'd be very surprised to discover that I'm the first one to report it. Anyway, I look forward to knowing what you find out. Thanks again!

Subject:RE: AP7 demo - strange things

Reply by: drbam

Date:11/23/2009 1:12:06 PM

Re: #1: I can reproduce it with 100% consistency. Launch AP7 after booting computer (no other apps running). Check under Options menu and "External Control" is unchecked. Check it - make sure that MCU is running properly - save the session - close AP7. Re-launch AP7 and once again external control is unchecked.

Another minor bug: if I choose more than 6 in the show previous sessions preferences, AP7 no longer shows the proper sequence of previous sessions. I selected 9 and nothing ever changed in the previous sessions window until I went back to selecting the default 6 as the maximum number and it began working properly.

Subject:RE: AP7 demo - strange things

Reply by: lofreequency

Date:11/23/2009 1:39:54 PM

"can reproduce it with 100% consistency. Launch AP7 after booting computer (no other apps running). Check under Options menu and "External Control" is unchecked. Check it - make sure that MCU is running properly - save the session - close AP7. Re-launch AP7 and once again external control is unchecked."


Same here. #1 happens all the time with my Behringer BCF2000. Quite annoying. ( I just assume Acid doesn't want to assume you want to use the external controller in each session so one has to tell it to look for it? Seems like that should be able to be saved in a project's settings if one wanted though)

Have had buggy probs with #2 too in the past too.

Subject:RE: AP7 demo - strange things

Reply by: Kit

Date:11/23/2009 1:46:08 PM

I just wish Acid would remember which was the last used folder like most other applications. If it had Sound Forge's dropdown list of recently accessed folders that would be useful too.

Kit

Subject:RE: AP7 demo - strange things

Reply by: drbam

Date:11/23/2009 2:29:56 PM

Well I think I'm honing in on the potential problem. I am starting to have some crashes with AP7 when editing and one of the crashes gave me an error dump that pointed to the MCU dll (I can post this later). I uninstalled AP7, reinstalled (again running as demo). This time I turned off the MCU and have been doing some work with just the mouse and keyboard (a big PITA after being accustomed to the MCU for almost 2 years). At any rate, AP7 "seems" a bit more stable and it hasn't crashed since shutting down the MCU. I'll keep pushing it and report back later and also post the error message as this may help Peter track down what is happening.

Update: Stack dump data

ACID Pro 7.0
Version 7.0c (Build 653)
Exception 0xC0000005 (access violation) READ:0x06ACDF08 IP:0x0B52E902
In Module 'spmackiectrlopt.dll' at Address 0x0B430000 + 0x000FE902
Thread: GUI ID=0xA30 Stack=0x0012F000-0x00130000
Registers:
EAX=00000001 CS=001b EIP=0b52e902 EFLGS=00010206
EBX=00000001 SS=0023 ESP=0012fc28 EBP=fffffff0
ECX=06a99998 DS=0023 ESI=06873f68 FS=003b
EDX=06acdf08 ES=0023 EDI=00000001 GS=0000
Bytes at CS:EIP:
0B52E902: 83 3A 00 74 22 8B 81 38 .:.t"..8
0B52E90A: 0C 00 00 8B 08 56 8B 74 .....V.t
Stack Dump:
0012FC28: 0B43D4C5 0B430000 + D4C5 (spmackiectrlopt.dll)
0012FC2C: 06ACDF08 06790000 + 33DF08
0012FC30: 0012FC60 00030000 + FFC60
0012FC34: 00000000
0012FC38: 0000000A
0012FC3C: 06ACE008 06790000 + 33E008
0012FC40: 06873F68 06790000 + E3F68
0012FC44: 00000000
0012FC48: 00000002
0012FC4C: 00000000
0012FC50: 00000000
0012FC54: 00000000
0012FC58: 00000000
0012FC5C: 000665C5 00030000 + 365C5
0012FC60: 00000000
0012FC64: 00000000
> 0012FD7C: 0B43D9E9 0B430000 + D9E9 (spmackiectrlopt.dll)
0012FD80: FFFFFFF0
0012FD84: 00000008
0012FD88: 00000000
0012FD8C: 06873F68 06790000 + E3F68
> 0012FD94: 0B4431C2 0B430000 + 131C2 (spmackiectrlopt.dll)
0012FD98: 00000000
0012FD9C: 00000000
0012FDA0: 0012FE20 00030000 + FFE20
0012FDA4: 06A99998 06790000 + 309998
> 0012FDB4: 0B52D30D 0B430000 + FD30D (spmackiectrlopt.dll)
0012FDB8: 06A99998 06790000 + 309998
> 0012FDBC: 0B52D49D 0B430000 + FD49D (spmackiectrlopt.dll)
0012FDC0: 0012FE20 00030000 + FFE20
0012FDC4: 00000001
0012FDC8: 00000000
0012FDCC: 00000000
> 0012FDDC: 0B52B6B8 0B430000 + FB6B8 (spmackiectrlopt.dll)
- - -