The aim of the project is to give Mackie C4 owners the possibility, to create things on their own. This midi controller is not well documented and if your software does not support it, you will be doomed, especially if you are on Mac OS. On release, there was once a software called ‘Total Commander’ with which you could do remote panels easily, but this software has several downsides. It does not work anymore on any newer Mac OS (i think Intel-Macs where the last ones). It does not support bi-directional work, so a panel cant react to program changes of the hardware for example. It also supports only one-time actions, so you cant use the push and turn function of a Vpot together, only one of these per Vpot and last but not least, it only works with a PC of course. . This midi controller is capable of so much more. With Bome MTP and this project, you will have full control over it AND are not limited to these restrictions. In combination with a Bome Box, you dont even need a PC anymore or do a Live act, only with your hardware.
This early version has only 32 Vpots, because before i move to the next page for another 32 Vpots, i want to solve some problems first. Once the first page is finished, a user can create a panel for another synth on his own, because this project will deliver any relevant infos and documents to do so.
I will post any future updates for this panel in this thread.
So for the remaining last Vpots on the first ‘page’ of the panel, i would like to have a gimmick for the LFO Speed/Rate. The A-Station has a small LED for it. This LED blinks in time at the speed of the LFO. I would like to do the same on the Mackie C4 with MTP. How would you approach to do this? It needs a timer that is bound to the amount of the LFO speed and triggers a on/off state for the led(segment).
Thanks in advance, . A better introduction to this topic, will follow later.
Hi, we would need to capture the value of the global variable that contains the current LFO speed and then set a repeating timer at a calculated interval based on that value. Is the LFO speed represented by a 128 (7 bit) or 16383 (14 bit) CC. An example of a given value and associated blink rate would also help to figure the calculations needed.
I don’t see anywhere in your project where you document the global variables that you are using and what they are used for. I guess you are tracking them somewhere else.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
LFO 1 and LFO 2:
Waveform Sample & Hold / Tri / Saw / Squ
Speed 0 Hz – 1Khz
Delay Fade In 0 – 5 Seconds
LFO Sync Internal – MIDI Clock
Speed is set by CC 80 and range 0-127 for the NON-SYNC LFO1 SPEED, which is the one i want to experiment first. I know this can only be a approximation, but i would like to have it anyways. I will experiment to come close to the hardware ;). The original can only blink and has no dimming. Full on or off so to say.
I am sorry, but they are inside the preset ‘Outgoing Values from A-Station’ in a Translator that is the first in the list, called ‘Novation A-Station Global Defs’. Maybe not the best place to be . Currently there is no global for the LFO speed, but g6, g7 is the desired one. Thanks for looking into this.
Zero is off and 127 is so fast, you cant really tell if it is blinking or just on.
For the smaller gif, i did cut off the ‘turned’ off part, but you can see how long the duration for the ‘on’ part is. The ‘off’ part has the same duration.
For the note number, it would be the best to use aany LED segment of the Vpot Ring. Best would be the pdot of the ring (the one that is on the center bottom 40 in hex).
OK, I’m not going to mess with your project so I attached and example.
This works with the first VPOT of MCU controller.
I calculate the CC value and send the CC 80 in translator 0.0.
I call Perform ‘Blink’ in that translator which is translator 0.1.
I used g6 to store the value
Perform Blink (Translator 0.1) calculated the blink rate and calls a repeating timer. If the blink rate is less than 100 ms or over 1000 ms, then I call Perform Stop (translator 0,2) and otherwise do nothing with the timer. If it within range it starts a repeating timer at the currently calculated rate.
The timer, actually turns on and off the LED toggling it (using global variable g7).
Blink stop (Translator 0.3) kills the timer and calls Perform ‘LED’ with the parameter for either on or off.
Translator 0.4 either turns off or on the LED when the timer stops.
I use aliases instead so that if port names change I just re-assign the alias.
Thats great, i will try that out. Thanks to your help, today i did found out how the meter leveling works on the Mackie C4. It was the last and only thing, that i could not setup on the Mackie C4 for years. Your patience with me and explaining the hex>binary>bit thing, helped me to understand the midi-implentation of the MCU and how to activate that meter leveling. Cant tell you, what a relief that find out is to me. This project was a good choice to learn these things and how great MTP is.
I wish you a very nice weekend. Again, many, many thanks for all that help and i will give my best to implement the LFO blinking
,
;). The original can only blink and has no dimming. Full on or off so to say.
