I know this, but thanks anyway. The problem is that I make a massive use of the instrument tracks and pinning tabs doesn’t solve the issues coming from the layout of the inserts/sends ones, which take both more than two thirds of vertical space available (and I have a 2560x1440 monitor…), no matter if there are things in it or not…
And about the instrument tracks, at a point, I even thought to get rid of them and use the VSTis I have at disposal with the instrument rack instead. Haven’t done so, until now, but I’m still thinking of it…
I’m with you, that there needs to be a design, which works for small and big screens, where everything needed can be made visible. Perhaps a modular customizable inspector would be nice.
But Steinberg already stated months ago, that a new inspector design is on the way, as they are aware of the issues.
Yep, I have read this. The problem is that Steinberg is also about to drop the remaining VST2.x support in Cubase for the next upgrade. So, Cubase 12 will probably be the last Cubase version that I’ll use and I’ll probably never see the new inspector design.
This, unless I find a kind of wrapper that would allow me to use my VST 2.4 instruments as VST 3 ones. I’m still investigating…
Yep, I have seen this one. It’s one of the solution that I’m considering, but before spending something like 100 €, I want to be sure that Cubase will not put it in its blacklist. So, I’ll probably make, at a point, a thread about it to get eventual feedback concerning it.
And about dropping the VST 2.x, it has been announced several months ago, for “technical” and “stability” reasons. Several months ago, I had a heated exchange about it with @Matthias_Quellmann, which closed the thread after his last argument…
Does anybody else find the inspector confusing? I’m not sure if it’s just me being simple…
but Logic’s inspector is how it should be done.
Yes - our take is a redesign should include displaying region based quantization settings, or something like the inherited base region parameters Logic implements. That would save mouse clicks as you would not have to use the quantize panel or the key editor to apply Q per region. You could then recall what you already set for (different) Q values in regions of MIDI data - not recalled/visible anywhere in Cubase/Nuendo. Instead of arrow or fold down menus other DAWs just do an automatic context related switch where what is displayed in the inspector automatically changes and is visible by default depending upon what you click on in your arrangement window. But it would likely break backwards compatability with old projects, so they probably won’t do it.
Cubase has all part (=region) relevant data in the horizonzal Info Line. If there was to be part based quantization (yes, please) it needs to go to the Info Line. Thus it has nothing to do with the Inspector rework, unless they would bring back the Info Line to the, shall we call it the Left Zone (instead of Inspector).
Yes, I have noticed that which would be fine. I made a screenshot of what that might look like if you follow the link to the other thread, but here it is. In the case where MIDI data had been manually selected and set to different values of Q, swing, catch etc, within the same region, then the lack of a common value for a parameter could be denoted with an asterisk (*) or maybe (-). I believe that is what Logic does.
Never understood the backwards compatibility thing, as a reason to not improve workflow and remove inconsistencies.
We have access to all the old versions, so there is no need, that I am able to open e.g. a Cubase 9 Project in C12. I would even recommend to open old projects in their old Cubase versions.
Of course it would be nice, but workflow is N#1 priority, so please forget about backwards compatibility ASAP Steinberg.
That’s interesting to hear. Steinberg really needs to focus on ease of use. I’m not saying dumb it down like Logic has been…but goodness…it’s a HUGE learning curve. Not saying it’s bad software….just not thought out with modern design sensibilities.
What would expect to happen if you press the Q button from the project’s quantization?
What would you expect to happen if you use the key command for Quantize?
What would you expect to happen if you have several events selected, hover the mouse over “1/32 T” (from your screenshot mock-up) and move the mousewheel?
I’d think those tools would continue to work the same way as they do now. At least in Logic what you set in the region inspector are the “base parameters” you start off with. So think of a photoshop project where you have the base or the bottom layer and then you add layers on top of that to superimposes images over one-another. If you have nothing in the base layer (no image there or no quantization applet to the MIDI data) then when you use the other existing tools to apply Q it’s exactly the same same as applying Q to the original MIDI data with nothing previously quantized. But if you set your MIDI region inspector to say 50% Q at 1/16 note then that becomes the base or start value any subsequent use of quantization will be applied ontopof be it from from the Key Editor, the quantization panel, etc. Should not matter if you select all notes or just some notes and subsequently apply. different quantization to them; those tools still work the same way. I’m not sure how the devs would treat the existing use of the MIDI quantize plugin on a track. I would obsolete that in favor or the finer grain region based control, but that would certainly break backwards compatability for some people on this list.
Does Logic also have a quantize for regions within the project?
The article talks only about events inside the regions getting quantized. Can Logic also quantize the regions themselves?
Where would I find that?
