I’m working on the V1-M version of my cubase-mcu-midiremote project right now (with the P1-M version being next on my list) and I’m curious: What do y’all think would be the best use of the secondary displays on the V1-M? I definitely think track names should be there too (in addition to the ones on the primary displays), but then there’s still a second row left that I’m unsure how to use. I thought about displaying the fader’s value, but I don’t think it really matters most of the time as the faders already have a scale printed on the device and I don’t really need to know the exact db values while mixing. I’m happy to take your ideas! Which additional channel info would you find most helpful?
About your question regarding the second row on the screen, hmm. Spontaneously Im thinking that it should be dedicated to the specific track, but exactly what I don’t know.
I agree about the fader value, yes that is nice I guess but perhaps not super crucial since you can tell by the position of the fader.
I m going to think about this one for a bit. But yea something specific about the selected track… I’ll be back!
Oh, that’s a wonderful idea @vagglyren! However – you may have guessed this – the information available via the MIDI Remote API is quite rudimental (metering is the ultimate feeling already) But even if it were possible, there’s still the slow display update speed of the devices which would likely render this less useful than it could be. So I guess real-time data is not an option in general
New term for me “rudimental” Yea you are right, the display fresh rate is not the highest (was one of my wishes for the controller) This is hardware determined right?
In the middle of writing that I figured out something simpler perhaps, what about peak levels + a red light if the track is clipping? I know that the metering turns red if your track is clipping but perhaps you don’t notice it due to you not showcasing that specific track on the controller.
That light will linger until you have clicked/pressed something (I don’t know what you would click/press on though hehe)
Kinda like you have to do in Cubase to remove when the input is clipping?
Great to hear from you. Peak level of tracks is a great idea. Idk, how about whether the track is audio/vst/midi, and/or which vst device is being used (reason rack/Kontakt/HALion…). The fader level wouldn’t be a bad choice either although, like you stated, it’s already printed on the controller. But, the software fader doesn’t exactly match up with the hardware fader. With the fader position on the hardware about halfway down, the fader does a kind of “jump” and skips a bit at the exact same spot when you move the hardware fader slowly up and down.
besides that, I’m not sure.
I would think that the slow speed of the screen to be a software or firmware thing. the clock seems to be super fast, but the only other realtime measurements I can see if the meter bridge and its a bit laggy to me.
Thanks for all your ideas @vagglyren@HiddenTalentPro!
So I fired up Cubase and checked which of your suggested info I could retrieve via the MIDI Remote API. Here’s what we can do:
Meter Peak Levels (like displayed in Cubase) – I really like this as it’s like the info available in the Cubase-builtin channel UI:
Track Clip indicators – but only at +6 db, while the MCU meters clip at 0db already, so not very helpful
The name of the track’s instrument, if any
I would love this one! Or even the track’s target But currently, all we can do is showing the VST instrument for instrument tracks. I think I’d prefer meter peak levels then as they are useful for most other track types too.
Maybe we should show the peak level during playback and the fader value otherwise?
I think that’s a good idea. Just so I understand you better, during playback it would show the peak level, until I touch the fader then it would show the fader value?
I thought about this, but then I noticed one might also want to move the fader while watching the peak level. So by “otherwise” above, I meant “only when the playback is stopped”. But I’m reeeally not sure, only while touching is very nice too Which one do you prefer, or are there other combinations that might make sense?
Just my personal preference, I would prefer to see the level of the fader while I’m touching/moving it during playback, otherwise showing the peak level. However, the response time would really come into play here, because if it’s really choppy or laggy then it could become frustrating to look at, because you would have to wait for the controller to “catch up”.
Hi bjoluc & thank you - Can’t wait to try your implementation on my P1-M. When I tried your script I realized that I miss some things that are available in MCU mode but cannot be implemented with MIDI Remote as stated in your Readme.
is it not possible to make it indicate above 0 db? My was that incase something is clipping, and you don’t see which it is right away since you only showcase 8 tracks at a time (on the controller) when you are scrolling through your tracks, a red light or something would indicate that “this track has been clipping”.
A fast way to “search” for what track is clipping.
Yup, I agree! Tried this and decided to keep it. The response time is not super fast, but still OK in my opinion.
I think you didn’t miss anything there since the video you shared only refers to a custom controller script, not the builtin MCU integration…
It might be, based on the peak level dB text, right!
Makes sense, only that there’s no way to show a red indicator (other than track colors) in the display…
That’s because the MIDI Remote script can’t directly send pixels to the displays but only MIDI messages with ASCII strings to the device firmware which then takes care of the rendering.
But even if it were possible, there’s still the slow display update speed of the devices which would likely render this less useful than it could be. So I guess real-time data is not an option in general 
Yea you are right, the display fresh rate is not the highest (was one of my wishes for the controller) This is hardware determined right?
But currently, all we can do is showing the VST instrument for instrument tracks. I think I’d prefer meter peak levels then as they are useful for most other track types too.