- I would like to see a function that with one click you can create a Halion instrument from VST instruments. Basically to create a multi sampled instrument. Good for collaborations like FL Studio.
- Retrospective Recording with tempo or beat detection.
- Smart Pencil that recalls the length value of the notes.
- Find similar sounds in Mediabay.
- Feature: (Project) Notepad added to the right side of the menu (VSTi, Media, CR, Meter, Automation)
- Feature: Project Color Setup --color picker added so that color gradients can be created relatively easily from a base color
- Feature: track background colors can be customized
- Fix: When implementing the Key Editor function āCopy CC data from Controller Lane CC-1 to CC-11ā on the Stream Deck. This cannot be implemented properly: The problem is that if the data in CC-1 was recorded in Ramp mode, it can only be copied to CC-11 as a āStepā curve type using the Logical Editor. So far, the Curve Type can only be changed via the GUI. A Key Command would be desirable here, so that all CC data points could be selected and the Curve Type of these points could be changed.
- Fix: Mac: TrackPad - Swipe in MixConsole window. Swiping works in the lower zone. However, it does not work in the MixConsole window.
- Feature: Option, when using Soft-Quantize, so that the first note is ignored to prevent it from landing outside the part OR the part is automatically expanded.
- Feature: Option to ensure that interpolated CC values for the Ramp/Curve controller curve type are interpreted at the beginning of a part even if the first point lies outside the part (e.g., in the case of a linear rise).
- Feature: Enable the Chord Track as chord input for the Melodic Pattern Editor
- Feature: Integration of VST plugin windows in the lower zone
- Feature: An API for plugin developers to read MIDI data from all tracks at any given point in time
- Feature: Arranger events can be created via drag-and-drop from markers on the Marker Track
- Feature: Live chord display for MIDI input in the top toolbar
- Steinberg Forum - Feature: Dark mode without the need to log in
Iāve used many programs and none of them sit there for five seconds with a splash screen saying, āchecking licenseā then changes the splash screen to your program version, then boots the program.
But it doesnāt read/write metadata to the files, which is the issue. Googlyās issue is legitimate; how would it stay fast and efficient? With a proprietary index. So how do you read/write in real time but have an index? By importing the files into the index. And then it auto updates (monitors) the relevant folders.
An example of this is Void Tools - Everything. You choose the folders and it creates an index for itself from those folders. It does NOT create its own proprietary metadata. It reads/writes the files to update its index. When using the program we are referencing its own index, but the index is a mirror of what exists. It monitors the windows event table to update changes to its index.
Every single digital industry reads/writes directly to files except for the AUDIO INDUSTRY. All the audio software has their own stupid proprietary system. If you make an ms word document and use the program to add some metadata, does ms word create a proprietary database to store that info? That only ms word can handle? No, cause that would be RETARDED! It writes the metadata to the file itself. So now any program that supports .docx files can read that metadata. The files carry their own metadata, as it should be.
Look at any of the industries (except audio). Document, video, picture, programming etc. They all read/write to the files. All of them! When I add a rating to a .wav file in cubase, my file manager canāt see the rating, my sampler canāt see it, sononym canāt see it, other daws canāt see it, mp3 tag canāt see it, my music player canāt see it; the metadata doesnāt exist except for in cubase.
I also canāt backup my samples (and other files) to an external drive and have the metadata saved with them. So if I spend time adding ratings, tags, comments to files then I have to use cubase and only cubase with those files. Otherwise itās a waste of time.
Hi again @ASUNDER,
sorry, thatās no what youād written.
So please donāt try and twist my words.
You wrote this:
ā¦and thatās simply not true, since it has a database.
Thatās why I took a minute to correct your assumption.
Your - or anybody elseās - wish to have those meta data processed differently - or more conveniently, at least from your POV - may be legit, but itās an entirely different topic.
Cheers,
Markus
Would love to see improvement to note expression. E.g. option to snap back to the starting value at the end of the block like the pitch wheel, and less clunky editing. Could be a great feature but itās a pain to use.
My original request is to not have a proprietary database. Iāve also talked about it in previous threads.
Cubase read/writing the files is all win and no downsides at all.
Hi @ASUNDER,
thanks. If you put it this way, I wholeheartedly agree.
Not so sure about this one, regarding Steinbergās long habit / tradition of downwards compatibility (software content format generations vs. archived projects).
Would the latter be broken, in this case? At least for some time, all content might again have to be distributed for the old proprietary database concept and for a newly implemented open database concept.
We already had such a āparallelized old and newā situation a couple of times, especially with the rather time consuming transition of all available *.vstsound content from eLicenser licensing to the new Steinberg Licensing.
Of course all this can be done, technically. Itās just that - for example - studios which still run their stable productive environment based on Cubase / Nuendo 10 to 12 perhaps might not want to have to go along with such fundamental changes again.
So, at least some downsides might be unavoidable.
Best,
Markus
True, it would be pretty painful to move a forty year old dug-in system to a new one. Especially for the people who have carefully curated a media bay library for themselves.
But on that note, if we are protecting legacy things due to growing pains, letās apply that same logic to the AI slop as well. If the doctrine is, ājust because we can doesnāt mean we shouldā is applied to foundational things (that by all rights ought to be updated to a common sense standard), then how the hell is anyone going to tell me, āAI is here so we might as well embrace itā ? (just a thought)
Yes i desparately want Plugin rack/Container.. and frequency 3 would be amazing more modern 
.
This a very good idea for the plugin rack and I support the implementation of it.
About more filters and shelves I completely agree!
About modern UI like FabFilterā¦ Nope! The current UI of Frequency 2 is far much nicer than FabFilter (this one looks like an Airspace technology). It gives a feeling of an analogue tool. We are working with music and audio, not in an Airspace Agency. So, more Analogue taste to the overall Cubase/Nuendo UI will be very welcomed! UAD Luna is a perfect example of a DAW UI aesthetics.
Definitely a good and helpful improvement!
Best wishes,
Thurisaz
Iāll take fast workflow over the look of a plugin every single time. FabFilter Pro-Q requires less mousing than Frequency 2. Dynamic EQ section in the āfull viewā is cumbersome and limited. This is why I always have to switch to a single filter view. But then Iām limited to a single filter at a time. Unnecessary view switching when everything could be on a single screen. Frequency 2 is slowing me down.
Seriously, Frequency can be much more elegant with better workflow / UX. Current workflow is really outdated.
@battleangel,
Iām not against UX improvements. Iām one of those who always advocate the workflow improvements in Cubase/Nuendo and Dorico.
The UX and the UI designs are different things. The UX could be improved without changing the overall style of the UI.
Best regards,
Thurisaz
There are not many things on my list, it briefly is:
- Better hitpoint detection (doesnāt work well on bass guitar DI tracks)
- Allow phase flip for sends (allows neat mixing tricks - lookup Dan Worrallās Parallel Filter Tricks why this can be handy)
- Donāt break existing workflow behavior (Iāve reported this several times, but apparently Iām ignoredā¦)
- Performance improvements
- Stability improvements
Thatās it for me, plain and simple.
I just want freaking scrolling to be fixed on Cubase Mac version!!
Screen scaling for Cubase/Nuendo itself in 12.5% increments,
not only for HALion, Retrologue, etc.
I would like VariAudio to support polyphonic editing like Melodyne, so that I can edit individual notes within a chord. For example, I want to be able to change just one note in a chord without affecting the others.
Cubase renders faster when the buffer size is higher. Is it possible to implement in C16 a fixed buffer size (1024 or 2048) in the settings menu if something is bounced or rendered and then come back to the lower buffer size youāve set once bouncing/rendering is done? Cubase would feel snappier.
Indeed, this is the sweet spot for me. This and VU meters in the mix console and Iād pay for the upgrade.