Now that horizontal scrolling (or expansion) of the Inspector Pane is possible, to be able to edit tempo step/ramp via a single click, in both the Inspector and a future “Data Inspector”. would be very helpful as one would not need to find the tempo point in a given project and edit it via the InfoLine.
Editing (or deleting) of Bezier curves for automation and tempo nodes, would also be equally helpful.
Note Off information should be editable via a future Data Inspector, as should the MIDI channel for all MIDI events, including bulk changing of data where values are not initially equal, both for columnar data and selections.
Also, where a data node is selected, playback should be able to be initiated from that point, as well as ranges selected for playback.
One other thing which I think is important as well, the Key Signature of a given track for the first measure should be able to be edited as MIDI data and not as an Inspector parameter.
We use Cubase, Nuendo and Pro Tools here, but I’ve heard from friends who use Logic Pro that the list editor is fairly comprehensive and includes markers, tempo, signature and automation.
I won’t post a link to Logic pages here but have a look for yourself and you’ll see what I mean.
Something exists, so may we live in hope.
Also, I would like to be able to Remove Unused Parameters, from within a future Data Inspector.
I imagine a new “Data Inspector”, would need as previously stated, access to score elements, as well as track data and automation, among other things including Bezier curves, step/ramp for Tempo, and Chord Track data.
I tried to have Key Signature changes at bar 188.8.131.52 but they are supplanted by what is entered into the score at the initial bar and thus have no effect so a true Object-Oriented Environment, would have all data editable in a list, since even Key Signature changes occurring in the initial bar cannot be edited in and of themselves.
It’s truly great that SB are allowing more diverse ways to edit data but a centralized view, with editing functions akin to what exists in the editors themselves would in my view, truly set the software apart.
Argh, I just spent 40 minutes looking for the Project Browser and wondering why it wasn’t listed under Key Commands etc, only to come here and discover it’s not in C13! Bad move Steinberg; put it back please. I’ve been using it since ‘day 1’ and have found it to be invaluable. Thank you.
Steinberg has been clear in the Cubase 13 release notes that Project Browser is end-of-life and has been discontinued. The current design, which was intended as a debugging tool but gained a place in many users’ workflows, was unmaintainable and, by the sound of it, was holding back modernisation elsewhere in the applications. Steinberg has decided to focus available development efforts elsewhere for now.
In short, the Project Browser is dead, cannot be revived in its current form and there are no current plans to replace it. If the loss of Project Browser is a deal-breaker for you, stick to version 12.
The Project Browser has gained a place in users’ workflows because of the fact that it deals with many types of data, within a single interface.
Workflows that use hardware for automation, for example may not require such a means of editing, as nodes are not required to be quantized but for workflows that require automation data to be quantised to Musical Mode, discontinuation of the Project Browser, is a real workflow killer…