Cubase 13.0.20 maintenance update

Cubase
,
43

Well, from the release notes I though perhaps the MIDI input transformer errors I made a video about were fixed, much to my surprise, I hadn’t noticed that the Action Target dialog under Event Transform actions is entirely missing options that were available in Cubase 12. There are no options for Value 1, Value 2, and Value 3 are totally missing. The only values there now are Channel, Type, Subtype, and Main Value.

Apparently, the only reason I was able to report the “off by one” issue earlier is because I was using presets from Cubase 12 that already had these values but the stored value from the operation was incorrect.

I will attempt to investigate this further tomorrow, but right now, I am frankly starting to get annoyed!

I’ve spent considerable effort trying to analyze the DPC issues that I posted about in another thread, and am getting no help! Now, in trying to see if my Input Transformer issue on relative encoders was fixed, I’m totally thrown by another issue.

I know that the developers must get tired of the complaining and I have TRIED to remain constructive. However, my patience is wearing thin!

If you don’t know what I’m talking about, a simple search of my recent posts will indicate what I’m talking about.

In the meantime, I will try to regain my composure and get some sleep before trying to discover yet again what has changed and whether the original transformer issue is fixed or if it’s actually more broken than I originally realized.

I hope that after I regain some sleep and some patience, I will discover that this is a simple misunderstanding on my part from name changes in the dialog and that the problem I was attempting to verify was indeed fixed. I don’t know how it could have even been tested unless I am obviously missing the name chjanges, but don’t have the capacity to investigate further.

With luck, a better mood will prevail tomorrow and I will report my findings.

44

I apologize for bordering on a rant in my previous post, but I am leaving it in place to illustrate my frustration. I was not able to put this to rest this evening and revisited the MIDI relative controls issue.

In spite of my confusion over the name changes in the Input Transformer page, I took a deep breath and experimented.

While I’m sure that there were “good reasons” to detour from the original MIDI field names, I was able to figure out how to get the expressions set up and it appears that the transformer value math issues have been resolved.

As for the DPC issue, I hope that someone will take notice of my post today concerning my research on the DPC issue. I do not want to repeat it here. I can provide data illustrating exactly what is happening but could use some expert help from someone as to what to do next. Believe it or not, I’m actually trying to help, AND I HAVE DATA!

1 Like
45

Have the graphics been fixed in this update? (Looking like no fix for many here). Can’t access my studio till next week to try it. Had to go back to C12 - the graphics make 13 utterly unusable for me so far (i7 + Intel GPU). If not fixed…are you serious Steinberg? You can twiddle a few minor things but don’t prioritize the big thing that makes C13 not fit for purpose for many users. We paid good money for C13 and it doesn’t work (well, it might work as far as I know, but I can’t see it, so how would I know?). I’m hoping my worst suspicions aren’t true, that we’ll get a working paid fix at 13.5 - I’ll want C13 refunded if that’s the case…

46

paid x.5 updates aren’t a thing anymore.

47

Hmmmm…so it might be broken for the whole of C13? Roll on C14, though I won’t jump on it early.

48

I’m not a beta tester. I’ve paid for a 13 version, I would like to use my product. The 13.0.20 doesn’t fix the graphics issues. I have to use Cubase 12 (which works on the same PC). It’s not acceptable from Steinberg (Yamaha) to buy a NON finished version !!!

1 Like
49

My performance issues have been solved with this update, it now runs as smooth as C12. A dev contacted me, they changed back a setting regarding the CPU core-affinity. No more dropouts and maxed out performance meters.

50

I love Cubase, but there’s a definite problem. Is it money, or just that the application is such a behemoth and in need of a complete overhaul to make updates less problematic? Technically we should have received 13.0.0 as the first release. The webstore issues meant that 13.0.10 was the first release so imagine what could have happened if they didn’t have that extra time to fix stuff before release.

I’m not a professional user, just a hobbyist, but I had three full crashes last week and a project corruption. I switch between Cubase, Studio One and Ableton depending on project, and Cubase is the only one with which I experience crashes. I simply cannot think of a time any of the others just threw their arms in the air and gave up, so it’s just not fair to blame users’ individual installations for the application’s inherent lack of stability, which I see a lot here.

That said, for me at least, the improvements with C13 make it the best update for me so far - lots of small things addressed and quality of life improvements.

51

Really ? Glad i haven’t even bothered then

1 Like
52

Update looks good so far.

Maybe you add this little preference feature request with the next one. Should be a minor thing to do. Thank you:

53

The upgrade performed terribly on my computer, but I couldn’t find a way to download the previous version to downgrade to 13.0.0 - Does anyone know where I can find it?

54

They should made it available here (it’s not yet).

55

Yes, I am very looking forward to it coming up - you an idea when? And what if there’s another way to get it?

56

Unfortunately not. I also intend to roll back to 13.0.10 because of the preset selector bug.

57

Hi guys,
I’m not sure why but Cubase is now saying my MIDI controller (SubZero MiniPad) is disconnected when it isn’t. Device manager (Windows 11) is saying it’s connected & working correctly. I’ve restarted my laptop & Cubase but I’m still getting the same thing. Strangely, the MiniPad is actually showing up in the MIDI Port Setup screen though, so Cubase knows it’s there. I just can’t do anything in MIDI Remote Manager, it’s like the device is unplugged. But obviously it’s not. It also shows up in the MIDI input device options on my VST instrument tracks. Bizarre.

Any ideas???

58

Why not an Artist trial ?? That’s confusing

59

I’m pretty sure the one Cubase Pro trial key will let you try all the little brother versions too.

I.E. Get the Pro trial key. It will unlock Pro, but it will also unlock Artist, SE, and so forth. You could also run the older Cubase version 12 stuff with a version 13 trial key. You can download and try/compare them all. So in theory, it’d be no problem to take that key, and only download Artist (or try it first), and if it’s not as fully featured as you like, grab and try Pro too.

If you buy a Pro key, then you’ll always be able to run the smaller versions with it. You can also roll back as far as version 12. If you have the old Steinberg dongle and ‘upgrade’ whatever version(s) of Cubase has keys on the dongle, then you can roll back to even older versions should the need arise.

HALion works the same way. The demo key unlocks full HALion 7, and when you download full H7 you also get a Sonic 7 setup, but you can also use the same trial key if you only wanted to download and check out Sonic 7 Collections.

Dorico has the free SE key, but I think there is also Dorico Pro trial key that will unlock all of the editions for trial. In Dorico’s case, I think the app itself is the same from SE all the way to Pro. Pro comes with more instruments/content, but otherwise, you’d hold down a certain key combo to try the little brother versions. Dorico simply goes by what key you have as to what all features are ‘unlocked’ in the main app. I.E. I have Pro here, but I can tap a certain key combo when launching to make it think it is a smaller version. My Pro installation does include more instruments too, and they’d be unlocked and still work in the smaller versions, so…for less confusion one might want to install the content sets for the smaller versions first, and work your way up.

60

Get the Pro trial and install it.

When you launch hold the alt/opt key and you will see an option to specify whether Pro or Artist is launched.

The programs are identical. It’s the license that dictates what actually launches.

1 Like
61

Ah…but since Artist probably comes with less ‘extra content/instruments/plugins’ one might prefer to start by downloading in the Download Assistant from the Artist section instead? Work your way up if you wish to try more…

62

13.2 is not stable at all for me like 13.1
Graphics issues still there… even worse than before :unamused:

AMD 5950X
3070Ti
64 GB RAM
Please do something to fix it in ASAP… Thank you.

5 Likes