As I am finishing up a large project in C14, I have now startet to look into C15.
First thing that bug me is maybe a small thing, but… Like in C14 I want to be able to reset the Meter value (clicking the value field) for any given channel WITHOUT the channel being automatically selected.
yes I know I can assign a key command for resetting the meters… but I don’t necesarry want to reset all meters in one go (not that important while mixing, but very much so in sound design etc)
I routed a mono track (panned center) to a mono group, and noticed that when doing an Export, of the mono group output, it rendered out a file 3 dB lower in level…. FIXED**
**Somewhat that is, when fiddling around with another old odd Cubase thing (export mono/stereo)… But that’s for an other day
What are the things that bug you with C15?
Or make you stay on C14 for now?
I cannot reproduce this issue.
But please keep in mind if you route the track, that has the created mono file on it, to a stereo bus the channel will display -3dB in peak. Is this maybe what happened on your side? That the created file flows to a stereo channel?
When renaming channels in the mixer pressing “Tab” should rename the next channel, like the project window behaviour.
Selecting and colouring multiple channels in the mixer. You could do this on older versions of Cubase, but in newer ones.
Using scroll wheel in the mixer no longer lets me scroll vertically between inserts, sends etc… anymore?
Mono / Stereo icon should be made into a button thats permanently in view when channel width is set to smallest.
Pre / post controls for gain, phase and filters should be turned into dials / button and permanently visible.
Folders;
Not being able to turn folders into a Bus, with nested tracks inside. Like other DAWS…
Reordering tracks in mixer (if already nested in folders in the project) moves them outside the parent folder. To move them back in, you need to do it from the project window.
PLE;
No commands for assigning plugins to designated insert slots.
Tracks.
I just hate how controls for every track type don’t follow the same design spacing. Even after customising tools, name and control widths, they just don’t look consistent.
Volume and Pan controls on different track types don’t all share the same design or display the same values.
When saving pan presets, loading them can recall incorrect pan graphic. For example; save a preset using combined panner, load the preset on a different track and it’ll display balanced panner, unless you changed the pan control to combined - prior to loading the preset.
Pattern Events.
When creating new pattens, you should be able to re-order them in the drop down menu. Instead of just duplicating and deleting.
UI (windows 11)
Compared to Mac, there’s still a lot of menus that need updating with the UI. For example - preferences.
It does NOT. I choose to export the mono group (multiple tab - only the mono group in question selected).
Strange… But then again I have not checked if any preferences or other settings are changed in C15. I have just let it inherit the settigs from C14 while installing/starting up for the first time.
PS. I have used Cubendo since Nuendo 1.5 and Cubase SX1 (and Cubase Vst 32 5.0 on test before that), so I usually know my way around in Cubase… But I will test some more before I take C15 into production of course. When time allows
Thank you. I have to agree with many of your points. I have not been through all of your comments… But you sure gave me a real “check list” to go through.
The fact that they’d change the way colors are available to be picked completly blows my mind. They limited colors and dumbed down the interface with the new system. Changing the color system that was almost perfect to begin with (along with the previous BPM counter changes) makes me wonder what the hell is going to happen to this program in the future.
I can’t import my color scheme that I spent a couple of years tweaking because the new color system won’t accept it. I really wanted some of the new features in 15, but it looks like I’m stuck on 14. The way the program looks really is that big of a deal to me. What’s worse is that Steinberg has been silent on the issue, and I can’t think of one good reason why they changed this. They could have spent that time working on allowing patterns to be switched between MIDI/Pattern at will like other programs allow you to do. Instead they screwed up one of the main reasons I used this software.
I have NO idea why the exported file showed up 3 dB lower… Yet. But will figure it out
But as you mentioned, it actually was the meter settings that visully fooled me.
When doing sound design and pre-prod stuff, I usually have the meter set to “Post Fader”… But when mixing I usually have it set to “Post Panner” (via Key Commands).
Slipped my mind for this test. Besides that, this was the first time I opened/started a new project in C15.
I were also reminded on the odd export mono/stereo thing again… But that’s for another day
That there is nothing in C15 that I need or want to make me upgrade from C14, so I’ve let the trial expire.
If the commonly described IU issues were resolved, full midi2 compatibility included, long standing bugs addressed, or the introduction of mixer folders, I would’ve upgraded immediately without even running the C15 trial!
Lots of good stuff in here (colors, scrollbars too small, etc)…
Overall C15 is amazing in so many ways, but instead of addressing some long standing issues they tinkered with the UI in ways nobody asked for instead of fixing long standing issues like:
inability to setup audio connections for multi-in single out external hardware like hardware mixers
inability to import projects from before C7 that have any automation on group or vst rack channels.
These are both situations where the code to handle this stuff is 99% already written they just refuse to do the last 1% because they had to make more reverb plugins.
This isn’t specific to C15 but it always catches me out that changing the ‘event start’ in the sample editor breaks group editing / phase coherent audio warp because it doesn’t do it across all the events.