feature requests usually consist of one single feature. Your feature request is a list… and according to your tag it should be about the score editor alone.
If I were you I would support existing feature requests by leaving a vote. If there is no such request I would create a new one. Why? It is highly unlikely that someone will support the exact list that you have posted above. The more votes the more attention.
We don’t know how Steinberg deals with votes. What we do know is that feature requests with many votes are heard and that chances are higher that you’ll see them in a future version (although this might take time).
It could just be my workflow, but I find Save Selected and Load Selected very valuable. Ever loose the drum track names/settings of 24 Toontrack SD channels for example?
I also use this feature daily to load similar plugs, for example 5 compressors, into 1 mix console track to determine which plug is going to work best for my objective, then of course remove the other 4.
Going further, if you create a standardized mix console template, Save/Load Selected is a quick way to load plugs that are typically associated with that particular track.
Save template without media I have been writing about in the forum for a decade I think at this point. I dont have enough upvotes for this one
… and your other point to import track settings (inserts, EQ and Send inc Ins and outs) onto a selectred track track in your song from another song (not just import the whole track) - an enhancement to Import from Project.
Some say the ‘save FX chain presets’ on Project A and then import them on Project B is the answer - but it takes a long time to exit a large project B and load up Project A. save the settings you want, then close that and Open project B- then go your track and load the chain. This process could be super simplified by being able to import selected channel settings from a channel from another project.
Hi @mart,
Something like that exists in Dorico - “Playback Templates”, but for instruments.
Similar conception could be used for “FX Chain Templates”. That way we will be able to switch between different “FX Chain Templates”.
There is no rule on the forum that the tag requires only a single feature to be requested, no matter that it’s written in a singular form.
This means the interpretation about the single feature request is just yours.
About the score-editor tag .
Since the Score Editor is mentioned among the requests… tagging it is just fine.
About the features I have listed in the first post.
For the most of them I’m the original requester, so I can’t vote multiple times to my own requests.
For some of the features I’m not the original author, but I’m the one to support them the most. Once again I can’t vote multiple times.
All of them aren’t new as feature requests. Just they are an essential part of the rising ecosystem around the products of Steinberg like Cubase/Nuendo and Dorico.
The Voting system.
It isn’t a bad thing but definitely very rarely something here depends on the voting.
It’s limited.
The implementation of features depends on other things (the importance for the software, the value it will bring, the time needed for the implementation… etc.).
I hope I was able to bring some clearance with this reply!
all good, that’s why I wrote that feature requests usually consisted of one single feature. You do you! I was just trying to point out that there are more effective ways to promote a feature request.
Yes, the voting system has its limitations and I agree with most of your points. Again, my post aimed at showing best practice tipps and not rules. Sorry, if my post came across that way. That wasn’t my intention at all.
I’ll say it again: many of the recently added features had been high up in the voting chart.
Either it is a huge coincidence that Steinberg has a roadmap that coincides with what forum users vote for or they simply let themselves be influenced by the votes.
My wishlist:
Order tracks (sort) by a chosen sort order.
Sort by name, or chronological, track type, color, etc.. Let’s say I click “Type” then all the basses would be sorted to the top, then the drums etc. “Time” sorts by events on the timeline, chronologically; by the beginning of its first event.
Make the media bay read/write metadata to the files. No proprietary database nonsense. Write metadata to the file and read from the file. Let audio files carry their own metadata.
On my 4 year old PC Cubase takes 12 seconds to an empty project window. How much quicker do you want it? It’s the number of plugins and tracks that take time, and I doubt if Cubase can do anything about that as it’s outside of Cubase.
Yes, please!
I think this could add a lot of overhead when navigating the MediaBay - all that disk activity!
That’s pushing it. I don’t know of anything else that takes longer than three seconds. Most things are almost instant. One of the problems is steinberg products refresh their license every single time, instead of just having a license install system. We all have to suffer for a software company to have slightly more security. Cause the same governments that put people in a cage for hurty tweets doesn’t give a damn about enforcing piracy law. Cause if they did software wouldn’t have to be a hardened fortress.
The media bay could have a database. But it would create the database from the contents of the disk. You would do an initial scan to build its index. That would take the file data and mirror it into its own database (import). There is your cache for speed and efficiency.
???
IMO, an internet connection in order to machine-activate a product (programs as well as content packs) is mandatory only once. There may sometimes be random checks, though.
After the activation process via Steinberg Activation Manager (SAM), some local representation of this process will be left on a system harddrive, and also the Steinberg license server system will remember a PC’s technical fingerprint (including its “friendly” machine name). From your Steinberg ID’s user account, you can see and even deactivate all your running - and machine specific - license activations. Also, there’s even an option to offline-activate a product (important for film post-pro studios etc.). Both SAM plus Steinberg’s server infrastructure combined is in fact the licensing install system.
The MediaBay does have a database, its database container file type ending does point exactly at what it is: a *.db database file.
A simple phase correlation meter on every stereo channel/buss, viewable concurrently in the mixer would be nice. Plus the ability to default set the Frequency 2 EQ as the standard channel EQ.
