Using Control as clip automation?

[braj]

Is it possible to assign the midi editor's 'Control' feature VST CC info? It already allows you to automate controller data on a per-clip basis, like volume, pan etc. Is there any way to map this to things like a synth's filters? I'm thinking we may already have clip automation and not realize it, though I'm not versed in this aspect of midi enough to know for sure. Anyone?

[djsubject]

yes its all there

just load your vst first & then open the midi mapper,

any parameter that can be automated in T can have a midi cc set to be its controller

[braj]

I think you misunderstood what I'm asking. I know about the regular controller mapping, I'm specifically talking about the 'Control' button the the midi editor, which allows you to select from a list various controllers, and then draw controller automation. This seems to work differently from the regular automation, but it is saved on a per-clip basis. What I'm not sure of is if/how you can use this to automate something like the filter of the Pro-53, for example.

[djsubject]

Sorry braj i still dont understand what you are asking?

but it is my birthday & i'm verry stoned

EDIT: ok i got it now!!

to do this you would have to wrap your vsti in E-XT, or somthing else that lets you do this

[P.T.]

Try the small "A" in the uppper right corner of the track. All of the automatable parameters are listed there.

[pHz]

I think you misunderstood what I'm asking. I know about the regular controller mapping, I'm specifically talking about the 'Control' button the the midi editor, which allows you to select from a list various controllers, and then draw controller automation. This seems to work differently from the regular automation, but it is saved on a per-clip basis. What I'm not sure of is if/how you can use this to automate something like the filter of the Pro-53, for example.

seems like it SHOULD work but only if you could tell the instrument listening to the controller data which parameter it should be affecting ...

... having said that ive just tested it by using the new MIDI controller mapping to attach CC#25 to impOSCars filter frequency and then drawing a curve for cc#25 in a MIDI clips control area ... this clip then outputs to impOSCar but even though the plugin is hearing CC#25 (i know this since tweaking the knob on my x-session affects it) it ISNT picking it up from the MIDI clip for whatever reason ...

... but this WOULD be a VERY easy way to have clip automation if there was some way (other than modulrs CC-rider ??? ) to link the curves to filter parameters ...

... BTW ... for those watching the clip automation thread this is pretty much how id expect that to work too (kind of based on the ableton live model) ...

slainte rob

[IIRs]

What I'm not sure of is if/how you can use this to automate something like the filter of the Pro-53, for example.

Of course! This is what CCs were invented for! It is up to the synth in question to assign controllers to parameters however: some synths will ignore them completely, others will have a fixed implementation (so you may need to consult a chart to see what controller the filter cutoff is linked to), while others allow free assignment of any controllers to any parameters, or even a "MIDI learn" option..

If a synth has a fixed assignment, it might stick to certain conventions (eg: cc 1 = "modulation" (vibrato depth) and cc 74 = "brightness" (filter cutoff)..

[djsubject]

... but this WOULD be a VERY easy way to have clip automation if there was some way (other than modulrs CC-rider ??? ) to link the curves to filter parameters ...

slainte rob

i thought cc-rider worked the other way round

[pHz]

probably does ... never used TBH ...

slainte rob

[pHz]

dunno though ...

CC-Rider has two funtions. It can use VST automation parameters to transmit Midi-CC's. It can also record midi-CC's to create VST automation curves. This is particularly useful in Tracktion, who's CC editing is less than ideal.

slainte rob

[djsubject]

dunno though ...

CC-Rider has two funtions. It can use VST automation parameters to transmit Midi-CC's. It can also record midi-CC's to create VST automation curves. This is particularly useful in Tracktion, who's CC editing is less than ideal.

slainte rob

you mean it was there allways

i havent used this in e-xt in a song becouse i only have the demo & it wont save the settings (witch i dont blaim them atall)

thanx for that rob



edit: mod? has this been updated since i tested it a few months ago?

if not then

[pHz]

just tested it myself ... once you actually read the readme and suss how it works it does the CC > automation thing pretty well although it does take a few clicks to do the conversion and apply it to a filter parameter ...

... so with a fair amount of working around we DO already have clip automation ... sort of ...

slainte rob

[valley]

the Tracktion CC mapper only works on incoming MIDI.

Even if it could respond to clip level CCs, it wouldn't be a great deal of use because it doesn't differentiate between MIDI channels or inputs, so you'd get in a mess pretty quickly.

Clip level automation curves are the only elegant way forward at this point.

[braj]

Oh well, it looked like it was a solution