Hi, I need some help. I tried to map a knob of my Axiom 49 to control a parameter of an istrument in mu.lab.
For example CC74 (knob2) to control Brightness of a Wurli piano.
This is what I did:
If I create an automation sub-track and choose "Wurli w Speaker-- Brightness" and then write an automation by pencil tool on the clip the wurli parameter moves following automation.
If I right click on Brightness knob on instrument interface --> Map Midi controller --> Source CC74 - Filter Env as Target Module - Decay Level as Parameter. The knob on the wurli was supposed to move in real time as I move the controller on the keyboard, but nothing happen. If I record the sequence nothing happen.
How can I map controller and record the automation on an automation track?
What was wrong?
Is there a tutorial about master keyboard controller mapping?
Many thanks,
Gabriele
Master Keyboard MIDI Controller Mapping
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
The Decay Level does not control the Brightness, that's why you don't see the Brightness knob change while the automation is played back. These are two different parameters.
That said, i noticed that there is a problem with the Wurly patch, i'll check that asap. Normaly it should be as simple as right-click knob -> Map MIDI Controller -> click OK. But with this Wurly patch the parameters themselves (eg Brightness) don't show up in the Map MIDI CC dialog. Will research.
That said, i noticed that there is a problem with the Wurly patch, i'll check that asap. Normaly it should be as simple as right-click knob -> Map MIDI Controller -> click OK. But with this Wurly patch the parameters themselves (eg Brightness) don't show up in the Map MIDI CC dialog. Will research.
-
- KVRian
- 731 posts since 25 Oct, 2008 from Holland
I understand that MUlab is capable to make a video record ? : muvieNonno wrote:nothing happen.
How can I map controller and record the automation on an automation track?
What was wrong?
Is there a tutorial about master keyboard controller mapping?
Many thanks,
Gabriele
Or do i don't understand it?
Perhaps someone can make a user tutorial, because automation seems to be not documented by a videotuterial ( only externa; via Johny Pumphandle )
Well the same seems to be for the modular editor (MUX), there is no video tutorial from users where they show their modular setups for compositions.
-
- KVRian
- 855 posts since 3 Mar, 2009
Automation with the Wurly works fine here.
I can't see anything wrong in what you did.
And, btw, Brightness IS working on Decay Level (Filter Env inside the PolySynth). So, there's nothing wrong here.
When i focus on a different track than the Wurly, i can't see my external controller moving the Brightness of the Wurly. I recorded anyway, which created a sequence on my drum track. Inside this sequence is the automation for the Wurly! Moving that sequence onto the Wurly track made the Brightness moving.
These automation data are created in a midi sequence, which can be viewed in the piano roll editor. Click on where is usually says "All Notes" and select from the top of the list "Wurly [your controller name] Decay Level"
One more thing: If you have created an automation track with a curve inside, this will fight with the recorded automation data in the sequence. So, you should decide what you want to use, recorded automation (as CC) or automation parts.
I can't see anything wrong in what you did.
And, btw, Brightness IS working on Decay Level (Filter Env inside the PolySynth). So, there's nothing wrong here.
When i focus on a different track than the Wurly, i can't see my external controller moving the Brightness of the Wurly. I recorded anyway, which created a sequence on my drum track. Inside this sequence is the automation for the Wurly! Moving that sequence onto the Wurly track made the Brightness moving.
These automation data are created in a midi sequence, which can be viewed in the piano roll editor. Click on where is usually says "All Notes" and select from the top of the list "Wurly [your controller name] Decay Level"
One more thing: If you have created an automation track with a curve inside, this will fight with the recorded automation data in the sequence. So, you should decide what you want to use, recorded automation (as CC) or automation parts.
-
- KVRian
- 855 posts since 3 Mar, 2009
Reading your post more closely, i see that you are not targeting Brightness, but the actual parameter 'PolySynth/Filter Envelope/Decay Level'.
This means that your automation will not move the Brightness knob on the Wurly user interface, but the parameter inside. Open the envelope and Decay Level moves.
There is one problem with this: Brightness is set from 0..100. If you just take the default values for the Decay Level automation, your automation is scaled from -100 ...+100, which gives a good chance that you close the filter even more.
I would propose you just right click on the Brightness parameter, select "Map Midi Controller" and wiggle you external controller for the assignment. Nothing more to do! It will automate Brightness and scale correctly.
This means that your automation will not move the Brightness knob on the Wurly user interface, but the parameter inside. Open the envelope and Decay Level moves.
There is one problem with this: Brightness is set from 0..100. If you just take the default values for the Decay Level automation, your automation is scaled from -100 ...+100, which gives a good chance that you close the filter even more.
I would propose you just right click on the Brightness parameter, select "Map Midi Controller" and wiggle you external controller for the assignment. Nothing more to do! It will automate Brightness and scale correctly.
-
- KVRist
- Topic Starter
- 34 posts since 20 Mar, 2012
Not for me, unfortunately. I can't see anything moving!AndreasD wrote:Automation with the Wurly works fine here.
I can't see anything wrong in what you did.
yes, I check it on "right clic on automation track icon - Edit Meta Parameter Map" and I saw that brightness is target on "Filter Env Module" and that the parameter is "Decay Level"AndreasD wrote: And, btw, Brightness IS working on Decay Level (Filter Env inside the PolySynth). So, there's nothing wrong here.
How to focus? Just clic on the track?AndreasD wrote: When i focus on a different track than the Wurly,
-
- KVRist
- Topic Starter
- 34 posts since 20 Mar, 2012
I think I don't understand ...AndreasD wrote:Reading your post more closely, i see that you are not targeting Brightness, but the actual parameter 'PolySynth/Filter Envelope/Decay Level'.
This means that your automation will not move the Brightness knob on the Wurly user interface, but the parameter inside. Open the envelope and Decay Level moves.
There is one problem with this: Brightness is set from 0..100. If you just take the default values for the Decay Level automation, your automation is scaled from -100 ...+100, which gives a good chance that you close the filter even more.
This is much easier and faster and it works.... with all instruments expect Wurli... it still doesn't work...AndreasD wrote: I would propose you just right click on the Brightness parameter, select "Map Midi Controller" and wiggle you external controller for the assignment. Nothing more to do! It will automate Brightness and scale correctly.
Many many thanks...
For me it's very important to know the software very well since I have to show it to my students and to persuade that it's a good DAW to buy at a cheap price.
-
- KVRian
- 731 posts since 25 Oct, 2008 from Holland
You can automate by drawing or midicontrollers: (inside noteroll editor ) or by recording (outside in composingscreen: automatic added a subtrack by moving a knob or add a subtrack manual and use a midi controller: map midi controller. i don't know how to use the pencil tool on the automation track in the composerscreen ?)
Well drawing and recording ( with midi controller or by moving knob ) automation curves in both the note roll editor and the composingscreen should be logical?
Focus a knob or rack as example is to click on it that it shows a yellow border around the knob or rack.
So i loaded the wurli in a rack and record the Brightness knob by moving this by hand... a automation track is added by Mulab with the brightness knob moving
if a replay it after the recording.
Now you want automate this brightness knob with a midi controller keyboard ?
Indeed there is no tutorial about automation in MUlab 4 and that is because MUtools gives no priority to this.
But i read something about a "muvie" a videorecorder inside Mulab? ..so user canmake their own video within MUlab ?
Well drawing and recording ( with midi controller or by moving knob ) automation curves in both the note roll editor and the composingscreen should be logical?
Focus a knob or rack as example is to click on it that it shows a yellow border around the knob or rack.
So i loaded the wurli in a rack and record the Brightness knob by moving this by hand... a automation track is added by Mulab with the brightness knob moving
if a replay it after the recording.
Now you want automate this brightness knob with a midi controller keyboard ?
Indeed there is no tutorial about automation in MUlab 4 and that is because MUtools gives no priority to this.
But i read something about a "muvie" a videorecorder inside Mulab? ..so user canmake their own video within MUlab ?
-
- KVRian
- 855 posts since 3 Mar, 2009
Here (http://dl.dropbox.com/u/62409608/Automa ... roller.wmv) is a short video about automation with an external controller (CC73 here).
My first! So, please bare me the missing overdub/text. I have no means to edit movies. Neither have i ever uploaded to YouTube.
I hope it will clarify how things work.
How to make a video:
Assign a shortcut to "Mulab Application->Toggle App Movie Recording"
This key will then start/stop recording. The Mulab window will resize to 1280x720 px.
Files are found in Mulab/User/Appmovies
My first! So, please bare me the missing overdub/text. I have no means to edit movies. Neither have i ever uploaded to YouTube.
I hope it will clarify how things work.
How to make a video:
Assign a shortcut to "Mulab Application->Toggle App Movie Recording"
This key will then start/stop recording. The Mulab window will resize to 1280x720 px.
Files are found in Mulab/User/Appmovies
-
- KVRian
- 731 posts since 25 Oct, 2008 from Holland
I cannot find this ?AndreasD wrote: How to make a video:
Assign a shortcut to "Mulab Application->Toggle App Movie Recording"
This key will then start/stop recording. The Mulab window will resize to 1280x720 px.
Files are found in Mulab/User/Appmovies
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
If you have installed M4.1.4 or M4.1.5, then goto main MuLab menu -> Edit Shortcuts and create a shortcut to "Toggle App Movie Recording". It must be there. More details on http://www.kvraudio.com/forum/viewtopic ... 05#4853405janamdo wrote:I cannot find this ?AndreasD wrote: How to make a video:
Assign a shortcut to "Mulab Application->Toggle App Movie Recording"
This key will then start/stop recording. The Mulab window will resize to 1280x720 px.
Files are found in Mulab/User/Appmovies
The docs will be updated soon on releasing M4.1.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Nonno, about the Wurly patch MIDI CC mapping problem: Please install the newest version M4.1.5 from http://www.mutools.com/mulab/cedar
If you're currently using M4.0.115, then make sure to install the full new package. To keep you current user settings, see http://www.mutools.com/mulab/docs/installation.html
In M4.1.5 the MIDI CC mapping problem should be gone.
If you're currently using M4.0.115, then make sure to install the full new package. To keep you current user settings, see http://www.mutools.com/mulab/docs/installation.html
In M4.1.5 the MIDI CC mapping problem should be gone.