Peavy StudioMix Mixer

So I was here recently with help my peavy Mixer and thought I had finally figured it all out by switching the midi type in pro tools  to m-audio keyboard, unfortunately this midi type is only allowing me to change the faders. So I most go back to the HUI setting on Pro tools if I would like to use the other functions of the mixer. When I have it all set up it says the input and output are both sending and receiving. I am not getting anything out of Pro Tools. So I'm not sure if pro tools is not capable of being compatible with NRPN(which the mixer sends). I could really use some help to get the mixer working and to soothe my head-ache.

Could you show me your log file with Pro-tools running. Also the screen shot you have MIDI set up while in m-audio mode? What m-audio model keyboard did you have set up?

So do you want the log file while using hui? And do you want me to copy it out of the log window? Also do you want screen shot of just the Bome midi screen? Lastly when you set the m-audio keyboard mode it does not ask for a model, the keyboard is part of the type of midi.

Well I’m not convinced M-Audio keyboard would not work, if in fact it had LED’s that are updateable, but maybe not because many M-Audio keyboards do not have LED.s With that, yes lets see the HUI mode log from MT Pro and also snapshot within Pro-tools that shows how you have things set up. I don’t have full version of Pro-tools but maybe I can get it to work with Pro-tools First (which is free). I suspect that if your faders do not have touch control, perhaps Pro-tools is looking for fader touch message before it will actually move faders. I saw this problem with Davinci Resolve a while back and had to modify the HUI fader output from the Xone controller to include touch messages prior to sending fader move message.

Here is the log when going from the mixer to pro tools

13011: IN 1.9 Control Change (14-bit) on ch. 16 with any CC# set ‘pp’ to CC#=6 with any value and ‘pp’ to value=13441

13012: OUT 1.9 One-shot timer “suspend input”: 50 ms delay
13013: IN 1.1 NRPN 14-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=13520
13014: OUT 1.1 Control Change (14-bit) on ch. 1 with CC#:0 (0x00) and value:pp=13520
13015: IN 1.9 Control Change (14-bit) on ch. 16 with any CC# set ‘pp’ to CC#=6 with any value and ‘pp’ to value=13520
13016: OUT 1.9 One-shot timer “suspend input”: 50 ms delay
13017: IN 1.1 NRPN 14-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=13587
13018: OUT 1.1 Control Change (14-bit) on ch. 1 with CC#:0 (0x00) and value:pp=13587
13019: IN 1.9 Control Change (14-bit) on ch. 16 with any CC# set ‘pp’ to CC#=6 with any value and ‘pp’ to value=13587
13020: OUT 1.9 One-shot timer “suspend input”: 50 ms delay
13021: IN 1.1 NRPN 14-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=13657
13022: OUT 1.1 Control Change (14-bit) on ch. 1 with CC#:0 (0x00) and value:pp=13657
13023: IN 1.9 Control Change (14-bit) on ch. 16 with any CC# set ‘pp’ to CC#=6 with any value and ‘pp’ to value=13657
13024: OUT 1.9 One-shot timer “suspend input”: 50 ms delay
13025: IN 1.1 NRPN 14-bit with MSB=27 (0x1B) LSB=44 (0x2C) on ch. 16 with any value set ‘pp’ to value=13725
13026: OUT 1.1 Control Change (14-bit) on ch. 1 with CC#:0 (0x00) and value:pp=13725
13027: IN 1.9 Control Change (14-bit) on ch. 16 with any CC# set ‘pp’ to CC#=6 with any value and ‘pp’ to value=13725
13028: OUT 1.9 One-shot timer “suspend input”: 50 ms delay
13029: IN 1.0 On timer “suspend input”

I also attach the screenshot of pro tools

 

 

 

Well your outputs are certainly non-HUI outputs. You might want to muck around with the attached project. It takes CC output from my non-HUI controller (WorldE Easy Control) and converts to HUI Protocol. I did this for Davnici Resolve.

 

You will probably need to set up your own NRPN inputs from your Peavy Studio Mix.

So my pro tools output looks a lot different then the output that was in the attached file one. Here is what is outputs:

7757: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 2A
7758: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7759: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 2A
7760: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 40
7761: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 2C
7762: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7763: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 2E
7764: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 40
7765: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 30
7766: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 40
7767: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 33
7768: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7769: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 33
7770: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60
7771: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 35
7772: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 40
7773: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 39
7774: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 40
7775: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 3D
7776: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60
7777: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 40
7778: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7779: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 41
7780: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 20
7781: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 41
7782: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60
7783: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 43
7784: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7785: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 45
7786: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7787: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 4A
7788: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 00
7789: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 50
7790: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60
7791: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 55
7792: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60
7793: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 00 57
7794: MIDI IN [Bome MIDI Translator 1 Virtual In]: B0 20 60

So what should I put in the out put? Also is this the one the one you were saying has to do with the touch fader?

Hi, Well HUI can be a complex protocol and the discussion here is really beyond the scope of free support by the Bome Company. You might want to either reach out to me for paid consulting/programming services at my email address or do some research on the HUI protocol. Or maybe you can set up Pro-tools for a more simple and well documented controller to emulate. Even Mackie MCU is simpler than HUI. In a nutshell though the B0 0x yy are “zone select” messages and B0 2x yy are port select messages. HUI supports 30 zones each with 8 ports. Each zone/port combination supports a given control. Zone 0 for instance controls fader, select, mute, solo, v-select, insert and rec/rdy. Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz For your examples: B0 00 xx = Means set fader 0 MSB to xx B0 20 xx = Means set fader 0 LSB to xx

Alright before I do that, I’m going to do more research. Could you send me the forum for fader touch? The one that
that you saw with Davinvi Resolve

It was not on the forum. I just had to figure this out myself and it took me hours.

I can post a bit of a cheat sheet I use to figure out HUI. (See below)
Not sure if it will be much help without the larger research and context.

CC 10-18H – Vpot Rings
CC 0C – Zone 0 to 1D – 0C from user 0F from System
CC 0D – Jog Wheel -F to -1 : 1 to F
CC 2C – Port 0 to 8
CC 00-07 -Fader Hi – Move Fader
CC 20-27 -Fader Low – Move Fader
CC 40-4C – V-Pot – Delta Values uf vv> 40 then vv-40 if < 40 then -vv CC 0F - Touch Fader - Release Fader Pt 1 Value 00 to 07 CC 2F - Touch Fader - Release Fader Pt 2 Value 40=touch 00=Release CC 0F - FootSwitch - 1D = Footwitch - Part 1 CC 2F - FootSwithh - 1D = Footswith - Part 1 40=SW1 closed 00 = SW Open 41=SW2 close 01 = SW Open FF - One or More is System Reset 90 00 00 - Ping 90 00 7F - Ping reply V-Sel Changes behavior of the V-Pot Auto- Enable Automation Scribble Strip -4 Char LED Display

Oh and I found out the Pro-tools First does not support external control surfaces. Only instruments. So if you want me to help and do some testing with Pro-tools, it will require I purchase a monthly subscription for the duration of the testing.

Regards,
Steve