To access, the channel strip module settings, press the DYN/FX/AUX button in the ASSIGNMENT section.
according to instructions in MCU map:
DYN
Position left/right 1,
Position up/down 3,
MIDI “note” A2,
value/On 127,
value/Off 0,
Channel 1
the point is, understand how to program all other stuff to make template for my APCmini (should be used to control channel strip)
Hi and welcome to the forum. To me the position just looks like the position of the button on the Mackie MCU device where left/right is column and up/down is row and doesn’t have any bearing on programming your APCMINI. The note names are not very useful as different people use different octaves in the note naming system. The note number in question start with 0x28 (Decimal 40). Some Mackie MCU’s call “Dyn” “Instrument”
So for instance to change to instrument mode, send note-on note number 0x2d (45 decimal) value 0x7f (127 decimal) Cubase should light the LED when the button is pushed and should extinguish it when another button on the strip is pushed.
Do a web search on “Logic Contro;l Macke”. You should find a document which is more meaningful and will show you note number (in hex) instead of note names.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thank you Steve, Looks like i found that manual.
Now other problem, i can’t find V-Pot 1-3 CC (some info in internet says its 32,33,34)
Here manual from Cubase
Now what i get inside BMT
looks like everything correctly, and Cubase shows midi activity, but nothing is happened.
Btw, i assign Bank select, transport buttons and it works
Rotation of V-POTS is different than V-POT push. The APC MINI does not have VPOT push so for that I suggest you use the top row buttons for that.
For V-Pot rotate, you will either need to change the faders to look like V-POTs or have another controller to do this. I suggest you use one of your right buttons (maybe the one under select. To change presets so that while select the sliders become virtual knobs. It will be a bit tricky since your APC MINI sliders are not continuous.
The V-POTs of a Mackie MCU controller send hex B0 1x yy. Where x is the V-Pot number (0-7) and yy will be 01, 02 ,03 etc for right turn 0x41, 0x42 , 0x43 etc for left turn.
So when changing to the preset for V-Pots you will likely want to have another button to let you center the fader without sending anything while pushed, (next button down?) then center the fader, release the button and then move the slider up or down depending on direction.
Basically the conversion from absolute to V-POT would look like this. You will need a different global variable for each slider. This would be for V-POT 1
Incoming: Midi B0 30 qq
Rules:
// Determine whether it is right or left we
// we use ga for global variable here but each will need their own global variable to track the
// last known position
if pp>ga then tt=1
if pp<ga then tt=0x41
// update ga for next iteration
ga=pp
// Look to see if suppress button is held down (a different translator using gi)
if gi==1 then exit rules, skip outgoing action
Outgoing : Raw MIDI B0 10 tt
You suppress translator should set gi to 1 when pressed and gi to 0 when released
Yes, that should work. You will just need to see what the incoming messages are and target your translators, or parent preset to only look at the Axiom 40 for input. There may be some translation differences depending on what your Axiom sends. If it has a relative mode, you will not need to use any global variables but just convert the incoming left/right messages to the proper Mackie left/right format.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks Steve for help! I finally figure out how to activate it!
i should sent to Cubase:
Note on 45 vel 127
CC16 value 1
Note on 49 Vel 127
CC18 value 1
and if i send it 1by1, everything ok, but when i assign 1 button for all this commands in BMT, cubase can’t activate it.
Probably solution is in, put delay for each sended message. How to properly implement it in BMT ?
There are 5 translators. The first translator sets up a global variable ga to determine the amount of delay between steps. In this case I used 10ms but if you want to change it you can change it there in one place.
The outgoing message is a 1 shot timer named “CH_Strip_Module” which fires the other 4 translators.
The second translator sets the local variable pp to 0 since local variable values are undefined until you set them. Since the translators use the same incoming trigger, pp can be shared between the translators using a local variable.
It sends the first MIDI message with delay of pp (0). This is a nice an often overlooked feature of MT Pro. Normally local variables are private but only private to a given incoming trigger. Since translators 2-5 share the same incoming trigger, they can also share the local variable pp, thereby not having to consume another global variable.
Each of the other translators increments pp by a value of ga (10) and sends out their MIDI message with the additional delay by the rule “pp=pp+ga”.
I set the incoming alias as “My Controller” which points to my FaderFox EC4. You will need to change that to your controller. You will also need to change the incoming trigger message to whatever you want to send but you only have to do that in the first translator since I’m using the same timer for all of the other outgoing message. In my case I set the output alias to “Cubase” which I point to Bome MIDI Translator 1 Virtual port.
