Cubase is far from perfect, we all know, and if a specific bug keeps you from working efficiently or even crashes your system - I DO get that. It will always be work in progress.
HOWEVER, I think it is important to also keep in mind all the great features that the devs accommplished by now. I’d be frustrated if all I ever hear is how bad things are. This is far from true because they are not.
I really appreciate Cubase 14 and it ticks almost all boxes for me.
Yeah, I’m just saying keep things balanced - it is not a question of all good vs all bad // half full vs half empty. There are many great achievements that are worth mentioning, too. I can second what @Googly_Smythe said: C14 is the most stable version so far and my version history experience goes way back, too.
Not all gold but Steinberg definetly deserves some credit for all their great achievments. Nothing more, nothing less.
I do recognize those people who keep running into showstopping bugs and I hope they get their issues resolved. I understand their frustration. Steinberg is not perfect, we all know that.
I do not envy the developers and accountants who have to figure out how to balance the limited resources to spread around new features and bugfixes to keep the business running and the lights on. The DAW market is ridiculously over-saturated and brutally competitive. All DAW developers are in a big crunch, so hard decisions have to be made.
But in recent years especially, I have noticed Steinberg has been finding a better balance between new features and bugfixing. They will never please everyone. It’s impossible. But they are finding a good balance.
Personally, I wish they would put another 10-20% more resources into bugfixing as well, but I have to agree that C14 is a big success for me. Congrats again to Steinberg! Keep up the good work and keep going in this direction! 14.0.20 is a certified hit IMO.
Special kudos to the Dorico/Score team for spending years and years laying the foundation for the new score editor. The future as the top DAW for composers looks bright!
And also special kudos to the whole team for ARM for Windows now officially supported. WOW! This says a lot about how tight the codebase has become, and implies a massive amount of refactoring and streamlining has taken place over recent years. Bravo for this, and again, the future looks bright!
Hi all,
weird situation here: I’m using Cubase on 2 machines: my studio desktop and my laptop. the desktop has been updated without any issue meanwhile the laptop got the update but, very strangely, the download manager doesn’t recognise all the components that I’ve previously installed (e.g. Padshop) despite they are there and I can recall them when opening a project made before the update.
Select multiple MIDI tracks, and while holding Shift + Alt in the Inspector, set the MIDI output destination. This changes the Ch of all selected tracks to 1.
This issue occurs 100% of the time in this project, but it cannot be reproduced when performing the same operation in a new project.
Thank you. It appears the problems were all this error:
2025-03-17 17:52:44.683 ERROR 11480 --- [Thread-8] n.s.e.d.d.aria2.internal.Aria2Process : stream: Exception: [AbstractCommand.cc:312] errorCode=1 Network problem has occurred. cause:A socket operation was attempted to an unreachable network.
2025-03-17 17:55:23.687 INFO 14016 --- [ForkJoinPool.commonPool-worker-2] n.s.e.d.d.a.DownloadArtifactServiceImpl : start() downloadArtifact: C:\Users\jeffr\Downloads\Steinberg\WINARM64\Cubase 14.0.20 - Application (required)\Cubase_14.0.20_Installer_winarm64ec.zip.sda-download State: NOT_STARTED
2025-03-17 17:55:23.700 INFO 14016 --- [ForkJoinPool.commonPool-worker-2] .e.d.d.r.PersistedDownloadRepositoryImpl : Add download Cubase 14.0.20 - Application (required) (3e473618-7e29-4684-9f6a-8d53086b2ea0)
2025-03-17 17:55:23.702 ERROR 14016 --- [Thread-8] n.s.e.d.d.aria2.internal.Aria2Process : stream: 03/17 17:55:23 [e[1;31mERRORe[0m] CUID#26 - Download aborted. URI=https://download.steinberg.net/automated_updates/sda_downloads/3dc569d6-260a-406b-9ac3-ccdcea35469b/Cubase_14.0.20_Installer_winarm64ec.zip
2025-03-17 17:55:23.703 ERROR 14016 --- [Thread-8] n.s.e.d.d.aria2.internal.Aria2Process : stream: Exception: [AbstractCommand.cc:312] errorCode=1 Network problem has occurred. cause:A socket operation was attempted to an unreachable network.
2025-03-17 17:55:24.789 INFO 14016 --- [Thread-8] n.s.e.d.d.aria2.internal.Aria2Process : stream: 03/17 17:55:24 [e[1;32mNOTICEe[0m] Download GID#aad949cfc5135ff6 not complete: C:/Users/jeffr/Downloads/Steinberg/WINARM64/Cubase 14.0.20 - Application (required)/Cubase_14.0.20_Installer_winarm64ec.zip.sda-download
2025-03-17 18:01:19.905 INFO 14016 --- [ExitApplicationEventHandler] n.s.e.d.c.ExitApplicationEventHandler : Exit application now.
2025-03-17 18:01:19.911 INFO 14016 --- [ForkJoinPool.commonPool-worker-11] n.s.e.d.c.command.CommandRunnerImpl : Execute command: [C:\Program Files\Steinberg\Install Assistant\Steinberg Install Assistant.exe, --stop-helper]
2025-03-17 18:01:21.244 INFO 14016 --- [ForkJoinPool.commonPool-worker-11] n.s.e.d.c.command.CommandRunnerImpl : Command output:
2025-03-17 18:01:21.245 INFO 14016 --- [ForkJoinPool.commonPool-worker-11] n.s.e.d.i.WindowsInstallHelperAccess : Successfully stopped the install helper via the SIA
2025-03-17 18:01:21.245 INFO 14016 --- [ForkJoinPool.commonPool-worker-11] n.s.e.d.i.WindowsInstallHelperAccess : Successfully stopped the install helper process
2025-03-17 18:01:21.250 INFO 14016 --- [ForkJoinPool.commonPool-worker-4] n.s.e.d.d.aria2.DownloadServiceAria2 : stop() downloadChoice: SelfUpdate 1.37.3 State: FINISHED
2025-03-17 18:01:21.253 INFO 14016 --- [ForkJoinPool.commonPool-worker-4] n.s.e.d.d.a.DownloadArtifactServiceImpl : stop() downloadArtifact: steinberg-update-helper-win-1.2.0.0.zip State: FINISHED
2025-03-17 18:01:21.254 INFO 14016 --- [ForkJoinPool.commonPool-worker-4] n.s.e.d.d.a.DownloadArtifactServiceImpl : stop() downloadArtifact: sda.zip State: FINISHED
2025-03-17 18:01:21.258 INFO 14016 --- [ForkJoinPool.commonPool-worker-4] n.s.e.d.d.aria2.DownloadServiceAria2 : stop() downloadChoice: Steinberg Activation Manager Installer State: FINISHED
2025-03-17 18:01:21.259 INFO 14016 --- [ForkJoinPool.commonPool-worker-4] n.s.e.d.d.a.DownloadArtifactServiceImpl : stop() downloadArtifact: Steinberg_Activation_Manager_Installer_win.zip State: FINISHED
I know my network was working. Perhaps it was the destination.
looks like your download is failing cause of a network issue. The log says “A socket operation was attempted to an unreachable network,” which basically means it couldn’t connect to the Steinberg servers.
Couple things to try—first, make sure your internet is working fine, maybe restart your router just in case. If you’re using a VPN or proxy, turn it off and see if that helps. Also, antivirus or firewall might be blocking the download, so try disabling them temporarily.
You could also run the Steinberg Download Assistant as admin, sometimes that fixes weird permission issues. If it’s still not working, maybe try downloading the installer manually from Steinberg’s site instead of through the assistant.
One more thing—maybe change the download folder to somewhere simpler, like C:\Cubase_Installer or something, sometimes weird paths mess things up. If nothing works, restart your PC and give it another go.
With this update - clicking the red clip indicator in the mixer selects the channel rather than just resetting the clip like it used to. A little annoying. But other than that great
Hi Yes, I had a similar issue, but I uninstalled then installed again and it seemed to complete … however … I now dont seem to be able to license it anymore. Activation Manager has its usual issues of saying I am not connected to the internet - and having tried the usual suspects eg turning off IPV6, running as admin, reinstalling Activation Manager, I cannot run Cubase 14pro anymore … happy days - great update lol … not
Hi, It does reset, but also selects the input channels rather than staying on the selected record channel. I either stop entirely and click to reset or wait for a large enough space to be able to click reset and then re-select the record channel.
