Cubase 11

General discussions on songwriting, mixing, music business and other music related topics.
Post Reply
Puma0382
Senior Member
Posts: 2013
Joined: Wed Dec 15, 2010 6:11 pm
Contact:

Re: Cubase 11

Post by Puma0382 »

Centralmusic wrote:
Sun Feb 16, 2020 2:22 pm
This Pic says it all...

FR: Volume and Pan Control in the Track Header!

(Screenshot taken from Nuendo Live) (!)
Nice. Hope you get a lovely large fader appearing when you click on that teeny, tiny volume block, so that fine adjustments are easier/more comfortable (especially when you're live). A double-click on the pan control to get a (the usual) large window as well..? ;)

Just checking.
System 1:- Win10 64bit, Gigabyte H81M m/board, Intel i7 4790 3.6Ghz, 16Gb RAM, NVIDIA GTX 750 Ti, 2 x 22" HD monitors; Steinberg UR44; Cubase Pro v10.5.20, WaveLab Pro v10.0.40, Studio One v4.6.1, Dorico Elements v3.5.10, Addictive Drums 2, Komplete 12, StylusRMX

System 2:- Win10 32bit, Q6600 2.4 Ghz, 4Gb RAM, NVIDIA GeForce 8400 GS, Delta 1010LT; Cubase Pro v8.0.40, WaveLab Pro v9.1.0, Komplete10, StylusRMX

Dragon96
Junior Member
Posts: 68
Joined: Thu Apr 07, 2016 3:20 pm
Location: Middle East
Contact:

Re: Cubase 11

Post by Dragon96 »

kostal wrote:
Sat Feb 15, 2020 1:04 pm
Dragon96 wrote:
Fri Feb 14, 2020 9:22 pm
I recommend:
1- Some jamming mode like Live session view
2- Rnd Portico and Yamaha Vintage Plugins as built-in
3- Listening AI assistant like Siri or Cortana
A Live style session view in Cubase is interesting. Digital Performer implemented it, but it’s still clunky. A more doable alternative is to simply have Ableton Link compatibility.
Yes, good idea!
I own and use Live professionally like Cubase and Link compatibility can help a lot. Of course that needs adding some kind of jamming engine inside Cubase.
Adel Al Agha عادل آل آقا
Singer, Music Producer & Trainer
https://radionama.com
Image

Dragon96
Junior Member
Posts: 68
Joined: Thu Apr 07, 2016 3:20 pm
Location: Middle East
Contact:

Re: Cubase 11

Post by Dragon96 »

Ivochkin wrote:
Sat Feb 15, 2020 1:32 pm
no need in Cubase 11. I want my 10.5 to be fixed and updated. I want 2-3 years of free updates for version 10.5 untill its fully stable and polished. I dont want to spend another 100 usd for buggy and rushed release. People who start threads like this should be killed.
It depends on your type of daily usage and people can have different user experiences if they are using Cubase for recording, editing or beat making or mixing and etc.
For me in 10.5 version Video Export, Import Tracks From Projects, Spectral Comparison EQ and LUFS and in 10 version Vari Audio 3, VR, Snapshots and GUI movement to Pro Tools style were great while 9 and 9.5 were like more a waste of money.
Adel Al Agha عادل آل آقا
Singer, Music Producer & Trainer
https://radionama.com
Image

cubace
Member
Posts: 942
Joined: Sat Jan 01, 2011 6:41 pm
Contact:

Re: Cubase 11

Post by cubace »

kostal wrote:
Sat Feb 01, 2020 10:18 am
Please.

- Proper EUCON support (reflect hidden tracks etc.)
- Rework of Macro system (scripting language, perhaps record macro moves/process live then save as preset?)
- Paid 500 series type options for channel strip. Perhaps an even deeper Console 1 integration with strips.
- Maybe a hardware controller for Groove Agent (see PreSonus or NI)
This are all connected. What needed is a proper interface for software interaction with cubase.
Python language is popular for this sort of functions. But I guess C++ or Java would also work.
Then you can start to integrate any hardware, you can do very advance macros.

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

cubace wrote:
Tue Feb 18, 2020 6:50 pm
kostal wrote:
Sat Feb 01, 2020 10:18 am
Please.

- Proper EUCON support (reflect hidden tracks etc.)
- Rework of Macro system (scripting language, perhaps record macro moves/process live then save as preset?)
- Paid 500 series type options for channel strip. Perhaps an even deeper Console 1 integration with strips.
- Maybe a hardware controller for Groove Agent (see PreSonus or NI)
This are all connected. What needed is a proper interface for software interaction with cubase.
Python language is popular for this sort of functions. But I guess C++ or Java would also work.
Then you can start to integrate any hardware, you can do very advance macros.
I’m not sure what you mean. EUCON is a proprietary ethernet protocol, now owned by Avid, for Avid hardware. Cubase is already compatible, but they don’t keep up with the developments.

And the potential hardware for Groove Agent will also be a very tightly integrated kit—not generic MIDI type control. And which third party will make a hardware controller for GA, if Steinberg offered some new way to interface?
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

cubace
Member
Posts: 942
Joined: Sat Jan 01, 2011 6:41 pm
Contact:

Re: Cubase 11

Post by cubace »

kostal wrote:
Fri Feb 21, 2020 3:56 pm
cubace wrote:
Tue Feb 18, 2020 6:50 pm
kostal wrote:
Sat Feb 01, 2020 10:18 am
Please.

- Proper EUCON support (reflect hidden tracks etc.)
- Rework of Macro system (scripting language, perhaps record macro moves/process live then save as preset?)
- Paid 500 series type options for channel strip. Perhaps an even deeper Console 1 integration with strips.
- Maybe a hardware controller for Groove Agent (see PreSonus or NI)
This are all connected. What needed is a proper interface for software interaction with cubase.
Python language is popular for this sort of functions. But I guess C++ or Java would also work.
Then you can start to integrate any hardware, you can do very advance macros.
I’m not sure what you mean. EUCON is a proprietary ethernet protocol, now owned by Avid, for Avid hardware. Cubase is already compatible, but they don’t keep up with the developments.

And the potential hardware for Groove Agent will also be a very tightly integrated kit—not generic MIDI type control. And which third party will make a hardware controller for GA, if Steinberg offered some new way to interface?
Avid as a plugin for cubase. It uses a programming interface, so do other like Frontier etc. It make no sense to have the programming interface secret or under NDA.

MIDI is a technology from the beginning of the 80's. I would love to so a standard protocol for this type of gadget so we dont need to worry about comparability issues. However the midi2.0 spec is a joke. And the it is not close to todays tech. Quite common today are REST, however im not sure that it is good for this. First you need some kind of function descriptions like device-tree's used in linux community. But you have two different design options. Let the DAW be smart and do the mapping or let the remote be smart and let DAW publish it capabilities. Today daw have drivers for various gears so it is the first. It's time to do the opposite. We are stuck we very old gears like the Mackie units, and the DAW vendors seems not to be intrested in use its potential. And it make a business sense too, they dont make money from it. Ok AVID does. Yamaha tries with Nuage. And the end users suffer from poor systems that might work with certain configurations the vendors promote in a time frame. Steinberg have is share of that with the CC121 and CMC's, they do what they did when they are new. Lot of functions have been added to cubase since they were added, but they new functions are not added to the hardware, and it's only about software that is missing.

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

cubace wrote:
Fri Feb 21, 2020 6:06 pm
kostal wrote:
Fri Feb 21, 2020 3:56 pm
cubace wrote:
Tue Feb 18, 2020 6:50 pm

This are all connected. What needed is a proper interface for software interaction with cubase.
Python language is popular for this sort of functions. But I guess C++ or Java would also work.
Then you can start to integrate any hardware, you can do very advance macros.
I’m not sure what you mean. EUCON is a proprietary ethernet protocol, now owned by Avid, for Avid hardware. Cubase is already compatible, but they don’t keep up with the developments.

And the potential hardware for Groove Agent will also be a very tightly integrated kit—not generic MIDI type control. And which third party will make a hardware controller for GA, if Steinberg offered some new way to interface?
Avid as a plugin for cubase. It uses a programming interface, so do other like Frontier etc. It make no sense to have the programming interface secret or under NDA.

MIDI is a technology from the beginning of the 80's. I would love to so a standard protocol for this type of gadget so we dont need to worry about comparability issues. However the midi2.0 spec is a joke. And the it is not close to todays tech. Quite common today are REST, however im not sure that it is good for this. First you need some kind of function descriptions like device-tree's used in linux community. But you have two different design options. Let the DAW be smart and do the mapping or let the remote be smart and let DAW publish it capabilities. Today daw have drivers for various gears so it is the first. It's time to do the opposite. We are stuck we very old gears like the Mackie units, and the DAW vendors seems not to be intrested in use its potential. And it make a business sense too, they dont make money from it. Ok AVID does. Yamaha tries with Nuage. And the end users suffer from poor systems that might work with certain configurations the vendors promote in a time frame. Steinberg have is share of that with the CC121 and CMC's, they do what they did when they are new. Lot of functions have been added to cubase since they were added, but they new functions are not added to the hardware, and it's only about software that is missing.
Okay, so you’re saying we should have third parties develop hardware controllers, but need a new open source protocol—something bigger than MIDI, Mackie Hui, EUCON, etc etc. Right?

Something like that can only work if it’s an industry standard and not just Steinberg-only. Or else you will have something like Halion vs. Kontakt. Almost no one develops content for Halion, because almost everyone uses Kontakt.
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

User avatar
Quietly
Member
Posts: 335
Joined: Fri Dec 17, 2010 4:15 pm
Contact:

Re: Cubase 11

Post by Quietly »

shanabit wrote:
Sat Feb 01, 2020 10:53 pm
How about just eliminate the show stopping bugs in 10.0.5 and 10.5. that would be a great update IMO
Exactly. Not sure adding anymore bells and whistles to something that has unsolved problems is a good idea. HiDPI Scaling is still not fixed and it is something that younger/newer Daws are doing without any problems. Studio One is an example of being able to do things far more quickly and hassle free, Reaper,Ableton and Bitwig are the same. Cubase is now showing its age and bringing out Cubase 11 without fixing all the problems that came with 10 will be a massive mistake.

At the moment I cannot use Cubase because of the Scaling issues and I can't even sell it at half price on eBay and I am not going to give it away. Long time user who has so many Cubase Projects that keeping it would make a lot of sense but the minimum that Cubase could do is make it usable, before asking for more money for an update.
https://soundcloud.com/gerry-cooper-855281238
Studio One 4.6. Windows 10 Pro 64 bit. Intel Core 2 Quad CPU Q9550 @ 2.83 GHz 4GB RAM. ASUS Radeon R7-259 Graphics Card , Focusrite Scarlett 2i4. Komplete Kontrol S61 and HS80M Monitors. Komplete 10 Ultimate, Symphobia, Ozone 8 etc

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

Quietly wrote:
Mon Feb 24, 2020 1:07 pm
shanabit wrote:
Sat Feb 01, 2020 10:53 pm
How about just eliminate the show stopping bugs in 10.0.5 and 10.5. that would be a great update IMO
Exactly. Not sure adding anymore bells and whistles to something that has unsolved problems is a good idea. HiDPI Scaling is still not fixed and it is something that younger/newer Daws are doing without any problems. Studio One is an example of being able to do things far more quickly and hassle free, Reaper,Ableton and Bitwig are the same. Cubase is now showing its age and bringing out Cubase 11 without fixing all the problems that came with 10 will be a massive mistake.

At the moment I cannot use Cubase because of the Scaling issues and I can't even sell it at half price on eBay and I am not going to give it away. Long time user who has so many Cubase Projects that keeping it would make a lot of sense but the minimum that Cubase could do is make it usable, before asking for more money for an update.
Why present this as a zero-sum game? .5 updates are paid for features. We have a year for any bug fixes—why don’t you convince Steinberg to only fix bugs. And why either/or? The whole team. The whole corporation. All departments. 🤷🏻‍♂️

I want to hear a Steinberg representative say this here; that new features or improvements are the only thing stopping bug fixes; that one with the other is impossible.

Quite a few things on the list are not new features per se;they are enhancements and improvements or auxiliaries.

I feel like some of us here like to think that there is one programmer slaving away at Steinberg who does everything.
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

cubace
Member
Posts: 942
Joined: Sat Jan 01, 2011 6:41 pm
Contact:

Re: Cubase 11

Post by cubace »

kostal wrote:
Mon Feb 24, 2020 8:42 am
cubace wrote:
Fri Feb 21, 2020 6:06 pm
kostal wrote:
Fri Feb 21, 2020 3:56 pm


I’m not sure what you mean. EUCON is a proprietary ethernet protocol, now owned by Avid, for Avid hardware. Cubase is already compatible, but they don’t keep up with the developments.

And the potential hardware for Groove Agent will also be a very tightly integrated kit—not generic MIDI type control. And which third party will make a hardware controller for GA, if Steinberg offered some new way to interface?
Avid as a plugin for cubase. It uses a programming interface, so do other like Frontier etc. It make no sense to have the programming interface secret or under NDA.

MIDI is a technology from the beginning of the 80's. I would love to so a standard protocol for this type of gadget so we dont need to worry about comparability issues. However the midi2.0 spec is a joke. And the it is not close to todays tech. Quite common today are REST, however im not sure that it is good for this. First you need some kind of function descriptions like device-tree's used in linux community. But you have two different design options. Let the DAW be smart and do the mapping or let the remote be smart and let DAW publish it capabilities. Today daw have drivers for various gears so it is the first. It's time to do the opposite. We are stuck we very old gears like the Mackie units, and the DAW vendors seems not to be intrested in use its potential. And it make a business sense too, they dont make money from it. Ok AVID does. Yamaha tries with Nuage. And the end users suffer from poor systems that might work with certain configurations the vendors promote in a time frame. Steinberg have is share of that with the CC121 and CMC's, they do what they did when they are new. Lot of functions have been added to cubase since they were added, but they new functions are not added to the hardware, and it's only about software that is missing.
Okay, so you’re saying we should have third parties develop hardware controllers, but need a new open source protocol—something bigger than MIDI, Mackie Hui, EUCON, etc etc. Right?

Something like that can only work if it’s an industry standard and not just Steinberg-only. Or else you will have something like Halion vs. Kontakt. Almost no one develops content for Halion, because almost everyone uses Kontakt.
es, it need to be a standard. If it is a network protocol it can be done as IETF work, or it can be AES or midi3.0 or something new. But it will of course requires that some vendeors like yamaha, apple, icon, mackie etc all agree to attack avid's leading on this market. More or lesss I think it their only chance to keep there share of PRO market.

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

cubace wrote:
Mon Feb 24, 2020 5:59 pm
kostal wrote:
Mon Feb 24, 2020 8:42 am
cubace wrote:
Fri Feb 21, 2020 6:06 pm


Avid as a plugin for cubase. It uses a programming interface, so do other like Frontier etc. It make no sense to have the programming interface secret or under NDA.

MIDI is a technology from the beginning of the 80's. I would love to so a standard protocol for this type of gadget so we dont need to worry about comparability issues. However the midi2.0 spec is a joke. And the it is not close to todays tech. Quite common today are REST, however im not sure that it is good for this. First you need some kind of function descriptions like device-tree's used in linux community. But you have two different design options. Let the DAW be smart and do the mapping or let the remote be smart and let DAW publish it capabilities. Today daw have drivers for various gears so it is the first. It's time to do the opposite. We are stuck we very old gears like the Mackie units, and the DAW vendors seems not to be intrested in use its potential. And it make a business sense too, they dont make money from it. Ok AVID does. Yamaha tries with Nuage. And the end users suffer from poor systems that might work with certain configurations the vendors promote in a time frame. Steinberg have is share of that with the CC121 and CMC's, they do what they did when they are new. Lot of functions have been added to cubase since they were added, but they new functions are not added to the hardware, and it's only about software that is missing.
Okay, so you’re saying we should have third parties develop hardware controllers, but need a new open source protocol—something bigger than MIDI, Mackie Hui, EUCON, etc etc. Right?

Something like that can only work if it’s an industry standard and not just Steinberg-only. Or else you will have something like Halion vs. Kontakt. Almost no one develops content for Halion, because almost everyone uses Kontakt.
es, it need to be a standard. If it is a network protocol it can be done as IETF work, or it can be AES or midi3.0 or something new. But it will of course requires that some vendeors like yamaha, apple, icon, mackie etc all agree to attack avid's leading on this market. More or lesss I think it their only chance to keep there share of PRO market.
Well, we do have MIDI 2.0 that's been announced. Let's see what happens with that.
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

cubace
Member
Posts: 942
Joined: Sat Jan 01, 2011 6:41 pm
Contact:

Re: Cubase 11

Post by cubace »

kostal wrote:
Fri Mar 06, 2020 11:30 pm
cubace wrote:
Mon Feb 24, 2020 5:59 pm
kostal wrote:
Mon Feb 24, 2020 8:42 am

Okay, so you’re saying we should have third parties develop hardware controllers, but need a new open source protocol—something bigger than MIDI, Mackie Hui, EUCON, etc etc. Right?

Something like that can only work if it’s an industry standard and not just Steinberg-only. Or else you will have something like Halion vs. Kontakt. Almost no one develops content for Halion, because almost everyone uses Kontakt.
es, it need to be a standard. If it is a network protocol it can be done as IETF work, or it can be AES or midi3.0 or something new. But it will of course requires that some vendeors like yamaha, apple, icon, mackie etc all agree to attack avid's leading on this market. More or lesss I think it their only chance to keep there share of PRO market.
Well, we do have MIDI 2.0 that's been announced. Let's see what happens with that.
I wrote midi3.0 since midi2.0 does not solve anything regarding this. It might have been relevant in 1987 or something,a ctually I think it will cause problem than what it solves.

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

Lets wait and see!
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

ggmanestraki
Member
Posts: 230
Joined: Sun Feb 09, 2020 7:33 pm
Contact:

Re: Cubase 11

Post by ggmanestraki »

+1

All feature requests are fair, and all are valuable. It's very difficult to favor one over the other.

I agree with all of them, and prioritize what I consider is mostly overdue. Like the Audio Connections window, or things that obviously (ie visually) don't agree with the current design.

However, I would also like to see a clean-up. Features that Steinberg feels they don't want to maintain, they must clearly state so and phase them out. But there are many small things scattered in all corners of the program that need fixing. Missing or not working key commands, remote controller assignments, small GUI issues, one in this window, one in another. All these small quirks amount to a certain stiffness, that I, personally, would greatly appreciate if it went away.

For example to know that this "Apply" button in this menu is useless but we haven't taken it out, or that the Import Key-commands button is a relic from past days and that we shouldn't use it... it doesn't look logical to me. Remove them and be done with them! Will there be some special-cases impacted from the removal? Evaluate, provide a workaround, document it clearly and all's well!

Ideally, I would expect each and every one of the programs editors to feature:

-Fully modular Left, Right and Bottom Zones. Build our own workspace. This goes for toolbars, transport panel and bar included. Adjust height in lines, freely place buttons, just like we can do with the "Track Controls Settings". (sneak a fader and a panner there please)
-Full Key-Command Control. Everything should have a key command. Not enough keys on the keyboard? I don't think so. Being able to load key-command presets on the fly would make this wonderfully manageable. Imagine having a whole keyboard at your disposal JUST for Score Editting, or midi editting.

One of Cubase's "problems", well not problems, I just can't find the right word now, is that while it's choke full of features, sometimes they are hidden from the user in menus and places a user would overlook. Encouraging modularity, the program can highlight its features, by means of having the users put the right function in the right place for them.

J Buckingham
Member
Posts: 447
Joined: Wed Aug 01, 2018 6:44 am
Contact:

Re: Cubase 11

Post by J Buckingham »

+1 for Cubase 11
Last edited by J Buckingham on Fri Mar 20, 2020 6:27 am, edited 2 times in total.
Cubase Pro 10.5.20, i7 9800x @ 4.2GHz, 128GB RAM, Windows 10 Home, Focusrite Scarlett Solo, Geforce GTX 1060

User avatar
tomateck2
New Member
Posts: 44
Joined: Tue Apr 30, 2019 10:48 am
Contact:

Re: Cubase 11

Post by tomateck2 »

+1000 and I add the full screen mode for mac users, I hope It will be able without the need of pay for a new upgrade for v11.
Cubase Pro10.5, Dorico 3.1

dstenning
New Member
Posts: 30
Joined: Sun Sep 22, 2019 3:15 pm
Contact:

Re: Cubase 11

Post by dstenning »

+1. Agreed. A sensible list indeed.

I'll add just one thing :- Ableton-style. SESSION type page with clip/scene launching.


Along with gapless audio I'd like to be Able to use cubase as a pattern mode tool -maybe combining aspects of the arranger feature too as there would be some crossover.

cmbourget
Member
Posts: 309
Joined: Fri Dec 28, 2012 3:47 am
Contact:

Re: Cubase 11

Post by cmbourget »

Don't forget the clipgain. Great in Pro Tools, stupid in Cubase. I don't understand why.
Cubase 10.5, Pro Tools 2020
PC Windows 10, Intel Xeon E5-2667 v2 3.30GHz, 8 cores, 64 Go
PrismSound Titan, Solo Be and Focal sub, etc, etc.

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

Great suggestions! Added.
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

In_Stereo
Senior Member
Posts: 1533
Joined: Wed Oct 12, 2016 6:21 pm
Contact:

Re: Cubase 11

Post by In_Stereo »

Dragon96 wrote:
Mon Feb 17, 2020 11:13 pm
kostal wrote:
Sat Feb 15, 2020 1:04 pm
Dragon96 wrote:
Fri Feb 14, 2020 9:22 pm
I recommend:
1- Some jamming mode like Live session view
2- Rnd Portico and Yamaha Vintage Plugins as built-in
3- Listening AI assistant like Siri or Cortana
A Live style session view in Cubase is interesting. Digital Performer implemented it, but it’s still clunky. A more doable alternative is to simply have Ableton Link compatibility.
Yes, good idea!
I own and use Live professionally like Cubase and Link compatibility can help a lot. Of course that needs adding some kind of jamming engine inside Cubase.
I would heartily endorse not putting an Ableton Live-like thing in Cubase. Cubase is such a deep and multilayered piece of software, and running Live alongside with it is a better idea than trying to mash it into Cubase (which will never be as good as Ableton Live...because it's Cubase and not Ableton Live). But I have no need for Ableton (I know it pretty well and just don't like it for the way I work), so this option is a very good compromise to me that keeps Cubase Cubase-focused and also lets people use Ableton if they love it.

My opinion, anyway! :-)
Latest Cubase 10.5, Windows 10 Pro 64-bit, i9 10920x 12-core 4.8gHz, 128 gigs RAM, AMD RX-550 , plugins galore, some hardware, a bunch of real instruments and synths, Apollo 8 TB, etc., etc., and two cats

Glorian_Gray
Junior Member
Posts: 78
Joined: Mon Oct 08, 2018 9:00 pm
Contact:

Re: Cubase 11

Post by Glorian_Gray »

lovegames wrote:
Sat Feb 01, 2020 10:55 pm
kostal wrote:
Sat Feb 01, 2020 9:22 pm
lovegames wrote:
Sat Feb 01, 2020 9:17 pm
revamp of external audio connections is on of the most important. I would pick it over everything on that list combined
Okay. Lol.. I'm sensing a pattern, my friend! Good luck.
The pattern is logical analysis and conclusion.

I have a personal list of about 200 feature requests spread out across multiple notebooks crammed with notes, some of which are the ones you've listed. I know every quirk about this program like how StepDesigners CC modulators are Cubase global and don't save/recall project to project which is annoying and ridiculous.
- Waveform anti-aliasing.
Nice but non-essential.
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance (if anything decrease it)
- Professional metering
Nice, but again, can live without, have 3rd party tools as most do.
-Isn't going to significantly speed up workflow
-Isn't going to significantly assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance (if anything decrease it)
- Moving tracks in mixer.
Nice, but meh, I've lived without and can continue to. I think potential problems with this is the folders aren't displayed in mixer.
-Could speed up workflow a bit, but not significantly. I always keep my tracks organized before I'm opening up the mixer.
-Isn't going to significantly assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
- Warping on arrangement window/tracks.
Not sure what you're talking about here
- Better fonts/colors.
-meh, everything's fine, check your OCD maybe.
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance
- Ability to turn on and off grid lines in arrangement window.
This could be useful with a key command but again:
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance
- Multi-track free warp
-This could be useful, but honestly, I avoid Warp at all costs. cut-slide-xfade is still the preferred method - doesn't degrade the sound variably across the entire project from one section to the next, doesn't create artifacts, etc.
- Nudging of events and midi notes by specific musical or time values by key command and nudge tools (without the use of logical editor).
Why? What is wrong with keybinding PLE scripts? I think you can even skip PLE and just use macros for this:
--Cut
--Nudge Cursor Forward by quantize value
--Paste
- Proper EUCON support (reflect hidden tracks etc.)
I'm guessing Steinberg/Yamaha are developing their own control/console interfaces such as Nuage.
- Gapless audio engine
Nice, would be good to get rid of any slight annoyance like this
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
- Folder group tracks (folder tracks fold/reflect in mixer)
Manageable without this, can survive.
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance
- Range selection edit on event gain/envelopes
-Could be nice, but you can set up a macro to split the selection, trim by -6db and crossfade all in one key stroke.
- Stereo plugins on mono tracks.
Could be useful sometimes, but I hardly run into this and a solution is a keystroke away and couple clicks away.
- Range selection edit on tempo track.
I'll give you this one, anyone doing a lot of tempo work, tempo editing is a bit finicky.
- Ability to show only event name or event description—not both. Or events follow track names exactly always. Also event names to be tabbed thinly so they don’t overlap waveforms (see Logic or Cubase 5?)
Nice but can live without, actually if I were to suggest one thing here, it would be to resolve the name obscuring the waveform. the name should be behind the waveform or transparent or something.
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance
- Tabbed VST views
This could be good, I'll give you this one. Some sort of VST window management
- Slicing in sampler track
This could be good, I'll give you this one.
- Smooth playhead cursor (see Logic Pro X)
Not sure what you're talking about here - my cursor is fine.
- Inspector icons/workflow enhancement.
huh?
-Isn't going to significantly speed up workflow
-Isn't going to assist in improving audio/production quality
-Isn't going to contribute or help deliver creative output
-Isn't going to improve performance
- Elastic band in midi editor like Ableton
Not sure what this so I'll pass personally
- Improved markers display/visuals
The only thing I would suggest here is that there is an option for markers to visually extend their legs down to the bottom of the project and to pin marker tracks to the top ruler or in the project Overview which would give it a use.
- Drum editor and key editor enhancement (patterns).
- Everythings pretty good to make music and compositions. What I would improve actually is the DrumMap editor which is still an archaic line by line text column editor thing.
- Triplets and swing grid in warping
I perform triplets. I think isn't there a way to hack your own grid map? I thought there was a way to do this. maybe not.
- Better way to import and store swing/groove Q presets.
Sure I don't know, I guess. sort of a yawn. I'll throw you a bone I guess.
- LFOs/VST modular routing.
If you're talking FL Studio cross patching, Not really what Cubase does nor is it what I want my head to be contending with while working in Cubase. Cubase hosts things that does this. Last thing I would want is for someone to send me their project to work on and have this random *flower* scattered everywhere.
-so, no. bad idea.
- Ableton Link support
-Why? Never understand why people have utility for this, is it even realistic? There's already ways of achieving this as stated above. Just do some work in Ableton, commit, export. I'm more concerned with improving Cubase as a self-contained program integrating other Steinberg assets.
- Paid 500 series type options for channel strip. Perhaps an even deeper Console 1 integration with strips.
They could do this with RND (I have a thread suggesting so), but this isn't a priority, there's already so many plugin options out there offering colours.
- Maybe a hardware controller for Groove Agent (see PreSonus or NI)
This would be good and is something missing. Steinberg has the software asking for HW drum control, Yamaha has the resources. They could team up with Roger Linn and Dave Smith (the aesthetics and nerd factor matches Cubase)
- A way to edit transient settings on elastique algorithms. Etc.
Meh, I mostly avoid these utilities but they have their purpose, if some tweakable settings gave significantly better results, sure.


So, it's only an alright list. And this is the problem with the Feature Requests forums, no offense, but there is a lack of deliberative criticism on what people suggest and why and we just end up with huge lists without a consolidated direction.

Audio Connections

a.) It's still the old GUI, so it needs an update regardless.

b.) While the industry swung hard into being mostly ITB, it swung back and leveled out between the two in which a lot of people are moving back to or are aspiring to work with analog equipment, gear. Eurorack exploded, 500 series exploded, Behringer is releasing affordable knockoffs, lots of guitar pedal makers as always, DIY pro audio community exploded, used Synth market exploded, pro audio external hardware effects are returning such as the new Neve AMS RMX16 500 and the Eventide H9000. All of Steinbergs new marketing has eurorack and synths in it.

Steinberg has not facilitated this change, in which people have more gear than they do AD/DA and that is a big problem. Audio Connections can't be shared, they get stolen, they break from project to project and don't recall properly sometimes. External Audio Connections to make it worse, doesn't have a full-recall presets only individual presets. If you are running a studio with only 16ad/da which you are using sometimes 16 channels for recording inputs, and then 12 of those are being switched to analog gear for mixing, and then you're having to switch back to full recording set up, and then you're doing a combination of synth recording and external mixing, etc, etc. It's incredibly non-viable way of working.

Now the vast majority of people who have Cubase, probably have no gear, perhaps not even AD/DA and just use their laptops headphone out. But this is important for Steinberg to facilitate professional studios and high-end hobbiests. Steinberg is at a critical point to break a bigger chunk off of that market for themselves, and improving this aspect of Cubase is essential to that.
Mr. "Meh", I'd suggested you to keep your "meh" with you, okay! You're not alone here, and I personally support that guy above with his list. Your nasty tone is annoying. Watch your mouth and keep your disrespectful behavior away. If you could live without this list of improvements - okay, but don't speak for other people who uses this DAW.
All the best.
Cubase Pro 10 | Intel Core i7-9750H 2.60GHz | 8Gb Memory | 1TB Solid State Drive | Windows 10 Pro (1903)| Steinberg UR22 Audio Interface

Glorian_Gray
Junior Member
Posts: 78
Joined: Mon Oct 08, 2018 9:00 pm
Contact:

Re: Cubase 11

Post by Glorian_Gray »

Hi there @kostal
Nice bunch of improvements you have suggested!
I have few of mine, it would be awesome if add 'em into your list too!

Here:

I personally use sample track for 808 bass triggering, I put it mono and play with glide knob to creat a crazy legato effect (i'm edm producer btw)
But I noticed that when I play a whole C note for e.g and put a quarter E note in octave above (not at the same time but at the half of a whole lower C note) - this do not produce that effect that I'm looking for - I think, that problem is that "sample track" is retriggering the note again - what is not required.

I could do this effect simply in FL Studio, Ableton etc, but I can't do so in Cubase's sample track. I hope this description is make a sense, anyway if it's not that clear, I could try to explain again. Thnx.
-----

Request for Drum Editor:

There's a CC field inside, when I could draw velocity curve etc. Could you, Steinberg make it possible to add CC commands for preloaded VSTi's (GA) knobs, sliders, to manipulate such settings like coarse, fine for particular intruments: hihat, snare. Hope you've got the idea. I saw this feature in Studio One where you could pick up any settings from Impact's sounds and draw the CC curves in drum editor. That would be awesome in Cubase as well.

Thank you in advance, all the best!
Cubase Pro 10 | Intel Core i7-9750H 2.60GHz | 8Gb Memory | 1TB Solid State Drive | Windows 10 Pro (1903)| Steinberg UR22 Audio Interface

kostal
Member
Posts: 210
Joined: Sun Sep 14, 2014 4:28 am
Contact:

Re: Cubase 11

Post by kostal »

Glorian_Gray wrote:
Thu Mar 26, 2020 4:43 pm
Hi there @kostal
Nice bunch of improvements you have suggested!
I have few of mine, it would be awesome if add 'em into your list too!

Here:

I personally use sample track for 808 bass triggering, I put it mono and play with glide knob to creat a crazy legato effect (i'm edm producer btw)
But I noticed that when I play a whole C note for e.g and put a quarter E note in octave above (not at the same time but at the half of a whole lower C note) - this do not produce that effect that I'm looking for - I think, that problem is that "sample track" is retriggering the note again - what is not required.

I could do this effect simply in FL Studio, Ableton etc, but I can't do so in Cubase's sample track. I hope this description is make a sense, anyway if it's not that clear, I could try to explain again. Thnx.

Thank you in advance, all the best!

Hey, thanks.

So I tried to recreate what you said in the sampler track here. And the glide works just fine. I'm not sure what you mean by "sampler track is retriggering."

Is the C note being retriggered when you release the E note? Or the glide is not happening?
Cubase Pro, Nuendo, Wavelab, Halion, Groove Agent // MacOS

Ehabmxd
New Member
Posts: 49
Joined: Fri Mar 27, 2020 11:53 am
Contact:

Re: Cubase 11

Post by Ehabmxd »

To Steinberg:
Hello I am use studio one 4.6 professional

And I want to buy Cubase pro 10.5 and I have a plan to buy a lot of ur plugins
But In Fact am very afraid
Sorry for saying this , The first thing.. ur customer service is not good
a lot of ur customers they went to another DAW Because a lot of things
Cubase , neuendo , works only with USB Dongle ..!!
they cant activates ur Softwares easily and they took hours and days to solve the problems, and some of them could not solve it go check youtube videos , comments about issues ..
I read a lot of customers problems, They sent u an emails to find solution and now they ask some of them in the comments :
(Did u find a solution to this problem)

we are in 2020 and u r still using this old method elicenser usb dongle .. !!
There is no objection to buying and using it to activate if this is your policy
But the program does not work except this USB,, Every time when we running the Cubase ??

This indicates lack of respect for the customer
if the usb missed what can I do ? if the usb damged on my laptop bag I will lose my sessions, I cant do any thing and maybe if I get the new dongle cant download it again
I bought a lot of product that’s require a hard disk and USB flash memory to activation , after activation I no longer use the usb to run the software , this makes the customers more comfortable from being lost or malfunctioning.. I bought a lot of software form the biggest international companies like ADOBE
I can use my adobe collection with out USB and the collections can be transferred on any device provided that the collections is on only one device ..

The worlds has changed and now we are use laptops and small pcs .. and we cannot plug this dongle all times..!!

Do u have any plan to make the usb elicenser only for activation ?
after activation we can use the cubase without USB Dongle
we do not mind when receiving an update we plug this dongle again..

Please Steinberg make some changes to your approach in your very old way..
Which makes the user afraid of losing everything due to any damage, they are buying ur products and u TREAT HIM LIKE A PRISONER ..

I bought studio one professional they gave me 5 copies I can managed every device in my presonus profile ADD NEW , EDIT , DELETE USERS .. (and thier customer care is very good) most people now use studio one just a download link and the way yo avtivate it is simple it does not require more waiting and we can run the software freely without any USB

With presonus I have remote control app to the DAW for studio one I cant easily record my self with my android mobile ,
why you don’t have REMOTE APP FOR IOS & ANDROID .. this is a very modern way
the customers will grow up with every service u offer them

CUBASIS APP FOR ANDROID ??
U don’t support android ? the android users its more than apples more Cubase user I know them using android phone and and android tablet

support multitouch for Cubase 11 we are now use a touch screen monitors for pc and touch laptops
let users freedom choose between (2 modes) TOUCH MODE .. STANDARD MODE most users now have to complete the mix with windows tablets and this causes the user to purchase more than one copy

PIANO ON SCREEN In the midi section make ur software’s CREATIVE add a full touch piano on screen with large keys for touch playng and record at the same time .. this makes it easier to compose any where without any external device a lot of people now use touch device laptops, pcs , tablets
ROLAND ZAINBEATS DAW SOFTWARE they add beautiful multitouch support and piano on screen but the software its for beginners

Can u hear our voices ? and take care of your customers and their opinions

( we have no problem using the USB Dongle to Activate , but after that it must be plugged only if we have an updates )

Sorry for my long story
I wish u all the best
Best regards

absolutelylasteffect
New Member
Posts: 2
Joined: Fri Mar 27, 2020 4:43 pm
Contact:

Re: Cubase 11

Post by absolutelylasteffect »

I use cubase from long time, together with others softwares and for soundtrack projects would be great if the VSTRack could be shared between projects, similar to V-Rack in Digital Performer. Many times I need to opened different project that have the same VSTi with the same patch, Halion 6 and Kontakt for example with ton of samples to loads. Every time to switch Cubase reload all.
Thank you

Post Reply

Return to “Steinberg Lounge”

Who is online

Users browsing this forum: No registered users and 4 guests