Tired of Steinbergs Upgrade to fix attitude

[LeVzi]

So Padshop pro and Retrologue both don't work correctly in Cubase 10.5 , I contacted support.

The response was

"We are aware that x,y and z happened in Cubase 10.5 and broke the plugins, but we fixed it in Cubase 11"

Seriously, wtf, we broke something so we are going to charge you to fix it.

[chk071]

So Padshop pro and Retrologue both don't work correctly in Cubase 10.5

Did that happen with a Cubase update, or when updating Padshop and Retrologue? (I saw that there was an update for them recently)

If it was a Padshop and Retrologue update, then uninstalling and reinstalling them with the last working update might work.

That suppport statement is bold indeed though. But, it shows what's important for them: Selling software. I wrote that in another thread here: I'm kind of tired of those paid upgrade per year policies so many DAW manufacturers do these days.

[Obsolete462444]

What's wrong with Retrologue and Padshop in Cubase 10.5? Last time I checked they worked without issues.

[chk071]

My guess: He updated them with the latest versions.

I can only see a re-install fixing it.

[LeVzi]

So Padshop pro and Retrologue both don't work correctly in Cubase 10.5

Did that happen with a Cubase update, or when updating Padshop and Retrologue? (I saw that there was an update for them recently)

If it was a Padshop and Retrologue update, then uninstalling and reinstalling them with the last working update might work.

That suppport statement is bold indeed though. But, it shows what's important for them: Selling software. I wrote that in another thread here: I'm kind of tired of those paid upgrade per year policies so many DAW manufacturers do these days.

It was the 10.5 upgrade that broke the plugins, they were aware of it, and fixed it in V11. reinstalling the plugins doesnt fix it, as they gave me a bunch of technical reasons (I cant find the email, buried in a million others) but they did point out that V11 fixes this. I should have tested it when I demo'd V11 tbh, thats my bad.

Padshop is the latest version, Padshop Pro I should add, but Retrologue is V1, not V2, but they both have the exact same issue of this moving GUI. I will go V11 at some point, but surely if they broke something in 10.5 causing the issues, which they are aware of, surely they should fix that in 10.5 as well as 11. Shows their mentality tbh, which is something I really dislike.

[chk071]

I agree. And, that's also the issue I am facing, when my (older) DAW breaks one day.

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

[EnGee]

The best thing then is to return to v10 (before the 10.5 update). In this case you don't need to upgrade. Not a perfect solution, but if you need to stay with Cubase, then I don't find another solution if you don't want to update to v11.

[Crossinger]

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

This is what market economy is all about.

Or do you mean the music software industry has passed its peak and now it's all about milking customers?

[chk071]

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

This is what market economy is all about.

True. Doesn't mean I have to like it. I don't blame them though. If there's a market for that. You see subscriptions literally everywhere now.

Regarding the software industry having had its peak: Not sure. But, it seems indeed that they desperately invent and sell features now. What I really notice is that it's all so lightning fast these days. It feels like you just bought the new version, and they're already releasing another one.

What is really ridiculous in this case though is that Retrologue and Padshop are DAW included plugins, which work in any other DAW just fine, but not in the former paid version of Cubase. Which is double ridiculous when you consider that it should still be supported, i.e. there should be a fix.

Would be interesting to know if they don't work for other users as well though.

[DollyNipples]

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

This is what market economy is all about.

True. Doesn't mean I have to like it. I don't blame them though. If there's a market for that. You see subscriptions literally everywhere now.

Regarding the software industry having had its peak: Not sure. But, it seems indeed that they desperately invent and sell features now. What I really notice is that it's all so lightning fast these days. It feels like you just bought the new version, and they're already releasing another one.

What is really ridiculous in this case though is that Retrologue and Padshop are DAW included plugins, which work in any other DAW just fine, but not in the former paid version of Cubase. Which is double ridiculous when you consider that it should still be supported, i.e. there should be a fix.

Would be interesting to know if they don't work for other users as well though.

Another reason for me to not buy Cubase. *cue hardcore fans rushing in with blowtorches and pitchforks*

You completely trolled the last cubase thread, you are not going to start this one off like this...you dont use cubase, you dont plan on using cubase, you have no dog in this fight so stay out of this thread...any posts you make will just be deleted

[AdvancedFollower]

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

This is what market economy is all about.

Or do you mean the music software industry has passed its peak and now it's all about milking customers?

Another feature of the market economy is that you can change to a competing product if the one you're currently using doesn't fulfil your expectations. There are lot of different DAWs available, with varying paid or free upgrade schemes.

[thebutler]

The best thing then is to return to v10 (before the 10.5 update). In this case you don't need to upgrade. Not a perfect solution, but if you need to stay with Cubase, then I don't find another solution if you don't want to update to v11.

+1
Seems a fair response to the OP's topic

[Daimonicon]

Basically, they keep you buying and buying and buying. It's like a subscription, more or less.

This is what market economy is all about.

Or do you mean the music software industry has passed its peak and now it's all about milking customers?

Another feature of the market economy is that you can change to a competing product if the one you're currently using doesn't fulfil your expectations. There are lot of different DAWs available, with varying paid or free upgrade schemes.

Yes sure. But then one has to go thru the hassle of learning a new DAW. It takes a couple of years being fully comfortable with a new DAW. And for what? Because of Padshop?

[chk071]

True thing. Preference of workflow is the primary concern when choosing DAW's for me.

If it is like the OP says (still waiting for confirmation from other Cubase 10.5 users), then that's a really bad sign Steinberg sends out. Cubase 10.5 is still being supported by them. It can't be that the DAW included plugins stop working, and Steinberg doesn't do anything about it.

Don't get me wrong, I like Cubase, and I like Steinberg. Just saying that, again, if it's true what the OP says, then that's not how it should be. And, again, still waiting for confirmation here. As far as I'm concerned, it could be an issue which just happens for the OP, or a handful of other people. Or for everyone. Or for noone. Or cats get killed by the new update. Or something.

[thebutler]

Sounds like that response from Steinberg support was trying to explain at length (shame that email is now 'lost'), exactly why technically it was not possible to provide a 'retro-fix' for v10.5. I'd be surprised if there wasn't an apology included. And probably the suggestion your only safe route would be to use v10 for PadShop or Retrologue based projects for now.

Which is not ideal by any means - no-one knows exactly what all they're going to need from the outset...

But I get it - you're miffed they knew about the issues before release (of v10.5), yet didn't say anything upfront. Instead, they rather played a waiting game for folk to 'discover' the problem(s) for themselves. Which I too dislike immensely by the way - non disclosure of 'known issues'.!

Anyway, hopefully you can (afford to) move to v11 soon - bezier curves in key editor, SpectraLayers One, new export job queue, global tracks in key editor, SuperVision, new Sampler Track features - meant the £85 upgrade, was money well spent for me...