As of Cubase 12, the relative control resolution is 127 steps (there are many posts complaining about this from way back)
I appreciate all the new features probably benefit someone…but have really foundational issues that would take at best 30 mins to implement been fixed?
127 steps was groundbreaking in 1982 for midi control. Cubase is a mature audio daw now…and Im not asking for 14bit control even…just very simply using current controllers with internal resolutions that are professional for this day and age
Please…without ANY coding…just using even legacy remote or midi remote editor and allow a higher resolution, even just a multiplier eg X2 X5 X6 etc
That would be amazing…but 14bit relative is not official and lol…its 14bit and from my small knowledge of midi…doesnt it need 2 x 7bit msgs to even work so where is the extra dialog entry
Without having tested if it is the way it works: in Midi 1.0 the first 32 controllers get their expansion to 14bit by using thext 32 controllers. Adding 32 to the controller number should yield the additional controller number.
In your screenshot you use CC0, 0+32=32. So CC32 might get used to make it 14bit.
As I said, I might be very mistaken with my assumption.
Well thats the first issue…where are the MSB/LSB choices? Seems it has options for relative but in reality only allows absolute 14bit
But way more simply that…why not allow a resolution multiplier on the 7bit value of a normal inc/dec. That would solve everything with a small bit of code.
So going by the overwhelming responses…no its not fixed and there arent many who care because they probably dont know…oh well
As a safety stop, I can use Eucon on the artist stuff I guess…you know, the interface to Cubase that actually has the exposed API hooks and hi res control…but for the application Im talking about…the hardware is painful compared to a dedicated IFX controller…
Anyway…dont know what I was expecting along with all the other complainers for basic stuff instead of bells and whistles. That we have to bang on for this long only tells me the devs are not able to understand the implicit nature of hi res control and investing 30 mins to add a multiplier is just too much
Subject Closed…Yeah I am disappointed…again but not wasting my time anymore, just checking back on how many responses I actually got on the last 5 topics I posted…Reaper is slowly edging along but its a tough learn and there are some major bits missing that you have to 3rd party for
I never said it stopped peeps making music…the post is about a better and more refined workflow
You obviously didnt read the details else you wouldnt answer like that. Simple cheap and good midi controllers use 7bit like they have for the last 45 years…they arent the problem. Midi 2.0 wont even fix it and what are you talking about…64bit automation???
Why dont you try making a mapping for high res mixing. Its my job atm…to make other peeps music better and it affects my workflow. I accept that it may not affect yours and you then why comments?
Said plainly, Cubase does not allow hi res relative midi control (in cubase 12 at least) ie 14bit. Try it on dynamic mixes…no not the -8 that basic pop etc uses or -6…how would you even notice?
Prove me wrong…but after actually experiencing the difference using Avid gear…I now get what I blindly couldnt perceive
There are those of us who care. I posted quite extensively about the lack of a range or scaling option for relative MIDI CC values back when version 12 was released and I got at least one Steinberg dev to understand the importance of such a setting in the Mapping Assistant.
Currently your only option is to write a script for your controller which would allow you to scale relative signals however you wish. That part of the API works well and is what I do.
Unfortunately MIDI Remote suffers other shortcomings and bugs that I hoped would’ve gotten fixed by now, but alas.
I remember your posts @mlib and a number of others…thats why I wrote “arent many”…your explanation is what made it plain to me.
Im just tired of coding after 35 and I hate javascript verbosity…python is just so much more logical and to the point ime…but the point is I paid decent money and there is a midi remote which as we both know, simply needs a divider of the step value internally and would all be fixed. After using the Eucon IO…just wow…how much does it improve the INSTRUMENT of automation. I have done a couple of mixes lately that the client couldnt believe how it improved and made the song so accessible and connecting to new listeners…Im not pointing out me being a guru etc but Im saying, mix and automation are part of the art and this aspect of workflow can be quite frustrating. Thanks for taking time now and in the past to help try and make Cubase the professional solution it should be with more than bedroom producers in mind. I go to any studio (practically) and Pro Tools is there, they might have Ableton and rarely Cubase…which exemplifies what is important. The avid controllers eg even artist mix being the entry level are mind blowing to the craft of mix and automation.
