Is there a way to see in Mulab where all automations are applied?
Now i must go in the editor to see that here is automation curve
Sometimes there is a subtrack under the midi track to show the automations and on this way is easy to follow what is done there
Automations where to track down in project
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
I am trying now to get a meta parameter (gain bass2) in the automation lane under the notes in the editor...intuiatieve... drag the parameter on the name slot .. but nothing happens
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Are you sure you are dragging the right thing, can you post a pic of what you want and where?janhardo wrote:I am trying now to get a meta parameter (gain bass2) in the automation lane under the notes in the editor...intuiatieve... drag the parameter on the name slot .. but nothing happens
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
Thanks bibz1st,
I thought there was parameter dragging and dropping in Mulab? ... its about a to getting a metaparameter automation lane in the editor
I must look again first to a trainings video...
I thought there was parameter dragging and dropping in Mulab? ... its about a to getting a metaparameter automation lane in the editor
I must look again first to a trainings video...
-
- KVRAF
- 1925 posts since 29 Mar, 2013
There is and its very easy, make sure you are not dragging the knob, instead drag the name or value onto the new "track" area
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
The drag and drop feature seems to only for the composerscreen, while i was in de editor window ..there you must choose a parameter from a list ..or even construct a new parameter one..this new one to choose could be done by drag and drop to in the editor ?
-
- KVRAF
- 1925 posts since 29 Mar, 2013
The following are both done using the basic synth patch
You can even do it straight from the front panel Is that what your looking to do ?
You can even do it straight from the front panel Is that what your looking to do ?
You do not have the required permissions to view the files attached to this post.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
Yes, also in the composerscreen what have showned here..drag and drop ..easy ..thanks.
It als possible to automate parameters in the midi editor under the notes
It seems to be better to automate in the composerscreen to see the whole picture
Why i should automate in the midi editor...?
It als possible to automate parameters in the midi editor under the notes
It seems to be better to automate in the composerscreen to see the whole picture
Why i should automate in the midi editor...?
-
- KVRAF
- 1925 posts since 29 Mar, 2013
I guess the answer would be try and use automation lanes where possible, better resolution and curves
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
Yes ..a closer look is neccessary to make a comparison, but there is no parameter drag and drop in the midi editor..i check it.
I am also stuck with the vst midi drone from the composer(important for the connection of the composer and mulab).. i need that thing working for 16 midi channels
But it has now 4 ..must i use mutltiple midichannels on 1 midi channel ? ..in Cubase i get 16 midichannels with a the composer drone.
I am also stuck with the vst midi drone from the composer(important for the connection of the composer and mulab).. i need that thing working for 16 midi channels
But it has now 4 ..must i use mutltiple midichannels on 1 midi channel ? ..in Cubase i get 16 midichannels with a the composer drone.
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
A midi drone is a Vsti device what can be installed on a host DAW to receive midi data ( the arrangement screen in the composer can be connected to midi channels in the DAW with Vsti or native soundmodules )
On this way the composer program can use mixing capabilities and audio from the DAW, when the arrangement(song) in the composer is ready enough..the midi data can be drag and dropped to the DAW.
It seems that when i installed the Vsti drone in Mulab i only can connect 4 racks, but i has 16 audio outputs in the modular editor.
On this way the composer program can use mixing capabilities and audio from the DAW, when the arrangement(song) in the composer is ready enough..the midi data can be drag and dropped to the DAW.
It seems that when i installed the Vsti drone in Mulab i only can connect 4 racks, but i has 16 audio outputs in the modular editor.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Are you refering to these
You do not have the required permissions to view the files attached to this post.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRist
- Topic Starter
- 203 posts since 26 Sep, 2014
Yes, those two ..how to get this..i will look again
Another question: how to remove a existing controller parameter curve in the midi editor ( fine automation)
Because i am working with the composer and mulab i transer also the automation , but it went wrong so i must remove all controller data assigend to wrong parameters.
The rebuild from the demo song pure in the composer went very well, but the last fifth rack has a wrong automation and there is no sound ..i am stucked at this last rack
I drag the midi from the composer to mulab for rack5 leads ( via midi drone in Mulab installed) and copied the parameter curves, but assigning the right parameter i do not master yet.
This all is a sort of training to know all automations handling in Mulab.. i don't get a grip on it yet
The whole idea of the composer and Mulab is to use mididrones from the composer in Mulab.. then i can connect on the midi tracks in the composer the racks in Mulab
Then i export a midi from mulab and import this in the composer ..but that is only midi...there is also automation data from mulab what must be transferred to the drone setup ( composer + mulab connected)
I tried the demo song Pure to make this in the composer, but get stuck, due also not knowing exactly how to automate and probably the wrong drone setup in Mulab.
Another question: how to remove a existing controller parameter curve in the midi editor ( fine automation)
Because i am working with the composer and mulab i transer also the automation , but it went wrong so i must remove all controller data assigend to wrong parameters.
The rebuild from the demo song pure in the composer went very well, but the last fifth rack has a wrong automation and there is no sound ..i am stucked at this last rack
I drag the midi from the composer to mulab for rack5 leads ( via midi drone in Mulab installed) and copied the parameter curves, but assigning the right parameter i do not master yet.
This all is a sort of training to know all automations handling in Mulab.. i don't get a grip on it yet
The whole idea of the composer and Mulab is to use mididrones from the composer in Mulab.. then i can connect on the midi tracks in the composer the racks in Mulab
Then i export a midi from mulab and import this in the composer ..but that is only midi...there is also automation data from mulab what must be transferred to the drone setup ( composer + mulab connected)
I tried the demo song Pure to make this in the composer, but get stuck, due also not knowing exactly how to automate and probably the wrong drone setup in Mulab.