Wednesday, April 23rd 2014, 1:48pm UTC+2

You are not logged in.

  • Login

Dear visitor, you are currently not logged in. Login or Register as a new user .

Zap13

Trainee

  • "Zap13" started this thread

Posts: 80

Location: Brampton, Ontario, Canada

  • Send private message

1

Tuesday, December 1st 2009, 3:45pm

Please fix 2 Huge Problems/Bugs in Virus Control for Pro Tools

Severe bugs to report on VC 3.1: Ctl-start-alt clicking on any virus parameters does not enable automation of those parameters in Pro Tools. That is the shortcut that enables automation of plug-in parameters. And another possible bug is that hitting the down arrow in the browser window does not go to the next patch. And the up arrow does not go to the previous preset either. The only way to switch patches is to double click.

But i cannot go patch searching by double clicking through thousands of presets. Please bypass pro tools like reaktor snapshot windows does for up/down browsing of the snapshots.

Again, in other words.... in other plug-ins like Reaktor, the down and up arrows are made to switch patches in the reaktor patch snapshot window even in pro tools. This is an essential must for any plug-in's browser that has lots of patches to scroll through. The operation of this feature not working in VC can only be considered to be a bug. It is much too severe of a problem for a pro tools user and I simply have no choice but to wait to see if Access can fix these problems because there is no efficient workflow in VC in PT as a result of these bugs when looking for sounds.

Thanks

This post has been edited 3 times, last edit by "Zap13" (Dec 3rd 2009, 5:49am)


Zap13

Trainee

  • "Zap13" started this thread

Posts: 80

Location: Brampton, Ontario, Canada

  • Send private message

2

Thursday, December 3rd 2009, 5:42am

does anyone know if 3.2 or 3.3 betas fix this so i can know if it is worth the upgrade before i do the install again?

This post has been edited 1 times, last edit by "Zap13" (Dec 3rd 2009, 5:50am)


3

Monday, December 7th 2009, 5:22pm

I don't think so, but you can read the new "change log" if there will be a fix.