could anyone tell me why I cant record automation?

Audio Plugin Hosts and other audio software applications discussion
RELATED
PRODUCTS

Post

well I've tryed it with the regular Cubase plugs like a1, monologue

Post

check the manual for the section on generic remote control, it's a while since i've played with SX - but I remember that you can set your generic remote contoller to control vsti's etc. & record it as track based vst automation rather than midi cc data within the particular midi clip.
From what I recollect though it is a bit of a faf.

Post

well I think thats not the problem, cause the knobs on the MIDI are recording when I do a record with '*' button

Post

by the way, the GM map shows keys only, not knobs

Post

anyway thank you all

Post

metalball wrote:by the way, the GM map shows keys only, not knobs
Didn't you read my post?

Post

device setup > genric remote control (if it isn't there click the add/remove tab & select 'generic remote control device' from the list & then click 'add' > click the 'setup' tab & select the 'generic remote control device' > select the correct midi input port > on the upper table that is displayed select the control you want to use (which fader/knob channel & midi cc > on the lower table select which parameter you want that particular knob to control.
I gleaned this from the SX2 PDF, i'm no expert though as I don't personally own/use SX & only come into contact with it every now & again.
As far as i remember if you have a vsti in your project when you are choosing devices from the lower pane the vsti's in use in the project are listed & you can then select various automatable parameters for that device.
If I am incorrect I apologise, but this should at least point you in the right direction if you are asking the question i believe you to be asking

Post

dude if you are using A1 you don't need GRC....read page 87 of the audio-fx and VST pdf. It explains exactly how to do it.
If you have to ask, you can't afford the answer

Post

diverdee wrote:device setup > genric remote control (if it isn't there click the add/remove tab & select 'generic remote control device' from the list & then click 'add' > click the 'setup' tab & select the 'generic remote control device' > select the correct midi input port > on the upper table that is displayed select the control you want to use (which fader/knob channel & midi cc > on the lower table select which parameter you want that particular knob to control.
I gleaned this from the SX2 PDF, i'm no expert though as I don't personally own/use SX & only come into contact with it every now & again.
As far as i remember if you have a vsti in your project when you are choosing devices from the lower pane the vsti's in use in the project are listed & you can then select various automatable parameters for that device.
If I am incorrect I apologise, but this should at least point you in the right direction if you are asking the question i believe you to be asking
well if it's sx3 the nice people at moobase managed to leave things like the a1 out of the generic remopte menu - so you can't use that (and yes i know how shoddy that sounds)
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

ericj23 wrote:
diverdee wrote:device setup > genric remote control (if it isn't there click the add/remove tab & select 'generic remote control device' from the list & then click 'add' > click the 'setup' tab & select the 'generic remote control device' > select the correct midi input port > on the upper table that is displayed select the control you want to use (which fader/knob channel & midi cc > on the lower table select which parameter you want that particular knob to control.
I gleaned this from the SX2 PDF, i'm no expert though as I don't personally own/use SX & only come into contact with it every now & again.
As far as i remember if you have a vsti in your project when you are choosing devices from the lower pane the vsti's in use in the project are listed & you can then select various automatable parameters for that device.
If I am incorrect I apologise, but this should at least point you in the right direction if you are asking the question i believe you to be asking
well if it's sx3 the nice people at moobase managed to leave things like the a1 out of the generic remopte menu - so you can't use that (and yes i know how shoddy that sounds)
You don't NEED the GRC for A1, it has full MIDI assign capability. READ THE f**king MANUAL, and quit blaming Moobase because you don't know wtf is going on.
If you have to ask, you can't afford the answer

Post

Sorry I thought the dude wanted to automate vsti's parameters using a control surface/keyboard & record it as vst automation & not as midi cc automation.
If i gave him incorrect info. I apologise, as I said I don't use SX, but i did help a friend sort this type of business out when he found it a little confusing.
For the record in my very humble opinion the method SX uses for this is a little convoluted compared to hosts like say Ableton Live (my host of choice), reason or Tracktion2, but obviously SX does have some deep midi business going on - so i'm not knocking it per se, just echoing what I have seen many users state on the official steiny forums.

Post

could you give an example of a VSTi that I could "plug" my MIDI into??
impOSCar would be a good one to check it out with. It has a demo, it also has a very straight-forward midi CC implementation. It also happens to scream like a bastard as well.

Post

You can automate VST that have MIDI CC support from a controller or keyboard without using the GRC to create either MIDI automation lanes or VST automation lanes. You only need the GRC for VSTs that don't have built in CC maps.
If you have to ask, you can't afford the answer

Post

SJ_Digriz wrote:You can automate VST that have MIDI CC support from a controller or keyboard without using the GRC to create either MIDI automation lanes or VST automation lanes. You only need the GRC for VSTs that don't have built in CC maps.
That's right.
But his problem is more, that he dosn't know anything about how to forward MIDI to a MIDI enabled VST. He obviously mixed up (is confuused about) the standard VST automation and common MIDI automation.

That's the problem with many beginners (even if they never used real MIDI equipment).

They often don't realize, that a VSTi is basicly an MIDI instrument driven by MIDI information, which has it's own Audio channel inside the host application and the additional possibility to use VST automation on that VST channel.

Two different shoes. Different solved with several different hosts.

Once understood, it is a snap. And many users surely will prefer MIDI rather than cumbersome VST automation (At least for live performances).

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”