Arturia Minilab 3 Manual
Jovanna Ponder
Greetings. I am just getting into my Arturia minilab mkII midi controller. Never played any keyboards, acoustic nor electric before in my life. In other words, I'm about as ignorant as they come when it comes to this Arturia minilab.
So....my question is I am running it on Windows 10, 8gb of ram, 3.4 processor....and I open CbB to record a preset synth track from arturia analog lab 4 I get this from CBb when setting Preferences/midi/devices:
ummmmm....i think i figured this out....minilab comes with it's own preset plug-ins in analog lab 4 which are quite good....however, CbB and minilab are not set up to communicate this nor, apparently, allow CbB access to the plug-ins....i guess....who knows....the arturia minilab tech support forum website is a joke....almost a month of unanswered questions....i had a feeling it was going to be like this....?
i finally figured out how to get CbB to work with the Minilab....so simple once you know how....the latency was screwing me up as I'm used to things opening immediately....so, on to the music....????
Writing from memory (my... not RAM): computers are using numbers to report errors. And different libraries use the same numbers for own (so different) errors. If an error comes from one library but the text for it is asked using another, obviously the text has nothing to do with real problem. So, as I remember, standard code which corresponds to "not enough memory" is something like "device is busy" in one other library (I can't remember which exactly, I just remember the number clash). I will not go into details, but that particular case has no easy fix. That confusing message appears in many applications for many years...
I have an Arturia Minilab. When using Minilab knobs to record automation in logic x, the automation is not recording to automation lanes. the knobs are moving on screen, and changing the parameters of the sound (Filter cutoff ect) but the automation is not being written.
I move the knob on the Minilab that i have assigned for Filter cutoff on ES1 for example, i can see the filter cut off dial move on screen and can hear the sound being filtered, so the minilab knob is controlling the soft synth. all good upto this point.
So i try and record the filter cutoff movements by turning Automation mode to latch, then hitting play, then moving the Knob on my Minilab, the movements of the knob are not writing automation changes to the automation lane.
That can only mean that somehow when in record mode, the Minilab goes back to sending straight, unassigned MIDI messages. That's what normally happens when you send MIDI and press record: the data gets recorded in a region.
To determine if this is related to your Minilab, download the free Midipipe and use the attached document to make an assignment, then press Play and move the slider to see if automation is written OK.
Before making the assignment, take a second to check that the MIDI Out tool in the attached document has a valid output assignment (MidiPipe Output 1 will do, or an IAC bus if you have them enabled in your system)
Some days ago another Minilab user was having issues with it. In his case it was related to having the Minilab installed as a control surface. So, go to Logic Pro X menu > Control Surfaces > Setup and see if you have any control surfaces there you shouldn't have (the other Minilab user had a Yamaha 01V96 there). Delete anything you should have there, and while you're in that window, go to the "New" menu and uncheck "Automatic Installation".
Then I'm out of ideas. The behavior you're describing is not normal MIDI controller behavior. Some weird s#!+ going on there with that Minilab. Better check that manual or try to get help from Arturia or other Minilab users.
**In the 2 columns on the left, you'll see Control and Parameter columns. When you do the 4th step, the parameter column will be filled with the name of the parameter. When you do the 5th step, you'll see a message "Learned" in the Control column. It indicates that the parameter is signed).
Im having the same issue here.
when I move the knob ether on the minicab or the KorgNano control2 or my Keystation MINI 32MKIII... nothing. its moves the knobs on screen & you hear the effect of your actions but wont write the track automation. meaning that this can't be a MIDI issue & has to be a logic thing as its all working.