Great nurturing video, as usual from you! Hope they fix the multi core performance issues with new gen CPUs. Just build a new Win 11 PC with an i9 14900K, 64GB RAM, SSD M2... a beast. Already optimized all the OS all... but to my suprise I'm getting CPU spikes (overloads) on Cubase 13, even with a few plugins loaded. And also loading just a few plugins quite loads got the CPU. Quite frustrating. Tried everything within the Studio tab in Cubase 13, with different settings of the ASIO guard, but without no success. I see they recommend to set the cores affinity in the task manager while Cubase is running, but it seems an awkward solution, so didn't tried yet. Considering this, I'm a bit hesitant to get the new vers 14 if there's no improvement in that issue!
Thank you. Very disappointing that the multi-core performance is still a thing. They previously announced that they tackled it in Cubase 13 I believe which I even made a video about. I would definitely contact support about this.
Another very informative video! I have noticed that loading larger projects in 14 is faster than 13. I also think that closing projects is faster as well. (Probably for the same reason) But, I haven't noticed any similar optimization in playing back tons of tracks with tons of plugins. It could be there but just maybe a small improvement. Have you noticed any CPU optimization on recording or playback? And yes, I think that 14 is even more stable than 13. 13 was a banner release for Steinberg as probably the most stable release right out of the box I had ever used. But 14 does indeed seem to be more stable than 13. All-in-all a really great release!
Thanks for confirming my experiences as well. Great that your projects also load faster. Didn’t notice any playback/recording performance improvements yet.
The new score editor was a game changer for me. I have loads of parts originally played on a keyboard that I'm having real brass/string players come in to play. Even without quantization, it does a great job of producing readable parts on the default settings. If necessary, I can import the parts straight in to Dorico for further refinement. It does lack some features that the old score editor had, but it's much, much more intuitive. Steinberg definitely got this right as far as I'm concerned.
I feel sad when it doesn't support showing my lyrics from version 13, and also from the standard midi file. There is no way around. If I want my lyrics in the score editor, I have to punch every single word again. 😢
Using the score editor heavily since the early 90s I'm slightly shocked by the new score editor's loss of functions and features. Especially the automation features of how the score is displayed with no chance to edit it how I want it to look pisses me of.
As a long time user of Dorico Pro, I don't think I'll be using the scoring features within Cubase. I think the update to include Dorico scoring is great, just can't see why I would use it. I'd be interested to know what other Dorico users think. Regarding the grace period comments, one detail they don't mention in the release notes: There is no free upgrade / grace period for those who purchased Cubase with the recent special anniversary pricing vouchers, as I found out. I guess getting Cubase Pro 13 for 70% off was all they were willing to offer. While saving yet another $99 would have have been nice, I have to agree with Steinberg's reasoning. Thanks for the video!
You're welcome. And yes I can imagine that you'll keep using Dorico if you have that already anyway. Didn't know about the grace period in combination with the earlier anniversary deal. Thanks for adding that!
The score integration is what I've wanted for years. But I'm now retired from composing and I'll only do it again when I can give verbal instructions and both score and mockup will be created automatically.
09:39 not so much I'm afraid and I wouldn't hold my breath for this to remain true. The 64bit files of C14 won't be "forward" compatible with Cubase versions prior 13.0.30 already. If anybody missed this little news-bit they might be in for a surprise. Speaking of challenges... Here's some 1st hand experience with the long history of Steinberg's "forward/backward" compatibility: (prepare for a rant) > Their own arrangement and song file formats (.arr, .all, among other supporting files) were abandoned with a dysfunctional migration path from the beginning -- if any. > 32bit VST stopped working -- but still does in other 64bit DAWs but requires unsupported volatile 3rd party solution for use in Steinberg. > VST2 will stop working soon (2025?) -- but still does in other VTS3-compliant DAWs. Not every niche or free 32bit plugin became available as 64bit - even "professional" ones. Not every niche or free VST2 has a VST3 successor/sibling to migrate to, many experi-mental VSTi in particular don't. If one can't migrate for whatever reason (of which there are plenty) one looses access to their own original works because of a Yamaha/Steinberg business decision. So no: I don't trust ANY compatibility statement from Steinberg at all -- or frankly *any* software company's for that matter. I've lost many, many files and (digital) creative works over the past decades for many reasons due to some IT company's decisions out of my control, from sudden bankruptcy, take overs, to "periodical online license checks" failing included. Some time shortly after SX/SE3 (when Steinberg also switched from LPT dongles to USB "eLicensers" iirc), I wasn't able to constantly upgrade for a while around that time (a change in career path and Cubase Pro isn't exactly cheap to keep as a hobby) That's when Steinberg dropped .arr and .all file support w/o me ever knowing. When I was eventually able to get back to music years later and afford a new Pro version I basically lost access to all my former files and works: new computer, new dongle, new installation, any old files inaccessible. Most of them had "just" MIDI wrapped in Steinberg's proprietary file formats to play and control several hardware synths. I asked for a file specification with no luck. All the hardware still exists and works beautifully, but the digital side of this is probably gone forever... Maybe outsourcing file format conversions into file plugins would be a good idea after all so they can be maintained in parallel or even open sourced. I see a formats tab under Studio > Plugin information but I don't see any plugins listed. I've been a Cubase user since version 1 so there are a LOT of (precious to me) originals that I can no longer access because Steinberg decided so. Many only exist as a stereo recording on magnetic tapes, a couple on 8-tracks, a few as WAV files -- some only as mono I presume due to some unbeknownst fuck-up during a format conversion. 🙄 The old dongle was no more, the old licenses/installers no longer work because of this. Any support to get them back running has "expired" w/o me knowing back then. Steinberg's "official workaround" to convert ARR/SNG to .cpr project files no longer works either. The licenses they put out and the SX/SE setup files to perform a conversion can't be installed anymore as the licenses are no longer accepted by any recent eLicenser software -- which had to be updated to run newer Steinberg software 🤬 Maybe I can get this shit show running in some virtual machine at some point ... I recently found and bought a new, empty USB dongle in the hopes I can make it work before 2025 also kills this part and renders re-installing old Cubase versions futile... I'm also a developer and I understand that companies want to get rid of their tech depth to make a profit and to satisfy their greedy steak and fries holder... Yet: I can still open ancient Word documents or Photoshop files both of which are documented with wide support outside Microsoft or Adobe. Their once proprietary PDF eventually became a standard. Not so much with Steinberg and their proprietary formats -- even the ones they abandoned. That's why I also have no big hopes for DAWproject to be sustainable let alone suitable as an "generic archive format" for days to come when Steinberg or Yamaha eventually stop doing business because the next generation is fine with AI generated conveyer belt music ... end of rant. 😁 thank you for your optimistic video 👍
As ever a very useful video. Whilst the Dorico score editor enhancements are welcome, as a basic user I was disappointed to see that the text editing is more rigid than before. For example I cant find a way of getting the Score Title to copy across to every page in the score. I can see a greyed out 'Title' and can not work out how to edit this. Am I asking too much or not using the tools correctly?
I’m getting a strange sound difference when samples from media bay to either the drum machine or project window. With the same settings as C13 which works fine?
I love the new cubes 14 but I’m having major issues with plug-ins not opening. As addictive Drummer 2.5 does not open up in cubas 14 but it does open in cubes 13. Also the remote app for the iPhone. Ic pro will not open and version 14 but still works in version 13. Any insight as to how to resolve these issues yet. Thank you.
Coming from Cubase 12, despite the great new features, the new version has been quite frustrating to me, because the GUI has gotten worse. Less contrast, less visual separation of elements, and most problematic, overall smaller and thinner fonts and text labels that are increasingly hard to read, especially when you’re older, have bad eyesight anyway and presbyopia. Additionally, they still haven’t managed to update the UI elements from SX days. The UI is just an inconsistent mess, they keep changing bits of it again and again instead of doing it once right (and employ a good UI/UX designer…). I’m seriously considering giving S1 another chance now, but I know that I’ll hate changing my workflow.
I feel the same. Everything seems so much more cluttered on the screen. 12 looks way better and less confusing to my eyes. I’m on the demo for 14 but may not upgrade because of this.
A small correction. "the version that opens is determined solely by your licence". This is not auctually true. They launching Cubase, while holding down the Option key. Something interesting will happen.
@@LanewoodStudios I don't think it's a delibereate lie. More of a misscomunications, which can easily happen with such a complex software as Cubase. I see this being useful in two cases. 1) People, like you, who deals with teaching. You no longer have to guess if a feature is present in a lower version (or have multiple versions installed). Just launch Cubase in a lower version, and check. 2) You can also avoid nasty surprises, if you're collaborating with someone who runs a lower version of Cubase. Such as the project relies on a feature that isn't avalable in the lower version. Just launch Cubase in a lower version, open the project, and check that everything is OK, before sending it off. Perhaps you should add this to your other video, about sharing projects.
Excellent video. You had a good idea creating a video about these less glamorous, “under the hood”, changes in Cubase.
Yes exactly, a slightly different take on the new Cubase!
Great Video As Usual. Thank you
@@hanisiblini thanks!
Thank you , you highlighted why my Synthogy Ivory 2 Piano VST ( an old favourite) has seemingly "gone" and how to get it back !
Excellent!
Great nurturing video, as usual from you! Hope they fix the multi core performance issues with new gen CPUs. Just build a new Win 11 PC with an i9 14900K, 64GB RAM, SSD M2... a beast. Already optimized all the OS all... but to my suprise I'm getting CPU spikes (overloads) on Cubase 13, even with a few plugins loaded. And also loading just a few plugins quite loads got the CPU. Quite frustrating. Tried everything within the Studio tab in Cubase 13, with different settings of the ASIO guard, but without no success. I see they recommend to set the cores affinity in the task manager while Cubase is running, but it seems an awkward solution, so didn't tried yet. Considering this, I'm a bit hesitant to get the new vers 14 if there's no improvement in that issue!
Thank you. Very disappointing that the multi-core performance is still a thing. They previously announced that they tackled it in Cubase 13 I believe which I even made a video about. I would definitely contact support about this.
Another very informative video!
I have noticed that loading larger projects in 14 is faster than 13. I also think that closing projects is faster as well. (Probably for the same reason) But, I haven't noticed any similar optimization in playing back tons of tracks with tons of plugins. It could be there but just maybe a small improvement. Have you noticed any CPU optimization on recording or playback?
And yes, I think that 14 is even more stable than 13. 13 was a banner release for Steinberg as probably the most stable release right out of the box I had ever used. But 14 does indeed seem to be more stable than 13.
All-in-all a really great release!
Thanks for confirming my experiences as well. Great that your projects also load faster. Didn’t notice any playback/recording performance improvements yet.
14 is superb! 13 was the worse release of all time! Great video as always Thank you
Thanks!
The new score editor was a game changer for me. I have loads of parts originally played on a keyboard that I'm having real brass/string players come in to play. Even without quantization, it does a great job of producing readable parts on the default settings. If necessary, I can import the parts straight in to Dorico for further refinement. It does lack some features that the old score editor had, but it's much, much more intuitive. Steinberg definitely got this right as far as I'm concerned.
Great to hear. I don’t really have a use-case for the score editor in Cubase myself but when you do I’m sure it’s a nice update.
I feel sad when it doesn't support showing my lyrics from version 13, and also from the standard midi file. There is no way around. If I want my lyrics in the score editor, I have to punch every single word again. 😢
Using the score editor heavily since the early 90s I'm slightly shocked by the new score editor's loss of functions and features. Especially the automation features of how the score is displayed with no chance to edit it how I want it to look pisses me of.
I guess they will now slowly add features. This is usually the way it goes for these big changes.
As a long time user of Dorico Pro, I don't think I'll be using the scoring features within Cubase. I think the update to include Dorico scoring is great, just can't see why I would use it. I'd be interested to know what other Dorico users think. Regarding the grace period comments, one detail they don't mention in the release notes: There is no free upgrade / grace period for those who purchased Cubase with the recent special anniversary pricing vouchers, as I found out. I guess getting Cubase Pro 13 for 70% off was all they were willing to offer. While saving yet another $99 would have have been nice, I have to agree with Steinberg's reasoning. Thanks for the video!
You're welcome. And yes I can imagine that you'll keep using Dorico if you have that already anyway. Didn't know about the grace period in combination with the earlier anniversary deal. Thanks for adding that!
The score integration is what I've wanted for years. But I'm now retired from composing and I'll only do it again when I can give verbal instructions and both score and mockup will be created automatically.
Good update for you then but you want more automation 😉.
What are your experiences with the new Cubase version? Were you aware of these under-the-hood changes already?
09:39 not so much I'm afraid and I wouldn't hold my breath for this to remain true. The 64bit files of C14 won't be "forward" compatible with Cubase versions prior 13.0.30 already. If anybody missed this little news-bit they might be in for a surprise.
Speaking of challenges... Here's some 1st hand experience with the long history of Steinberg's "forward/backward" compatibility: (prepare for a rant)
> Their own arrangement and song file formats (.arr, .all, among other supporting files) were abandoned with a dysfunctional migration path from the beginning -- if any.
> 32bit VST stopped working -- but still does in other 64bit DAWs but requires unsupported volatile 3rd party solution for use in Steinberg.
> VST2 will stop working soon (2025?) -- but still does in other VTS3-compliant DAWs.
Not every niche or free 32bit plugin became available as 64bit - even "professional" ones.
Not every niche or free VST2 has a VST3 successor/sibling to migrate to, many experi-mental VSTi in particular don't.
If one can't migrate for whatever reason (of which there are plenty) one looses access to their own original works because of a Yamaha/Steinberg business decision.
So no: I don't trust ANY compatibility statement from Steinberg at all -- or frankly *any* software company's for that matter.
I've lost many, many files and (digital) creative works over the past decades for many reasons due to some IT company's decisions out of my control, from sudden bankruptcy, take overs, to "periodical online license checks" failing included.
Some time shortly after SX/SE3 (when Steinberg also switched from LPT dongles to USB "eLicensers" iirc), I wasn't able to constantly upgrade for a while around that time (a change in career path and Cubase Pro isn't exactly cheap to keep as a hobby) That's when Steinberg dropped .arr and .all file support w/o me ever knowing. When I was eventually able to get back to music years later and afford a new Pro version I basically lost access to all my former files and works: new computer, new dongle, new installation, any old files inaccessible.
Most of them had "just" MIDI wrapped in Steinberg's proprietary file formats to play and control several hardware synths. I asked for a file specification with no luck. All the hardware still exists and works beautifully, but the digital side of this is probably gone forever...
Maybe outsourcing file format conversions into file plugins would be a good idea after all so they can be maintained in parallel or even open sourced. I see a formats tab under Studio > Plugin information but I don't see any plugins listed.
I've been a Cubase user since version 1 so there are a LOT of (precious to me) originals that I can no longer access because Steinberg decided so. Many only exist as a stereo recording on magnetic tapes, a couple on 8-tracks, a few as WAV files -- some only as mono I presume due to some unbeknownst fuck-up during a format conversion. 🙄
The old dongle was no more, the old licenses/installers no longer work because of this. Any support to get them back running has "expired" w/o me knowing back then.
Steinberg's "official workaround" to convert ARR/SNG to .cpr project files no longer works either. The licenses they put out and the SX/SE setup files to perform a conversion can't be installed anymore as the licenses are no longer accepted by any recent eLicenser software -- which had to be updated to run newer Steinberg software 🤬
Maybe I can get this shit show running in some virtual machine at some point ... I recently found and bought a new, empty USB dongle in the hopes I can make it work before 2025 also kills this part and renders re-installing old Cubase versions futile...
I'm also a developer and I understand that companies want to get rid of their tech depth to make a profit and to satisfy their greedy steak and fries holder... Yet: I can still open ancient Word documents or Photoshop files both of which are documented with wide support outside Microsoft or Adobe. Their once proprietary PDF eventually became a standard.
Not so much with Steinberg and their proprietary formats -- even the ones they abandoned.
That's why I also have no big hopes for DAWproject to be sustainable let alone suitable as an "generic archive format" for days to come when Steinberg or Yamaha eventually stop doing business because the next generation is fine with AI generated conveyer belt music ...
end of rant. 😁
thank you for your optimistic video 👍
As ever a very useful video. Whilst the Dorico score editor enhancements are welcome, as a basic user I was disappointed to see that the text editing is more rigid than before. For example I cant find a way of getting the Score Title to copy across to every page in the score. I can see a greyed out 'Title' and can not work out how to edit this. Am I asking too much or not using the tools correctly?
I have not delved into the new score editor at all yet as I never really used it before Cubase 14 either. But maybe someone else can help.
I’m getting a strange sound difference when samples from media bay to either the drum machine or project window. With the same settings as C13 which works fine?
I love the new cubes 14 but I’m having major issues with plug-ins not opening. As addictive Drummer 2.5 does not open up in cubas 14 but it does open in cubes 13. Also the remote app for the iPhone. Ic pro will not open and version 14 but still works in version 13. Any insight as to how to resolve these issues yet. Thank you.
Coming from Cubase 12, despite the great new features, the new version has been quite frustrating to me, because the GUI has gotten worse. Less contrast, less visual separation of elements, and most problematic, overall smaller and thinner fonts and text labels that are increasingly hard to read, especially when you’re older, have bad eyesight anyway and presbyopia.
Additionally, they still haven’t managed to update the UI elements from SX days. The UI is just an inconsistent mess, they keep changing bits of it again and again instead of doing it once right (and employ a good UI/UX designer…).
I’m seriously considering giving S1 another chance now, but I know that I’ll hate changing my workflow.
I do recognize what you are saying but I guess it’s just the modern dark mode designs. Is S1 really that different?
I feel the same. Everything seems so much more cluttered on the screen. 12 looks way better and less confusing to my eyes. I’m on the demo for 14 but may not upgrade because of this.
A small correction. "the version that opens is determined solely by your licence". This is not auctually true. They launching Cubase, while holding down the Option key. Something interesting will happen.
@svenisaksson3970 they lied in the release notes then? 😱😉
@@LanewoodStudios I don't think it's a delibereate lie. More of a misscomunications, which can easily happen with such a complex software as Cubase.
I see this being useful in two cases. 1) People, like you, who deals with teaching. You no longer have to guess if a feature is present in a lower version (or have multiple versions installed). Just launch Cubase in a lower version, and check.
2) You can also avoid nasty surprises, if you're collaborating with someone who runs a lower version of Cubase. Such as the project relies on a feature that isn't avalable in the lower version. Just launch Cubase in a lower version, open the project, and check that everything is OK, before sending it off.
Perhaps you should add this to your other video, about sharing projects.
@svenisaksson3970 thanks for that tip and video idea!