O.S. 3.0.10 is out!
 

Wish you a happy eastern:)


http://www.access-music.de/downloads...idesktop#cat18

Here it's a disaster, USB conflict with other devices. No problems in previous version.
(Mac os x 10.5.6-MacPro late 08 -Logic 8.0.2)
-A

Back to 3.0.9 all fine.

what do you mean exactly?

marc

Virus TI plugin v 3.0.1.10 doesn't work in Cubase SX 3.1.1

I mean a USB conflict message with other devices connected to my computer appear when Logic is come up. Try to change the usb connection putting Snow on the self powered hub or on the back usb ports but the conflict is still on.
Back to previous version solve the problem.....this problem...not the others....but that's another story.....
-A

did you load the vst3 version?

Mark the arp function did not work inthe vst3 09 version, is this fixed?
also can you create an "enable ARP note out" button next to the hold button? so you can select this from the DAW rather than the TI synth itself?

I have installed only VST2 plugins. Cubase shows only Virus TI Snow plugin, it doesn't load the Virus TI plugin. When I open Plug-in Information window, the Virus TI line is brown and it shows only name and path of the plugin. Virus TI Snow plugin is displayed normaly.

going back doesn't solve your problem, 3.0.1.09 just doesn't display an error message because the error message wasn't implemented in older builds. the problem you are having was there the whole time. also you're talking about other problems. can you elaborate?

please contact access support and let them help you.

thanks, marc

Unfortunately this can't happen. I asked Joerg at Access about having a button to toggle ARP NOTE SEND from within VC, instead of the synth itself, and he said it can't be done due to that setting being a global setting for the synth itself??

I thought it would be much easier as well to handle everything while you are already on the page, but alas I will not hold my breath for that to be implemented.

Strange as well how the ARP NOTE SEND can only be done on odd number parts to boot. Another confirmation from Access that this is a hardware limitation. No clue why, but they are aware of this and state it is normal behaviour.