Subject:Arp2600V problem in AP7c

Posted by: april.exe

Date:6/27/2009 1:49:58 AM

Loading the Arp2600V goes fine and patch edits are saved with the .acd no problem.

When adding a new vsti or midi track the 2600 resets to a default patch.

Choosing "Use Device Program Map" seems to be a fix. Does not work each time.

The patch change midi message filter does not seem to help.

Running the vst version of the 2600, possibly the dx will behave differently.

Subject:RE: Arp2600V problem in AP7c

Reply by: Bremen Cole

Date:6/27/2009 6:41:28 PM

My copy of Sylenth1 does this exact same thing. As a work around I put the first midi track in a project hooked to the default Sony synth, and then don't even use that track. For whatever reason when I put Sylenth1 in midi tracks after that, I do not have the problem.

It is some kind of bug, that that work around works for me.....

Subject:RE: Arp2600V problem in AP7c

Reply by: april.exe

Date:6/28/2009 2:30:47 AM

Thanks! Fix is working so far.

Subject:RE: Arp2600V problem in AP7c

Reply by: pwppch

Date:6/28/2009 6:17:37 PM

I have reproduced this.

ARP2600V appears to be an OMNI Softsynth. That is it will listen to all MIDI channels the same. It appears that when you add a new track and the ARP2600V is the first synth you add to your project, new MIDI tracks will be routed by default to it and ACID sends a default patch of 0 to the ARP2600V. This causes the patch to be "rest".

The suggest work around appears to solve the problem.

Another workaround is to enable at least one MIDI Output. This way all New MIDI tracks will route by default to the external MIDI port.

Neither is ideal in any way.

I will get this issue into our tracking system so we can provide a better solution in a future release.

Peter

Subject:RE: Arp2600V problem in AP7c

Reply by: april.exe

Date:6/29/2009 5:18:46 AM

Thanks, I will try adding the midi out as well. I had also tried a midi data filter on track 1 which helped.