|
Avid Pro Audio CommunityHow to Join & Post Community Terms of Use Help Us Help YouKnowledge Base Search Community Search Learn & Support |
#1
|
|||
|
|||
Controller Automation : Please Explain
I am baffled by the PT Controller Automation system and am hoping someone will be able to explain it to me.
Recently I have been automating plug-ins. I found that if I automate parameters with the mouse, the automation will be displayed in a track view labled "plug-in" > "name of parameter" but if I automate with a MIDI controller (which I much prefer), the automation will be displayed in a track view labeled "controllers" > "name of controller." The problem here is that the names of the controllers in the list bare no relationship to the automated plug-in parameters and it seems they cannot be re-named, not that that would be much of a solution anyway since the names would need to be different depending on the plug-in being automated. Names like "portamento" mean nothing to me, not to mention all the controllers labeled as "undefined." Suppose I want to go and edit some previously recorded automation later on, how am I supposed to know which controller relates to which automated parameter? The only connection I can see is the CC number in brackets next to the controller name. Am I really expected to remember the CC number of every automated parameter for every plug-in or am I missing something? Why wouldn't controller automation simply appear in the same track view as mouse automation and with the same logical parameter naming? If not that, why wouldnt the automation appear in the controller view as it does now but with the actual name of the automated parameter, like it does with mouse automation? Another thing is that controller automation cannot be written in the stardard way of simply choosing a write mode & hitting play. Instead, the track must be record enabled as must global record, in addition to selecting a write mode and hitting play. This in turn means that an actual MIDI recording is taking place, not just an automation recording. Therefor, MIDI Merge has a profound effect on the recording of controller automation. If MIDI merge is truned OFF & controller automation is recorded, everything will be lost including any MIDI notes on that track. If MIDI merge is turned ON, it is impossible to record over previous controller automation with new controller automation, even when in auto write mode. It still merges it. This means that old automation must be cleared first before new automation can be recorded. Thirdly, the controller automatoin line does not reflect MIDI controller moves while transport is stopped i.e. a knob of fader on the MIDI controller could be moved and the automation line will stay where it is (where the mouse last left it). There is no update until automation is actively being recorded. Since there is a short period of time between pressing play (to initialise auto recording) and acually moving controls, the start of the auto display will often be wrong. It will show that the control was at one value when it was infact at another and the audio will show this error. This whole system seems crazy to me. I am wondering if I'm not implementing it properly. I've searched the DUC and the Answer bases but I cannot find any information on this topic. The manual hasn't been much of a help either. Someone, please releive my ignorance if thats what it is. Thanks.
__________________
PT LE 7 & MBox Windows XP SP2 P4 3.0GHz CPU, Intel 865/PE/P Chipset 1GB RAM 2 X Seagate Barracuda 80GB HDD Novation Remote SL MIDI Controller |
#2
|
|||
|
|||
Re: Controller Automation : Please Explain
Anyone?
__________________
PT LE 7 & MBox Windows XP SP2 P4 3.0GHz CPU, Intel 865/PE/P Chipset 1GB RAM 2 X Seagate Barracuda 80GB HDD Novation Remote SL MIDI Controller |
#3
|
|||
|
|||
Re: Controller Automation : Please Explain
I think the basic thing you're missing is that midi automation is different than plug-in automation. Plug-in automation is specific to the plug-in. Midi automation applies to the same parameter for all keyboards, so if you automate portamento and have three keyboards daisy-chained together, portamento will affect all three keyboards.
Midi automation has been around alot longer than plug-in automation. The reason there is plug-in automation is because midi automation already existed. Back before there were computers everywhere and digital audio, the only way to create alot of effects was with midi automation. Now you basically have a choice between the two. Another difference is that plug-in automation is alot more responsive than midi automation, that is, midi just isn't as fast off the mark. I'm old enough to remember when continuous controllers (cc) were added to the midi spec and at the time, it was considered beyond cool. Being able to change three parameters at once without having to turn a knob on a hardware keyboard was a signicant development for keyboardists. I do understand your confusion though. It is possible now to do alot of the same things with a plug-in that were previously done with keyboards. And yes, you do have to record midi automation in order for it to take, unlike automating an eq plug-in. However, you can go in and edit the midi automation as soon as you're done recording. |
#4
|
|||
|
|||
Re: Controller Automation : Please Explain
Thanks for your reply.
I'm not sure if I explained myself properly. Please allow me to give you an example situation. I'm using a Novation Remote SL MIDI Keyboard Controller. It has lots of knobs, buttons and sliders on it. I want to automate parameters on third party virtual instruments using my controller. Suppose I were to do this in Cubase. No matter if I used the mouse or my controller to automate a plug-in parameter, the automation would appear in the same track view which would bare the name of the automated parameter. Suppose I were to do this in PT. If I use the mouse to automate a parameter in the plug-in, the automation will appear in a track view which would bare the name of the automated parameter. On the other hand, if I were to use my controller (which is obviously what I want to do) to automate the parameter, the automation will appear in a "controller" track view baring a name unrelated to the automated parameter, making it almost impossible to find later on after lots of parameters have been automated and added to the list with unrelated names. I'm failing to understand the advantages of this system (if there are any). So far I see only problems (which I described in my first post). It seems there are only 3 options. 1. Use the MOUSE to automate third party plug in parameters and be able to find the automation later down the track for further editing. 2. Use the CONTROLLER to automate third party plug in parameters and struggle to find the automation later down the track for editing. 3. Use CUBASE or any other sequencer which operates logically by naming track views with the automated parameter's name, no matter what device it was automated by. Is there an option that I'm missing here?
__________________
PT LE 7 & MBox Windows XP SP2 P4 3.0GHz CPU, Intel 865/PE/P Chipset 1GB RAM 2 X Seagate Barracuda 80GB HDD Novation Remote SL MIDI Controller |
#5
|
|||
|
|||
Re: Controller Automation : Please Explain
Does anyone else have any ideas on this?
__________________
PT LE 7 & MBox Windows XP SP2 P4 3.0GHz CPU, Intel 865/PE/P Chipset 1GB RAM 2 X Seagate Barracuda 80GB HDD Novation Remote SL MIDI Controller |
#6
|
|||
|
|||
Re: Controller Automation : Please Explain
I believe you should check your manual first for the keyboard you're using so you know what type of cc is being output first, and then you can make sure you're in the right midi track view when you record. I believe all parameters are the same for all keyboards, like midi volume is cc 7, and it's the same for all keyboards.
If you do it this way, you won't have to search through all the cc midi tracks looking for your data. |
#7
|
|||
|
|||
Re: Controller Automation : Please Explain
Unless your controller is supported as a control surface by Pro Tools or runs in HUI mode... then all you're doing in Pro Tools is recording MIDI data which some plug-ins may support... but it's not going to show up as automation in Pro Tools on the Pro Tools automation graphs. As you've seen, it'll show up as MIDI data.
Rail
__________________
Platinum Samples www.platinumsamples.com Engineered Drums for BFD |
#8
|
|||
|
|||
Re: Controller Automation : Please Explain
myfm: I dont understand how this is a solution. With 10 automated parameters in the controller auto view list, I will still have to know which CC # refers to which parameter. Volume and other parameters may be the same in some cases but for the most part, the CC # for a given parameter will change depending on the plug-in / controller template.
Rail: Thanks for the tip on running the controller in HUI mode. Novation have said they are looking into developing a HUI mode (Digi have said they can) for the Remote SL so that could solve a lot of my problems if it ends up happening. It frustrates me greatly that Digi make it so difficult to implement third party gear with PT. In any other sequencer this is not a problem at all.
__________________
PT LE 7 & MBox Windows XP SP2 P4 3.0GHz CPU, Intel 865/PE/P Chipset 1GB RAM 2 X Seagate Barracuda 80GB HDD Novation Remote SL MIDI Controller |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help using a MIDI controller to do automation. | rockguitarist1255 | Pro Tools 10 | 7 | 01-31-2013 06:35 PM |
Controller, and Automation lanes. | JimC | Pro Tools TDM Systems (Mac) | 12 | 05-25-2010 08:28 PM |
Digi 002 Controller Automation | motoxracer400f | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 11-06-2008 10:59 AM |
Midi controller for Automation - setup help? | undergroundcubby | MIDI | 6 | 11-22-2007 01:25 AM |
MIDI Controller Automation : Please Explain | Equality 7-2521 | MIDI | 9 | 03-26-2006 06:17 PM |