Changing parameters in AAX plug-ins in PT 12

[Brian@Wavefield Recordings]

Hi all,

I'm probably missing something but I'm not able to change parameters
with a lasting effect in plug-ins at the moment, thankfully I've no
mixes to finish anytime soon and its interesting getting buy on
presets for rough mixes.

Any parameter changes I make while transport is engaged or while
transport is stopped get changed back to the plug-in or preset
default positions when I resume playback later.

I've tried changing automation modes and tried writing in my changes
as automatin moves in the plug-in but no luck, no parameter changes
will stick for me.

I've scanned through the preferences but no setting seems to be
relevant to this.

Thanks for any answers possible solutions etc,

Brian.

[Poppa Bear]

I am not using PT 12, but have you tried to save the parameters as a preset and then go back and see if they stuck?

--
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stefan Albertshauser]

Hi Bryan,

Go to Setup, preferences, select the mixing tab, find the group automation, interact with it and locate the checkbox called „Plugin parameters activate for automation by default“ or so. Uncheck it, when it is checked. This should solve the problem.

Best Stefan

[Slau Halatyn]

I've seen a few inquiries about automation and thought I'd chime in. I've never even attempted any sort of automation without a control surface and I can't imagine how anybody would even consider performing automation moves with VoiceOver. Still, I suppose it could be done for very simple operations. Here's the main thing I meant to communicate (and this is not specifically directed toward Stefan but anybody in general who has tried to automate plug-ins): In order to automate a plug-in's parameter, the individual parameters to be automated need to be enabled. For example, in a plug-in with 80 parameters, rather than automating all parameters, you can simply select the handful of parameters that need to be automated. Unless you enable those parameters, nothing at all will be written. You need to enable them from within the Plug-in Automation enable dialog. Press the Plug-in Automation Enable button in the Plug-in window and navigate to the text review area, interact and double-click on the parameters you wish to enable for automation. Each parameter that has been automation enabled will disappear from this list. Now, when you start writing automation, the parameter values will be written. You can edit and delete that automation by selecting the particular parameter from the Track view pop-up that normally displays waveforms. Once you're displaying volume or pan information or whatever parameter you wish to edit, any edits you do will affect the displayed parameter rather than the underlying audio.

All of the stuff I'm mentioning is covered in detail in the Reference Guide. Just as I can't imagine trying to automate without a control surface, I can't imagine trying to do it without having read the manual. I encourage anyone who wants to learn how to automate in Pro Tools to read the automation chapter and learn about automation the way it should be learned. Yes, experimentation will ultimately be necessary but a basic understanding of the principles is key. It doesn't matter if you know what automation is because you used it in another DAW. If you're trying to use it in Pro Tools, learn how it's done in Pro Tools.

Finally, one more word about surfaces: when performing automation moves, it's far, far more efficient to do it with a surface, of course, but even more so, it's far easier to understand the effect of the automation pass when you can verify the moving faders' positions throughout the process. In fader flip mode, any parameter's automation can be tracked with the faders. Something to seriously consider.

Cheers,

Slau

[CaseyBrian Casey]

Hi all, back on this topic I am still unable to adjust plugin parameters in a plugin using Voice Over which I gather shouldn't be a problem.

I think Slau may have taken me up wrong, I'm not trying to write automation or anything, just change values of parameters.

For example I changed the polarity of a track using the trim plugin but after changing the parameter it reverts to its original state when I next resume playback.

I have tried changing some of the prefs relating to automation and tried turning off all automation but no joy. Fyi I aim to install a bcf2000 for controling plugs but I'm not sure that will change this behaviour.

To avoid clogging the list, I will also quickly mention that using shift and period on the num pad is for some reason not selecting to the next memory location as it should, also command and 5 is not opening the memory locations window for me and I have to go via the menus to find it,

Any ideas on this are greatly appreciated, having gone through many tutorials and looking through pt documentation it seems certain things are not appearing/working as they should.

Brian.

[Poppa Bear]

Bryan, some have found that they have an automation box checked and it is affecting the parameter changes. I am not using version 12 so I can not directly help. I hope that somebody who has kept track of this issue can assist.

-----Original Message-----
From: ptac...@googlegroups.com [mailto:ptac...@googlegroups.com] On Behalf Of CaseyBrian Casey
Sent: Tuesday, May 05, 2015 11:15 AM
To: ptac...@googlegroups.com
Subject: Changing parameters in AAX plug-ins in PT 12

[Brian Casey]

I've now found that the issue was check boxes in preferences not being read correctly by Voice over, wonder if this is normal?

Can't figure why key strokes for selecting between markers aren't working when other selection key strokes like shift return etc are.

Sent from my smart-ish phone!

> You received this message because you are subscribed to a topic in the Google Groups "Pro Tools Accessibility" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/ptaccess/n3ErriKAw1w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to ptaccess+u...@googlegroups.com.

[Poppa Bear]

Bryan, can you still use 3 on the numb pad to start record.

[Brian Casey]

Yup, all transport mode stuff works from the num pad

Sent from my smart-ish phone!

[mcdiemert .]

do you have quick nav, or quick keys turned on by chance?
Are you able to jump between markers?

Warm Regards:
Matt Diemert
330-980-0046

[Brian Casey]

Quick nav did catch me a few weeks ago but vo is set to normal, I can jump to markers as normal.

I'm getting by with creating region breaks and selecting that way for the moment, searching in preview in the shortcut guide isn't giving me any results relating to selecting to the next or previous memory location, only shortcuts relating to creating and moving to memory locations, I'm still assuming its something I'm doing wrong rather than something changing in pt 12.

Thanks for the suggestions,
Brian

Sent from my smart-ish phone!

[mcdiemert .]

Brian,
Let's say you have two markers, and you want to select everything
between marker 1 and marker 2. First Go to marker 1 by pressing period
one period on the numeric keypad. To select up to marker two, you
would hold down shift, and press period 2 period again from the
numeric. HTH

[Brian Casey]

Thanks for that, they are thhe exact steps I'm taking but no luck. Selecting regions to nearest transients etc are all working just fine.

Thanks for your response on slate vmr also, very helpful, I mostly want it to try reviver but its good to know that the parameters show once the modules are in place with a preset.

Sent from my smart-ish phone!

[Scott Chesworth]

With this preset method, that'd mean that you're restricted to running
one module per instance of VMR, right? Is there much of a difference
in terms of resources if you run a few instances instead of the
expected usage of chaining multiple modules within one instance? I
haven't sprung for any Slate stuff beyond Trigger yet, but I like what
I've heard and have enough sighted help available at the moment to get
stuff set up.

Scott

[Brian Casey]

I gathered that you could have someone setup any number of presets for different configs of whatever modules you have. The slate stuff isn't so cpu intensive anyway so I'd imagine multiple instances of vmr would be another good work around

Sent from my smart-ish phone!

[Scott Chesworth]

Sure, just figured that having one module per preset and then running
multiple instances would lend the most amount of flexibility. Gonna
grab a demo and give it a whirl tomorrow.

[Brian Howerton]

What exactly do I tell my sighted assistant what to do? I'm not really sure what to tell them to do.
Brian

Sent from my iPhone

[Chris Smart]

Scott, if you typically go EQ before compression, get someone to set
you up a preset containing a VCC channel, an EQ, a compressor like
the FG116 module, and whatever else you want after that. You can then
turn modules on or off as needed, adjust their parameters etc.

[Chris Smart]

you can add modules to the rack on screen in any order you like, then
save what you come up with as a preset.
Show your sighted help the manual if necessary.

Or, here's an idea. Bug Anthony at Slate tech support. He was more
than happy to help me set this up with him connected remotely. Can
you guys do that on the Mac side with something like Teamviewer?

Chris

[Scott Chesworth]

Good to know Chris, cheers. Out of interest, how well are the
parameters labeled? Do they all display formatted values? I'm assuming
that'll be the same on Windows and Mac because most stuff is. I'll be
using this on both sides of the fence, which means creating two sets
of presets annoyingly.

[Chris Smart]

the parameter values and names do make sense and Slate are certainly
willing to improve this if necessary. When I talked to Anthony, he
got a look first-hand at how I get at stuff on the Windows side.

[mcdiemert .]

On the mac side of things, the parameters don't make a whole lot of
sense, and it's a pretty sprawling plug.
What I have done, when working with the VCC moduals is to set each one
up and set the gain knob to 6 this way, I can quickly find it with the
item chooser. I like the tube immulation part of it enough to use, but
I personally don't find the other elements, IE compression EQ good
enough to spend the time navigating through such a poorly laid out
plug. Just my personal opinion.

[CHUCK REICHEL]

Hi Chris,
Yes teem viewer & calling slate tech support is a good idea!
Theres some accessibility flags up in front of "steven" currently & the phone call & remote link up is much encouraged now!
Talk soon
Chuck