I believe I have created a translator that will allow me to send MIDI cc from 0-89 on channel 105. I have attached the translator file.
I am assigning this to a specific fader in Digital Performer so that the fader will not exceed a particular maximum value.
I am using the ‘attach midi controller’ feature but after I do this, the fader is still able to move when controlled from the transmitting MIDI controller all the way to it’s max value, ignoring the BOME programming. I think this is because when I move this hardware fader, Digital Performer is showing in its MIDI Monitor window that it is receiving data both from BOME Virtual port #1 as well as directly from the MIDI device which happens to be a monogram fader.
I used to have this programmed in Digital Performer to receive data as though it was a control surface transmitting pitch bend and then BOME Scaled it for Digital Performer, but I had to stop using that since it was conflicting with my slate Raven which was also using a Mackie controller profile. I deleted the profile in Digital Perfomer to see the data coming from BOME as a control surface pitch bend data stream and now am simply attaching it as a midi controller.
So now I wish to control this fader simply by attaching the midi controller.
Is there a way to prevent this particular hardware fader from allowing Digital Performer to see the ‘monogram’ data stream and only the BOME Virtual #1? Scaled Fader Control.bmtp (1.3 KB)
Looking at your project file, it looks like you are sending CC105 on MIDI Channel 1. There is not MIDI channel 105.
The incoming values are 0-127 and outgoing values are 0-89.
Yes, you will need to disable input from Monogram and only us BMT 1.
You should be able to disable Monogram input port from being seen by Digital Performer in the MIDI port selection settings within Digital Performer.
Yes MIDI Channel 1 on Channel 105.
Because the Monogram is a USB device, it doesn’t provide for individual shut-down of midi ports in the DP MIDI bundles window.
I wish there was a way to capture all MIDI in the computer and edit it prior to it getting to Digital Performer. Kind of a ‘seize all midi application’.
Oh well…might have hit a tech-wall with this issue
I should restate that it seems that USB devices might be treated differently. I was able to show the 16 receive and transmit channels, but disabling all of them still showed data in the MIDI monitor within DP. That being said, it was after that, that I think I figured out a fantastic solution that is working great so far.
I’m using a custom console in Digital Performer, and it suddenly occurred to me that I could make the input to the custom console, BOME Virtual 1. So once I did that, and then pointed it directly to the mixer channel, within the custom console…voila. It works perfectly. I’m using the scaling in BOME that now has the maximum fader level of +0.4. For my O.C.D., I wish I could have it be at zero dB on the nose, but .4 over zero will have to do since I can’t find values that divided in the MIDI scale that come out to 0.
Great step in the right direction. If your controller can send 14 bit CC and DP can recognize it, you would get better precision. You would still need to do some scaling though. If it were me I wouldn’t worry about .04 db precision off.
Well…I just gave the 14 bit setting a try and then went back to MTP to play with the numbers and still couldn’t get closer. Maybe there’s a setting elsewhere that would help with the “resolution”…but I’ll just leave well-enough alone. I actually thought I’d be able to get this done without MTP since the DP console window has some values settings, but the minimum and maximum setting adjustments had no effect on the output values. So thank goodness for MTP!
