Dcommand doesn't write C4 automation with Preview

[Moviesound]

Anyone come across this....

I'm writing automation in preview with the Dcommand using Waves C4.I print automation using 'Write automation to selection' I am using a custom map and alot of the time it doesnt actually write the previewed settings.

If I use the DYNAMICS panel to control C4 it almost never writes the automation.

Any ideas?

[Drew Mazurek]

Almost never? Sounds weird.

Plugin Auto is enabled right?
The parameters are enabled right?
Can you draw it in and it'll playback?

[Moviesound]

Yes, works fine using the mouse. Dcommand changes settings while in preview but doesn't write them when write to selected?

[jmattchan]

just tried it on our d-control from the dynamics and eq sections and it seems to be working ok so it may be a d-command specific problem.

[Moviesound]

So just to verify that I have a dodgy Dcommand. Can someone confirm that they can control Waves C4 with the dynamics section of a Dcommand?

Although mine actually does map and control the plugin parameters. Protools never actually recognises this as a change of automation, by having the 'automation type' turn green under the track name in the edit page.
Other plugins seem fine??

[Hanswurstlsepp]

Originally Posted by Moviesound

So just to verify that I have a dodgy Dcommand. Can someone confirm that they can control Waves C4 with the dynamics section of a Dcommand?

Hi,
C4's Master parameters (Threshold/Gain/Range/Attack/Release) are generally not automatable. Unfortunatelly, those are the parameters which show up on the D-Command's dynamics section. I think Waves has to update this because afaik a user can do nothing against it.

The only 2 parameters which are automatable assigned to the dynamics section, are Knee and Output.

C4's EQ parameters are showing up on the D-Command's EQ-section and are all automatable.

It's of course the same if I use the C4 in the Custom Fader section (Custom Fader Channel Encoders .... to be more precise).

But - I can "control" the C4s MasterParameterValues which are showing up within the D-Command's Dynamics section .... to refer to your quote

[Moviesound]

Thanks Steff,

Interesting. So you say 'I can "control" the C4s MasterParameterValues which are showing up within the D-Command's Dynamics section'

I can control these but not write as automation. i.e. the dynamics section moves these parameters but when in preview the 'auto type' doesnt turn green, therefore I cant write automation.

Using the mouse these master controls can be written. So surely its a dcommand fault, not Waves. Is this the same your end?

[Hanswurstlsepp]

Originally Posted by Moviesound

Thanks Steff,

Interesting. So you say 'I can "control" the C4s MasterParameterValues which are showing up within the D-Command's Dynamics section'

I can control these but not write as automation. i.e. the dynamics section moves these parameters but when in preview the 'auto type' doesnt turn green, therefore I cant write automation.

Using the mouse these master controls can be written. So surely its a dcommand fault, not Waves. Is this the same your end?

It depends on if the individual parameters (like Band) controlled by the Master section of the C4 are automation enabled or not.

For instance, if you have all automatable parameters automation enabled, then of course it will work with the mouse, as this points directly to the individual parameters of theses controls.

But if you look into the Plug-In Automation Window where u can find all automatable parameters, you won't find a dedicated parameter entry for Master-Threshold, Master-Gain, Master-Range and so on.

And that's exactly where IMO the culprit is burried

[Hanswurstlsepp]

Originally Posted by Moviesound

So surely its a dcommand fault, not Waves. Is this the same your end?

Well I donno if it's a D-Command fault or a Waves fault. All I know is, that we (as users) can do almost nothing against it. I think it's a question of how the PlugIn's parameters themselves are organized for automation purposes.

Question is next, if it works with mouse, it should of course work with the D-Command too. But is the parameter flow/design of the D-Command same as if u touch a parameter with the mouse within PT-SW ?

And yes, it's the same here. I didn't try with preview, just checked directly with write & latch. But if it won't work with write/touch/latch themselves then of course it won't work with preview either

[Moviesound]

Thanks Steff. Yes you're right, thats what it will be. Still strange though how one can automate something with the mouse and not the Dcommand.
Thanks for putting my mind at ease. Digi claimed it worked at their end!