Hello,
mac pro 12 core, 96 gigs ram, mac osx 10.6.8.
Pro Tools 9.03, VEPRO v5.1.11548 and Uhe Diva v1.1.1. (rev. 871)
CASE A)
- in Pro Tools, auto read mode enabled, all 512 parameters are ready for automation (checked right-clicking VEPRO RTAS plugin, Automation Dialog) in the instrument track where VEPRO RTAS plugin is.
Of course in Pro Tools automation window the option "PLUG IN" is enlightened in red. I then write some pencil automation on the automation lane in PT9 for "Vienna Ensemble Pro RTAS, Param1".
I have in the VEPRO Automation Mapping view, "Parameter 1" associated to any of the possible parameters listed for "Diva 1", for instance "Diva 1 / Output", once by once at a time.
Click "Play" in Pro Tools, no movements of the knobs.
CASE B)
- in Pro Tools, auto write mode enabled, same Pro Tools and VEPRO automation settings reported in CASE A)
Click "Play" in Pro Tools to record some automation, and move the knob in Diva...the resultant automation, instead of showing a wave (various knobs positions), shows a square (on/off positions like)
When you switch to auto read mode in PT, and you play this automation, the knob in Diva don't move, as in CASE A).
Tried the same with NI Massive, no issues found, and the automation written in the lane is a normal wave.
Thanks.
Pro Tools 9, Vienna Ensemble Pro 5 and Uhe Diva host automation issues
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- 7 posts since 5 Nov, 2012
Last edited by beatlesforever on Mon Nov 05, 2012 8:41 pm, edited 3 times in total.
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- Topic Starter
- 7 posts since 5 Nov, 2012
tried with rev. 903, but still issue is
-
- KVRist
- 357 posts since 9 Jul, 2009 from Bay Area, California
I found your thread on the VSL forums and I'm more of a KVR regular so I thought I'd test out your issue and report back. I use VE Pro 5 and Pro Tools regularly so I thought it was peculiar that Diva wouldn't automate through the normal Pro Tools automation parameter routine. Here's what I found...
You are correct, choosing any "parameter" never works with VE Pro 5 in Pro Tools...it doesn't matter what synth you are using, they won't respond. The answer is a MIDI track!!! I found this post on MotuNation (but it still applies here...and explains it best...)
"VEpro only responds to MIDI commands. You need to create a MIDI track just for your desired automation then assign it to a channel that your synth is living on. For example, your synth is on group 1 channel 1, then assign the new MIDI track for automation to group 1 channel 2 in VEpro. Then you have to assign the filter on the synth you want to automate to channel 2."
That's exactly what I did and it works like a charm. Make a new MIDI track, put your instrument track in "Record Mode" and the automation into "WRITE," then with Diva in VE Pro 5, just right click and "Midi Learn" any of the parameters and assign them to a knob or slider on your MIDI controller. Hit record, perform your automation with MIDI, play it back. Diva's knobs and sliders are moving!!!!!!!!!!
Hope that helped!
Now I have a question for you, or Urs, or whoever...I'm running Diva in 32 bit through VE Pro 5. When I load up a 64 bit instance I don't see Diva in my drop down menu. I've got the latest version of Diva installed. Is there something I'm missing?
Cheers!!!
You are correct, choosing any "parameter" never works with VE Pro 5 in Pro Tools...it doesn't matter what synth you are using, they won't respond. The answer is a MIDI track!!! I found this post on MotuNation (but it still applies here...and explains it best...)
"VEpro only responds to MIDI commands. You need to create a MIDI track just for your desired automation then assign it to a channel that your synth is living on. For example, your synth is on group 1 channel 1, then assign the new MIDI track for automation to group 1 channel 2 in VEpro. Then you have to assign the filter on the synth you want to automate to channel 2."
That's exactly what I did and it works like a charm. Make a new MIDI track, put your instrument track in "Record Mode" and the automation into "WRITE," then with Diva in VE Pro 5, just right click and "Midi Learn" any of the parameters and assign them to a knob or slider on your MIDI controller. Hit record, perform your automation with MIDI, play it back. Diva's knobs and sliders are moving!!!!!!!!!!
Hope that helped!
Now I have a question for you, or Urs, or whoever...I'm running Diva in 32 bit through VE Pro 5. When I load up a 64 bit instance I don't see Diva in my drop down menu. I've got the latest version of Diva installed. Is there something I'm missing?
Cheers!!!
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- Topic Starter
- 7 posts since 5 Nov, 2012
S1gnsOfL1fe thanks for your help, very much appreciated...
...the point is that I'm already performing "midi automation" (or better, "midi learning" of the controllers for Diva, let's call it so) on the midi track which feed Diva...I've midi track #1 which sends midi data (pro tools in merge mode, don't mind if "write automation" for the midi track is enabled or not ) to the vepro instance which belongs to the vepro rtas plugin inserted in the main instrument track...in that instance, the instruments triggered by midi track #1 is indeed Diva 64bit (to answer your question, I just made a clean install of the 1.1.1, rev.903 version, just that), and I do control pretty easily the whole beast (using Diva's midi learn feature) ...but the issue is not in channel "automation" (midi learn, 128 midi cc, hardware device), because as far as Diva has sooo many parameters to control, you'd be forced to make use of the plugin automation option (the one which belongs to the "write automation" feature of the main instrument track, where the vepro rtas plugin is, 512 parameters, mouse controlled)..
...that one simply I can't make it work, period, no matter what I try, the results are reported on my first message...and once I apply th same settings in order to "plug-in automate" NI Massive synth, for instance, it just DO work flawlessly...
...so there must be an issue between Diva and Vienna Ensemble Pro.
In regards to what you ask my friend, the only suggestion which comes in my mind is trying uninstalling and reinstalling Diva, repairing permission, and rescanning all the plugins in the vienna 64bit server preferences.
Thanks again for your help !
...the point is that I'm already performing "midi automation" (or better, "midi learning" of the controllers for Diva, let's call it so) on the midi track which feed Diva...I've midi track #1 which sends midi data (pro tools in merge mode, don't mind if "write automation" for the midi track is enabled or not ) to the vepro instance which belongs to the vepro rtas plugin inserted in the main instrument track...in that instance, the instruments triggered by midi track #1 is indeed Diva 64bit (to answer your question, I just made a clean install of the 1.1.1, rev.903 version, just that), and I do control pretty easily the whole beast (using Diva's midi learn feature) ...but the issue is not in channel "automation" (midi learn, 128 midi cc, hardware device), because as far as Diva has sooo many parameters to control, you'd be forced to make use of the plugin automation option (the one which belongs to the "write automation" feature of the main instrument track, where the vepro rtas plugin is, 512 parameters, mouse controlled)..
...that one simply I can't make it work, period, no matter what I try, the results are reported on my first message...and once I apply th same settings in order to "plug-in automate" NI Massive synth, for instance, it just DO work flawlessly...
...so there must be an issue between Diva and Vienna Ensemble Pro.
In regards to what you ask my friend, the only suggestion which comes in my mind is trying uninstalling and reinstalling Diva, repairing permission, and rescanning all the plugins in the vienna 64bit server preferences.
Thanks again for your help !
-
- u-he
- 30225 posts since 8 Aug, 2002 from Berlin
Hmmm, unfortunately we don't have Vienna.
If Massive works but Diva doesn't, maybe Diva needs to be MIDI-Learned first?
If Massive works but Diva doesn't, maybe Diva needs to be MIDI-Learned first?
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- Topic Starter
- 7 posts since 5 Nov, 2012
hello Urs, nice to meet you, and thanks for sharing your knowledge about.
Just wanna say, if it wasn't clear enough, that I already midi learned Diva for mapping it to a hw midi controller, and it worked perfectly ! ( within the limits of the number of available midi ccs, which goes from #1 to #119, in Diva's case).
But here I'm talking about host automation, in order to map the entire synth's range of parameters...
...unless you're telling me to apply the midi learn feature (right-clicking), also to the parameters which are supposed to be host automated, but I recall to have tried that already, not to say that in Vienna Ensemble Pro automation mapping, the Diva's available parameters are already listed for automation, when you scroll them...and if you learn the parameters from vepro (you click on the "L" in the destination tab, and click on whatever Diva's knob, then the relative parameter is shown and automation-ready as expected)
but when you perform it, if you write, it writes squares, and if you read it back, there's no automation performed at all...
I'm thinking to download the demo of Zebra2 or Ace from Urs, and check if this behavior is common to all these products...
...anyway...Diva is freakingly astounding ! Best synth ever, how did you manage to make it ?? Night is meant for sleeping, not for workin' or playin' !!
I will report back later...
Just wanna say, if it wasn't clear enough, that I already midi learned Diva for mapping it to a hw midi controller, and it worked perfectly ! ( within the limits of the number of available midi ccs, which goes from #1 to #119, in Diva's case).
But here I'm talking about host automation, in order to map the entire synth's range of parameters...
...unless you're telling me to apply the midi learn feature (right-clicking), also to the parameters which are supposed to be host automated, but I recall to have tried that already, not to say that in Vienna Ensemble Pro automation mapping, the Diva's available parameters are already listed for automation, when you scroll them...and if you learn the parameters from vepro (you click on the "L" in the destination tab, and click on whatever Diva's knob, then the relative parameter is shown and automation-ready as expected)
but when you perform it, if you write, it writes squares, and if you read it back, there's no automation performed at all...
I'm thinking to download the demo of Zebra2 or Ace from Urs, and check if this behavior is common to all these products...
...anyway...Diva is freakingly astounding ! Best synth ever, how did you manage to make it ?? Night is meant for sleeping, not for workin' or playin' !!
I will report back later...
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- Topic Starter
- 7 posts since 5 Nov, 2012
Unfortunately I had no luck with both the demos of Zebra & Ace, same issues as in Diva...host automation don't work thru vienna ensemble pro 5...
I really hope when you've the time you'll take a closer look to this issue, thanks !
I really hope when you've the time you'll take a closer look to this issue, thanks !
-
- KVRist
- 357 posts since 9 Jul, 2009 from Bay Area, California
While unrelated to beatlesforever's issue, I did end up resolving Diva not appearing in the 64 bit version of VE Pro 5.
All I had to do was open the preferences in Vienna and manually "rescan" for new plugs. I thought that this was done everytime it opens, but apparently not.
Once I did that, I saw Diva was now in the "list" of available plugins in 64 bit.
This, combined with the latest update to VE Pro 5 adding .aax support, I'm one happy camper!
All I had to do was open the preferences in Vienna and manually "rescan" for new plugs. I thought that this was done everytime it opens, but apparently not.
Once I did that, I saw Diva was now in the "list" of available plugins in 64 bit. This, combined with the latest update to VE Pro 5 adding .aax support, I'm one happy camper!
-
beatlesforever beatlesforever https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=291373
- KVRer
- Topic Starter
- 7 posts since 5 Nov, 2012
Glad to see you are happy S1gnsOfL1fe, luckily we have this awesome tool vepro5 is, so we can drop down those rtas VIs and fire up AU ones, like Diva !