Strongly disagree with this, Itās a distraction, hard to look at, inconsistent, unnecessary, and counter productive. Itās just eye candy to try and sell product.
Cubase and Nuendo are catered to professionals working with 100-1000 tracks, not 808 pop music, and whereas 808 pop music can and is made on Cubase⦠I doubt people working with 1000 tracks would want to work in Luna.
To be fair, this kind of console processing is mostly aimed at bussed tracks and is very nice to have if you prefer that āanalogā workflow. Some call it top-down mixing, itās how I like to work.
They could for sure explore the possibility of the Harrison mixbus approach whereby this kind of interface could co-exist within the current eco system as an option in the signal chain.
Itās not all that removed from the current channel strip really - just more flamboyant in design, and there could be maybe 8 pots at your disposal.
Throw some cross-talk across these ānewā mix-busses and theyād appeal well to a large crowd without upsetting composers and such like who donāt want such elements in eyeline.
Iām going to stick with the US date format snd say 11.5 will release today. And furthermore weāll then see version 12.0 a month later on December 1st
in the Dorico part of the forum someone was jokingly asking for mac icons to be resized to match other app icons in the dock in the next version, Daniel Spreadsburry did reply though that it was intended for next versions of Dorico 4, Cubase 12 and Nuendo 12.
I teased him asking if it meant that next Cubase version would not be 11.5 but 12, he didnāt reply but edited his reply though by deleting version numbers, so Iām pretty much sure weāll skip 11.5 to go straight into 12 this time
I donāt see where I said that : if looking at this in a more in depth way, you would see that it was the poster to whom I answered previously that suggested it. See belowā¦
What I actually said was that different āfavoritesā could be made in case of interface swaps.
I suggest you to use more both dots and the [enter] key : it would make your prose more readable. Beside this, in all your logorrhea, I still donāt see where using Cubase āfavoritesā could be a true limitation. Additionaly, I guess that professionals and studio engineers know how to deal with these kinds of situation, without yelling at the limitations of their tools. Overall, where is the interface swap, in all these cases ?
Thanks for the contempt : you start your journey in this forum in a rather conflicting way. See, there is no bed in my āstudioā - not enough place for it - only a room with enough gear to occupy more than half of the available surface. Iāll leave it at thatā¦
@lordadb is suggesting the settings are saved with project, as they are currently global settings thus if you change the inputs and outputs in one project, they change for all projects.
Meaning, if you had one project set up for mixing with external gear with all the ins/outs in External FX assigned, and then you had another project or template set up for tracking with all the Inputs assigned for recording - youāre going to have change everything,
Hence me pointing out, unbeknownst to yourself, that you are suggesting that someone potentially has to create Favourites/Presets for every project that is different from the next.
The contention is not only interface swaps. In fact, I donāt think this has anything to do with interface swaps⦠with the exception that perhaps the Favorites/Presets would be useful in the context of interface swaps - thatās not what this is about though.
Now, if you are a studio with 64 in/out, 32 of which are for a console, and the other 32 for direct to outboard⦠you could leave everything set up the same from one project to the next.
Or if you are a small/private/personal studio/hobbyist musician and you are only working by yourself and your faced with less dynamic situations on a day to day basis where one is making modifications to their studio setup to facilitate different project workflows⦠this also may not be a problem for you.
There are plenty of studios - professional home studios, and smaller indie facilities that operate on 16-24 channels, but have plenty of gear, or situations where additional gear has been rented or a client has brought in gear. One could say, ātough luck, spend another $3000 on AD/DAā⦠or the DAW could easily implement this better and as a feature, save people money, which is a selling point.
As it seems you have trouble reading paragraphs, you can see that I made adjustments to my formatting above. Professionals and studio Engineers know how to listen and thus are great problem solvers. You havenāt listened, and thus youāve given faux solutions, and thus havenāt solved problems and thus have now resorted to a more facetious tone because you donāt understand and thus are becoming frustrated with how people are replying to you.
Itās likely just a simple misunderstanding, rooted in you not having the same workflow as others, and not using features in a way that some people are trying to. Itās okay, itās all good.
I understand you are surmising that, if the user wanted to use any Intel-only plugin, an ARM-native Cubase would be forced to run its intel-compatitble version, and then only allow intel-compatible plugins?
I agree this hypothetical Rosetta Jail restriction would be very disappointing. Is it confirmed somewhere?
Maybe it would be possible within the VST spec for an ARM-native Cubase to host plugins running code on a different architecture, like the TC Powercore plugins did?
In my case, if Cubase went ARM-native, I would be fine restricting myself to its stock effects and instruments, and compatible third-party plugins for now. eg. All products from Waves, Spectrasonics, U-he, Pianoteq, Modo BAss, Modo Drum. etc. I can do a lot with those. And Iām confident that SoundToys, Native Instruments and other will come through with ARM-native versions soon.
(Also, with better cpu performance, I am moving away from sampled instruments to modelled/hybrid: eg. Pianoteq, Modo bass, modo drum, etc + synths of course.)
Itās actually a good way to find out which vendors are progressive and resourced and prioritised to fully support the Mac platform.
I am tired of the VST ecosystem being flaky on Windows lately: poor HiDPI support; Cubase crashing entirely due to one malfunctioning plugin; poor performance. Projects getting corrupted when unfreezing channels etc.
I think a host architecture with legacy technology debt (like Windows and Cubase) leads to poor performance overall.
Feels like time to reset to a clean, modern setup, with a sound foundation.
Unfortunately the information on the Whatās new in 11 website was published unintentionally and it has already been removed. Iām sorry for the confusion.
After that unintentional post on ''Whats new in 11 āā I could speculate (and take that with grain of salt) that there will no be 11.5 version at all and we will get instead 12 in maybe january-february of 2022⦠Interesting if there will be any more info next week published? 11.5 or 12 - Cubase is great everytime and always!