Hi Steve,
again many thanks for your last help. 
I have an additional question: Is it possible to let a fader of an audio mixer move slowly from one specific value to another (e.g. from -∞ to 0 db)? I am only able to define a value the fader should go to in no time at all.
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
Since this is a new question, I moved it to another topic.
Please find the attached.
There are 3 translators
fader-delay-2021-08-26.bmtp (1.6 KB)
Steve Caldwell
Bome Customer Care
Hello Steve,
thank you.
I am not a Pro and do not understand where to place “my values” into your translator. :-/
My goal is to press a keystroke and then a specific fader should slowly fade up to 0db from the actual position so it would go until “B0 01 66” for example. And with an other keystroke to -∞ that would be “B0 01 00” for example. The “B0 01” is the specific fader and the last to digits are telling the value of the fader. It should go from 00 … 01 … 09 … 0A … 0F … 66 for example.
I want to be able to copy this action for differents Faders and also different final values (the biggest possible value is 7F).
Do you know what I am looking for?
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
Hi,
This version uses buttons (I disabled the last preset with a knob).
Every fader will need its own timer name and global variables. I’m currently using:
fader-delay-2021-08-26a.bmtp (3.1 KB)
You will also probably need to change the what incoming triggers are to the buttons you will be using.
Steve Caldwell
Bome Customer Care
Sorry Steve, I do not understand where to past for example “B0 01 66” as my target position. And how can miditranslator recognize the current position? The Mixer is a QL 1 from Yamaha.
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
Well I used CC1 so you will need to change the output an probably the timer name to match so you don’t confuse yourself. The current position, initially is unknown, however is updated by the timer as it moves.
Steve Caldwell
Bome Customer Care
Still no plan. :-/
Could you please create me one complete preset with this “B0 01 66” as target for the outgoing midi message (and ESC-Button to trigger)?
Otherwise I will not be able to use your knowledge. 
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
OK Set the alias “:Output” to point to your target device.
Make sure that MT Pro does not have application focus. Focus on some other window otherwise it will not recognize your keystrokes
Up Arrow key will take it to value 102 (66 hex)
Down Arrow key will take it to value 0
fader-delay-2021-08-26b.bmtp (1.9 KB)
Steve Caldwell
Bome Customer Care
Hi Steve,
thanks for your help. It works nearly like wanted.
Only Problem: If the fader was moved manually to an different value, MD does not start moving from that “specific position” to the “wanted position”. It simply jumps to the “last known” position and then moves slowly to the “wanted position”.
Is there a way to “read out” the real fader position all the time and start from that value to move to the “wanted value” without jumping?
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
This is a matter of capturing the real position back from your device and putting it into the global variable we are using for the actual fader position. In this case, we just take CC1 value and put it into the global variable gc.
At the preset level I define the input port we use for feedback in a new preset… See snapshot and attached update project file:
fader-delay-2021-08-28.bmtp (2.2 KB)
Here are how I defined my port aliases.
Steve Caldwell
Bome Customer Care
Hi Steve,
it works now perfect for CH 1 of the Yamaha QL1.
I think it works for all the channels up to 24. :-))
But from 25 on, the commands seem to change. When I capture CH 25, i get for example “F0 43 10 3E 19 01 00 37 00 00 00 18 00 00 00 00 00 F7”
Can you please tell me how to translate these big codes?
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
If you can set up the log window to capture the fader movement from min to max, I may be able to figure it out. I suspect the 18 is the channel number which is 24 decimal which would be 25 if you start numbering from 0. The 00 pairs are likely the fader values which I would need to find a pattern unless you have the SyeEX manual for the device.
Steve Caldwell
Bome Customer Care
Hi Steve,
I atteched two screenshots (with CH 25 and MIX 1 as examples).
On page 281 ff. there seems to be kind of a Midi list for my Mixer:
I absoutly do not understand what is written there. :-/
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
You can try this. I’m kind of guessing at the SysEX command for fader 25
Right arrow should move the fader from current position to 0db
Left arrow should move fader from current position to infinity.
I also took a shot at fader feedback which should reposition the fader. Since the fader has better precision than a CC value, it may not be precise.
If you have a controller to manually move the fader (CC24) I have a translator for that too. It should convert CC value to SysEx value.
Make sure you define your aliases. I just used a Bome Virtual Port.
fader-delay-2021-08-28a.bmtp (4.4 KB)
Steve Caldwell
Bome Customer Care
Hi Steve,
in general it is working.
But the fader is jumping back and forward in steps everytime. I changed “tt=uu>>8” to “tt=uu>>7” (not knowing what that is). But after that change it seems smother, but the fader moves now a longer way.
I attached two videos.
Do you know what could be wrong?
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
(Attachment tt=uu–7.mp4 is missing) ago.
(Attachment tt=uu–8.mp4 is missing) ago.
Hi Steve,
in general it is working.
But the fader is jumping back and forward in steps everytime. I changed “tt=uu>>8” to “tt=uu>>7” (not knowing what that is). But after that change it seems smother, but the fader moves now a longer way.
I attached two videos and a screenshot.
Do you know what could be wrong?
BR
Alexander Muckenhirn
Gebhardstraße 13
76137 Karlsruhe
USt.-IdNr.: DE 232 040 066
Mob.: 0172 - 72 73 690
Hi,
Yes it is probably the calculations on how far to move the faders. Shift 7 is probably correct, >>7, however you will also need to adjust the value in the fader feedback. I’ve gone way over my time on free support here so reach out to me via email or PM if you need paid support on this issue. The basic concept is currently there.
Since there are two bytes value for the sysex, I have to combine them into one value before calculating the scaling.
See this video on scaling.
// This is a value greater than 128 so we need to shift the high order bits into a low order byte
tt=uu>>7
// now tt contains the high order byte
qq=uu&127
// no qq contains the low order byte
// on feedback we combine them again before scaling in the opposite direction
// this should probably be a 7 instead of an 8 too
//shift into high order byte with the bit shift operand
rr=tt<<7
// combine with the low order byte using the bit OR operand
qq=rr|qq
// now we can scale it back to the 8 bit value
…
Steve Caldwell
Bome Customer Care
Hi Steve,
thank you so much for your support.
tried with “7” also on the feedback and now it seems to work perfect.
So I will copy/paste the translators anch change the different variables for all faders.
Again - thanks.
BR
Alexander Muckenhirn
Glad to see you got it working. Documentation was too difficult to follow, however I could see pretty much what I needed to do based on your log information.
Steve
