Hi all.
I'm pretty sure I've done this before so maybe I'm forgetting something important.
I'm basically trying to automate a plugin's parameter like this:
https://youtu.be/pcFsGs6eAqo?t=391
I'm doing just as she's saying but it's like the line I've drawn in the editor is simply being ignored?
In other words, in regards to the plugin's respective parameters changing, nothing is happening. I don't see anything on the plugin's gui change and it sounds like the effect is simply bypassed. It's not though.
FWIW, I can indeed manually move any parameter of the plugin and have its sound be affected though.
I must be missing some important step?
Thanks for any advice!
DP 10 plugin paramter automation not working?
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Re: DP 10 plugin paramter automation not working?
It's always astounding to me how often I'm able to solve* my own problem ONLY after publicly announcing it. Does this happen to others?
*I watched this video on DP's Automation Lanes which I've never seen before. I've never even had the use for lanes, I guess.
https://www.youtube.com/watch?v=QnoeVMb ... nel=motuTV
Either way, if I opened up the lane for this plugin parameter, there were many "missing" titles in the lane text. Those were of old attempts at this process whose settings theoretically shouldn't be showing up if that plugin was effectively uninstalled (i.e. set to 'none') in the Mixer Overview, right?
Seems odd. Why does the lane hang on to plugin data that was unset?
Anyway, to get around this...
You can open the lane of the track you're working with to see what's there. In my case, in that track's respective lane-view, there was no "automation line" drawn-out like I would expect. This seems buggy because if there's only one automation lane, shouldn't that automation lane be showing the line I drew in the Sequence Editor track's "non lane" view? it was simply missing even though I could indeed see it drawn over the waveform in the "non-lane" view (which is where the actual drawing of the curve took place).
To make this work, you draw the line in the actual automation lane; then automation works. ALSO, the line drawn in the automation lane does indeed get copied to the aforementioned Sequence Editor track's non-lane view after hitting enter.
So automation drawn in the sequence editor without showing lanes might not be happening sometimes? (i.e. It doesn't get copied to a lane properly?)
And that's because one needs to do the drawing of the automation in the track's respective lane-view instead?
Ok. Still seems weird though.
*I watched this video on DP's Automation Lanes which I've never seen before. I've never even had the use for lanes, I guess.
https://www.youtube.com/watch?v=QnoeVMb ... nel=motuTV
Either way, if I opened up the lane for this plugin parameter, there were many "missing" titles in the lane text. Those were of old attempts at this process whose settings theoretically shouldn't be showing up if that plugin was effectively uninstalled (i.e. set to 'none') in the Mixer Overview, right?
Seems odd. Why does the lane hang on to plugin data that was unset?
Anyway, to get around this...
You can open the lane of the track you're working with to see what's there. In my case, in that track's respective lane-view, there was no "automation line" drawn-out like I would expect. This seems buggy because if there's only one automation lane, shouldn't that automation lane be showing the line I drew in the Sequence Editor track's "non lane" view? it was simply missing even though I could indeed see it drawn over the waveform in the "non-lane" view (which is where the actual drawing of the curve took place).
To make this work, you draw the line in the actual automation lane; then automation works. ALSO, the line drawn in the automation lane does indeed get copied to the aforementioned Sequence Editor track's non-lane view after hitting enter.
So automation drawn in the sequence editor without showing lanes might not be happening sometimes? (i.e. It doesn't get copied to a lane properly?)
And that's because one needs to do the drawing of the automation in the track's respective lane-view instead?
Ok. Still seems weird though.