Midi translator

Hello, I am using the bome midi translator to translate my midi mixer to pro tools. The midi mixer I am using is the Peavey StudioMix(the Cheapest I could find at the time). I was able to get pro tools to control the faders of the StudioMix, but I could not get the StudioMix to control the faders of pro tools. When sending the pro tools I used the Control change(also was able to get it to work with the raw midi) to NRPN 7-bit. When I tried it the other way, from StudioMix to Pro tools, nothing was working. I tried raw midi and CC to NRPN 7-bit and nothing works. It says that it is outputting it on the event monitor but nothing is happened on pro tools. I could really use some help, would like to use this instead of buying a more expensive one.

Hi, could you capture a screen shot of how you have Pro-tools set up and also post the MT Pro project file you used. Also, could you capture the MIDI in the log window and paste into a text file? Turn on MIDI IN and MIDI OUT.

I suspect it is either a MIDI routing problem From Studio MIX to Pro-tools or that the wrong type of MIDI settings are there. Are you using Mackie Control in your settings? If you Studio Mix does does not set “touch” Mackie message when you touch the fader, Pro-tools will probably not do anything so we may have to simulate a touch message when sending from Studio MIX. Many Mackie emulating devices don’t always send “fader touch” information and some DAW’s are less forgiving of this. I think Pro-tools is one.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

I attached Bmtp file and a screenshot of the setup in pro tools.

Here is the midi log from the studioMix to pro tools

1: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=55
2: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=55
3: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=56
4: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=56
5: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=57
6: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=57
7: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=57
8: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=57
9: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=58
10: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=58
11: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=58
12: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=58
13: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=59
14: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=59
15: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=61
16: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=61
17: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=61
18: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=61
19: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=63
20: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=63
21: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=63
22: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=63
23: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=64
24: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=64
25: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=66
26: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=66
27: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=68
28: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=68
29: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=70
30: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=70
31: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=71
32: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=71
33: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=72
34: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=72
35: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=72
36: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=72
37: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=73
38: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=73
39: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=75
40: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=75
41: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=75
42: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=75
43: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=76
44: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=76
45: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=77
46: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=77
47: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=78
48: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=78
49: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=78
50: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=78
51: IN 0.9 NRPN 7-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=79
52: OUT 0.9 Control Change on ch. 1 with CC#:0 (0x00) and value:pp=79

 

Here is the midi log from pro tools to StudioMix which does work

1: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=0
2: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=0
3: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=1
4: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=1
5: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=2
6: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=2
7: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=11
8: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=11
9: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=18
10: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=18
11: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=54
12: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=54
13: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=90
14: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=90
15: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=124
16: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=124
17: IN 0.1 Control Change on ch. 1 with CC#:1 (0x01) and any value set ‘pp’ to value=127
18: OUT 0.1 NRPN 7-bit with MSB=27 (0x1B) LSB=45 (0x2D) on ch. 16 with value:pp=127

I am not using Mackie control, though

 


Attachments:
1539477905639_Yes.bmtp
![](upload://Y6Ox0IwusUX5gP3IIlsB8m3MuC.jpeg)

Well what stands out to me is that it looks like your LSB on all NRPN’s going from StudioMix to Pro-tools is 44 which your LSB coming from Pro-tools to StudioMix is 45.

I’m not sure what the StudioMix accepts but I did find a document that seems to describe it.

 

http://www.arthunkins.com/StudioMix.txt

 

Also in ProTools it looks like you have it set for HUI which I believe is a whole different Protocol but your log file doesn’t show HUI type of output so that may not be the problem.

Oh, sorry they were just two different faders. LSB 44 is the first one and LSB 45 is the second one. I’ll read through the document and hopefully I’ll find a fix.

OK, I actually could not find the documentation with search. That was the closest I could find but it didn’t look like the NRPN’s aligned with what you were saying. If you could find a link to the actual Peavy official documentation maybe I could help more. Also I assume your output is going to the right port. Keep in mind how ports work.
1) Default input outputs ports defined at the project level.
2) If there is something different defined at the preset level it overrides the project default.
3) If there is something different defined at the translator level it overrides both project and preset defaults.

If the resulting translator actions results in output, AND swallow is set, then default routes are overridden.

However if resulting translator actions exit without output or do not match the incoming trigger, the default routing will occur.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

So, I try all of the different midi types for pro tools and the one that finally worked was m-audio keyboard, but when i move the fader on the StudioMix the fader is fighting because the signals are countering each other. Any solutions?

Yes, you should set up a translator to disable incoming MIDI from Protools when you manually move your fader.
The way I would do it is monitor for NRPN going out (you are moving the fader) and set a global variable as a flag that you are moving faders. Outgoing action to set up a timer for a delay. Set the timer up so that when it fires, you set the global variable back to 0.

Then on incoming from Pro-tools, look at the flag and if the flag is set, skip outgoing action (cc to NRPN).

So as long as you are moving a fader within the time set by the timer, you will ignore input from Pro tools.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

Alright, I’m just start looking at this and I am a little confused. I just got this software, so I’m not 100% on how to use some of the functions. I’m not quite sure how to do that. I was looking online and the other examples just confused me. So am i setting the global variables in the Rules, with the incoming be the NRPN signal and then the outgoing as a preset change.

Now that you got most of it working. Send me your project file and I will make the final tweaks with what I discussed and show you how I did it. I know it can be a little bit of a learning curve but once you get through it, thinks go much easier.

Alrighty I only have the first three faders setup. They all are working if you turn off the opposite translator they work perfectly, but with both running they fight against each other.


Attachments:
1539566395146_ProToolsConversion.bmtp

OK, so something like this should work but I cannot test it because my controller does note send NRPN.

First of all I assigned the aliases as follows, you will need to properly assign them to the right devices when opening the project

From MBox External -> This should be the input from your controller

To Pro-Tools -> Use whatever Virtual Port you have defined as input in Pro-tools

From Pro-Tools -> Use whatever Virtual Port you have definde as output in Pro-tools

To MBox External -> This should go back to your controller

The above are all defined as the default ports at the Project Level

Then ant the Preset Level I defined Inputs and outputs as follows. These will override the project defaults at the preset level. You do not need to define them again at the translator level unless they are different

Pro tools to Studio Mix

Input: From Pro-Tools

Output: To MBox External

On the three translators there I added the following rule

if ga==1 then exit rules, skip outgoing action.

On the preset Studio Mix to Pro Tools

Input – From MBox External

Output – To Pro-Tools

I added two translators. The first one sets ga to 1 and triggers a timer to start in 50 ms. From the above since we se ga==1 then we will ignore anything from Pro-tools. When the timer triggers, then it sets ga back to 0 thereby re-enabling input back from Pro-tools.

Hopefully I got everything right.

I disabled the other 2 fader translators from Studio Mix as it looked like they had the same incoming message as the first. You might want to check the accuracy of your incoming messages on those translators.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 


Attachments:
1539568862194_ProToolsConversion-2018-10-14.bmtp

Could you rename this discussion thread for something more meaningful like “Peavy StudioMix control with Pro-Tools” and maybe put these in also as keywords so it is easier for others to find later?

Alrighty I got everything up and working. The only problem I ran into was that the any NRPN flag was doing for any of them so I just went back through and made an individual flag for each fader and it worked perfectly. Thank you very much for your help. Also I’ll change the name, but I did’t see an option to do that.

Glad you got it working. If you can’t change the name, maybe you can add the tags and I’ll ask the support folks to change the title of the thread.

Steve