Cubase 9.5.41 update available

[Macster]

What does the person need to do for you to fix that? Burn himself in front of your office?

Call me sensitive, but that remark upset me. Perhaps you need to realise that your sense of humour isn't everyone's, especially if they have suffered personal tragedy. You could have expressed your frustration differently.

I didn't mean to hurt you. I'm sorry.
But this is the internet, man, and this is the forum where many upset and angry guys come to complain. You should be prepared to see all sorts of comments here and not to take everything so personal.

Just FYI, I thought it was funny and in a way, very appropriate given that this has been an issue for so long...

[balinas]

does one need to download 9.5.40 and install before downloading and installing 9.5.41?

No

[DarrenGlen]

Hi Matthias,
I have a couple suggestions that might help. I work on code that gets rolled out to millions of users on a regular basis, it never goes off without a hitch, we have to support Win XP through Win 10.
1. Institute an alpha/beta program, even for maintenance releases. This will help you find the stuff that QA can't. You have a lot of loyal customers who would love to have a chance to help you make Cubase better. We all like to play with shiny new things before everyone else does, so there's that.
2. Allow for parallel installs/updates. If an update breaks a customers system, they're not stuck trying to figure out how to undo it and they won't have downtime trying to do so. The stuff you would need to copy from the base is not that big, so it should be doable. Parallel updates also allow you to validate the updater, can you roll it back?
I have a FrankenDAW and almost every commonly used plugin, I would have no problem with testing releases as long as my main production environment remains untouched and stable.
These are pretty cheap solutions and they should allow you to crowdsource some of your QA, we all want you to succeed.
Thanks

in a perfect world, this would be exactly what happens. But you must remember that Steinberg comes from Germany. Many have suggested exactly this and have been ignored. Maybe this time will be different? i have my fingers crossed. i want them to succeed also

[HarrySound]

I would like to thank all the contributors in this forum for their feedback and help to identify and resolve the issues. Also, thank you for your patience while waiting for this update. The 9.5.40 wasn't our best release yet and we will review our maintenance release process carefully to do better in the future.

Best regards,
Matthias

Hi Matthias,
I have a couple suggestions that might help. I work on code that gets rolled out to millions of users on a regular basis, it never goes off without a hitch, we have to support Win XP through Win 10.
1. Institute an alpha/beta program, even for maintenance releases. This will help you find the stuff that QA can't. You have a lot of loyal customers who would love to have a chance to help you make Cubase better. We all like to play with shiny new things before everyone else does, so there's that.
2. Allow for parallel installs/updates. If an update breaks a customers system, they're not stuck trying to figure out how to undo it and they won't have downtime trying to do so. The stuff you would need to copy from the base is not that big, so it should be doable. Parallel updates also allow you to validate the updater, can you roll it back?
I have a FrankenDAW and almost every commonly used plugin, I would have no problem with testing releases as long as my main production environment remains untouched and stable.
These are pretty cheap solutions and they should allow you to crowdsource some of your QA, we all want you to succeed.
Thanks

This is an excellent post.
Id' give any new version a go as long as I have my stable installation. I'm still slumming it on 9.5.2 because .3 broke everything (literally)

[steinpac]

[/quote]
Id' give any new version a go as long as I have my stable installation. I'm still slumming it on 9.5.2 because .3 broke everything (literally)
[/quote]

Same here!

[BaseCu]

I would like to thank all the contributors in this forum for their feedback and help to identify and resolve the issues. Also, thank you for your patience while waiting for this update. The 9.5.40 wasn't our best release yet and we will review our maintenance release process carefully to do better in the future.

Best regards,
Matthias

Hi Matthias,
I have a couple suggestions that might help. I work on code that gets rolled out to millions of users on a regular basis, it never goes off without a hitch, we have to support Win XP through Win 10.
1. Institute an alpha/beta program, even for maintenance releases. This will help you find the stuff that QA can't. You have a lot of loyal customers who would love to have a chance to help you make Cubase better. We all like to play with shiny new things before everyone else does, so there's that.
2. Allow for parallel installs/updates. If an update breaks a customers system, they're not stuck trying to figure out how to undo it and they won't have downtime trying to do so. The stuff you would need to copy from the base is not that big, so it should be doable. Parallel updates also allow you to validate the updater, can you roll it back?
I have a FrankenDAW and almost every commonly used plugin, I would have no problem with testing releases as long as my main production environment remains untouched and stable.
These are pretty cheap solutions and they should allow you to crowdsource some of your QA, we all want you to succeed.
Thanks

Many of us have made suggestions like these, but Steinberg remains a "move fast and break things" kind of a company. Users must pick up the broken pieces. It's been this way for years and is not likely to change anytime soon.

[ulesto]

Pleased to have a working update after .30 and .40. Issue with multiple DOP processes on affecting part of the file seems to be resolved with .41, and testing different bypasses working smoothly, despite not being listed in the fixes.

The only outstanding issue is the finicky nature of sending to RX6. Sometimes it stays stuck on 'Capturing audio...' and the Repair buttons don't activate.

Unbypass still actually means 'throw away all my RX work and send it back to RX to start over again. Before DOP the RX Connect exchange worked flawlessly. Undo/redo in Cubase was a better option than an unworkable bypass. Wish the old process menu was still an option.

Other than that it's great. So thanks for the .41 hotfix.

[jimknopf]

Thanks a lot for the update coming soon and working well!

[vinark]

It is possible to have parallel installs with a workaround. Just copy the the cubase folder in program files before the update. Call it cubase 9.30 or whatever version it is. It will work from that folder. You can even place the folders on other drives if you want to. If you don't like the 9.41 just delete it and rename your backup folder back to what it was. It is an at your own risk method and there might come a point it fails, but it worked here with an older version.

[cmbsa]

so I can't open a project in 9.5.21 if I saved it with 9.5.41? (see pic)

I had some asio-freezes, so I removed the 9.5.41 update from windows programs&features. I don't remember having this problem with previous verisons, I thought the cpr files are backwards compatible.

Untitled.jpg

(17.09 KiB) Not downloaded yet

[EmilStudio]

I work in 5.1 and here are few issues:
- Channel Settings/inser Routing tab: no scroll and the Routing for inserts 8 and up are unreachable
- Mixconvert (5.1 to 2) when used in send or channel out the interface appears as very older version of the plugin (looks like a old Nuendo I think)


- channel VST MultiPanner is different (I think it is also from Nuendo)


On my older version 9.5.3 everything is fine.
I tried replacing in 9.5.41 the surroundpanner.vst3 and Mixconvert.dll from 9.5.3 but nothing changed.
Can someone tel me which files/dll I have to replace so I can get back the regular VST MultiPanner and Mixconvert?

[BAB Studio]

We have just uploaded the Cubase 9.5.41 maintenance update...

Thanks!

[40W]

Please fix the Midi Chorder gui display bug. Was hoping these recent updates would address it but they didn't.

[mashipx]

i keep getting this error on install..... please see attachment.

my programdata folder in registered on D: drive if it helps

Capture.PNG

(143.67 KiB) Not downloaded yet

help please..

win10 pro, intel i7 8700k, 32gig ram, rme hdspe aio audio card. samsung pcie m2 256gig evo system drive.
most cubase data where possible is installed on a seperate D: drive.
thanks

[DeZorganiZator]

to mashipx
Create empty text file and change his name and expansion to OpenInCubase95_64.aepp and put this on C:\ProgramData\Steinberg\Audio Export Post Process Scripts

Original code this file:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<AudioExportPostProcess>
	<Description></Description>
	<Icon></Icon>
	<Executable>
		<Name>Cubase</Name>
		<Version>9.5</Version>
		<Path>C:\Program Files\Steinberg\Cubase 9.5\Cubase9.5.exe</Path>
		<Argument>"$PATH"</Argument>
	</Executable>
	<RunOnce>false</RunOnce>
	<WaitDone>false</WaitDone>
</AudioExportPostProcess>

[slinky005]

Export progress bar (not moving) fixed?

[ceemusic]

I see Cubase 10 will be 'Available Soon'. Will this be the last update for 9?
https://www.steinberg.net/en/shop/buy_p ... ro-10.html

[Starsprinkler]

I see Cubase 10 will be 'Available Soon'. Will this be the last update for 9?

No, they use to release the last update well after the next major version has been released.
9.0.40 was released February-18, 8.5.30 was released March-17 (it's in the version history pdf's) (3 months after next major version).
You should expect a 9.5.50 in Q1 2019 (following earlier release pattern).

[ceemusic]

I see Cubase 10 will be 'Available Soon'. Will this be the last update for 9?

No, they use to release the last update well after the next major version has been released.
9.0.40 was released February-18, 8.5.30 was released March-17 (it's in the version history pdf's) (3 months after next major version).
You should expect a 9.5.50 in Q1 2019 (following earlier release pattern).

Thanks

[medwaystudios]

Mediabay sync is still broken for me. I thought it was fixed but upon installing v10 I noticed it was off there. I then tried loading up 9.5.41 and it's off there too.

As before if I drag the 'off' loop into the project from then on the Mediabay syncs properly for that loop and any others.

Is anyone here getting consistent tight sync in the Mediabay when playing loops to the tempo of the project?

[J4R1O]

Please fix the download link for Cubase Pro 9.5.41 Update (Win 64). Mac link works, but Windows won't even start to download.

[Starsprinkler]

Please fix the download link for Cubase Pro 9.5.41 Update (Win 64). Mac link works, but Windows won't even start to download.

Working fine here, downloaded 9.5.41 update completely with no problem (Windows).

[J4R1O]

Please fix the download link for Cubase Pro 9.5.41 Update (Win 64). Mac link works, but Windows won't even start to download.

Working fine here, downloaded 9.5.41 update completely with no problem (Windows).

I deactivated F-Secure Internet Security and managed to download the update. Just wondering why it didn't block the Mac update, only that Windows one? :/

[nordlead26]

Sampler is BROKEN, doesn't work at all when you drag and drop audio from anywhere!

[nordlead26]

I see Cubase 10 will be 'Available Soon'. Will this be the last update for 9?
https://www.steinberg.net/en/shop/buy_p ... ro-10.html

If so, this is a rudeness for the users who still on 9.5 and want to keep on it for a while ... ¿why the silence Steinberg?