Cubase 13.0.30 maintenance update

Have to say though - all feeling rock solid and snappy!
Loving the new GUI tweaks!!

4 Likes

Great update overall.
As good a looks are though, more importantly. Something needs to be done about this disk cache spike issue users have reported for 5+ years now…You’d think a software that highly utilises audio would put more attention to the engine and cache performance.
I get a spike every time I press play. This specifically is worst when using an audio sample from cubases own packs.
When changing the volume on the event clip if the project is playing it becomes rendered unusable due to the cracks. I have have experienced nothing similar to this in Ableton, S1 or FL…What’s the deal?

From what I’ve seen as well this issue has got worse for people as each update arrives*

From 2013 >
https://forums.steinberg.net/t/disk-cache-usage-problem-persists/609361/6

Actually they do have something in common, sequential Track Numbers. In your pic Tracks numbered 9 through 16 are marked. It always indicates 8 consecutive Channels.

1 Like

May I ask if Meteor Lake CPUs are already supported?

1 Like

Anyone tested if Autotune X with ARA works in 13.0.30 or not?

1 Like

After several months of waiting, Cubase still crashes when closing Media Bay, or time stretching, and more actions. Very disappointed, sent the logs several times and nothing changed. I feel like I got robbed 100 EUR for nothing, just pain and frustration.

Autotune ARA still not working sadly :frowning:

2 Likes

There’s still some weirdness where solo/mute buttons stop responding in the arrange page. I ran into it when I was muting some folders. Restarting the application fixed it. 13.030 Sonoma.

Brief UI/UX Comments

  • Good work with the improved and consistent use of iconography. This is evident in the drop down menus I have highlighted. This should improve some usability I hope.
  • Also it was a good idea to use grouping/proximity/spacing with those drop downs. It shows relatedness and reduces the feeling of being overwhelmed with a lot of information at once. I hope this also improves the learning process
  • It was also a good idea to address some colors used in color coding. We can see now that the W (Write) button now uses an orange-ish color. It’s no longer a red color which is often associated with “arming” tracks. That seems like a sensible idea.

1 Like

I don’t know. It seems better than this:

Hello,
Can I (we) have another trial period? A couple hours is all I need. This update sounds like it addressed my reasons for not upgrading from 12 to 13.
Is that possible?
Thanks!

1 Like

3 posts were split to a new topic: Cubase 13.0.30 crashes when switching to regular Track font

Well this thread sure has gone sideways.

After starting off discussing the 13.0.30 update it got hijacked by multiple discussions of several different issues/problems with the replies all intermingled with each other…

3 Likes

Wonderful update! Just today I was complaining to a friend about the GUI changes from 12->13 and that I hated it, because my eyes hurt and it was hard to look at and navigate for a longer amount of time… this hits at a perfect time and love the direction this is going.
Thank you for listening to user feedback!

6 Likes


the stereo icon in Stereo Out Track ??

i have the same Font !!
Still The font, icons White why not black or grey .
image
its look better in the highlighted track

i think better if u make some Depth in the Icons like Studio one if u want to be flat make it right

For a comparison, when Studio One released updates (and when I frequented its forums) the threads also looked like this — diverse. The company announced the release with a pinned, locked thread. Then they’d create a separate announcement post where we could comment. And this is typically what occurred — lots of diverse chatter. Not sure what you expect us to talk about when the topic is both the latest CB release and our immediate response to it. One of them being immediate problems noticed by early adopters.

A good step forward in the right direction. I still prefer C12 (top) but C13 still looks “busy” to me. Thanks for all the work and listening to us long time users.

11 Likes

Welcome improvements to the UI. MixConsole and tracks with improved M S R W icons look much better now. The visual hierarchy of tracks is still not there though, no matter what font you use for tracks bold or regular. I’d still prefer track buttons with black foreground as it was in C12.

Also this alignment thing is somewhat off-putting

Alignment

3 Likes

I just pulled it up and the UI is noticeably easier on the eyes. This is a good sign. Thanks for that, Steinberg. Glad you are listening. I know I can be pretty hard on you all, but it’s been building up for literally years now.

Hope some performance issues have been addressed. Guess I’ll know soon enough.

(And please, please fix the MIDI CC automation lane never-goes-away scrollbar issue I mentioned in another thread I started. It’s gotta be something super simple, but I find it really quite irritating and I hope worthy of your attention. Still definitely not fixed.)

2 Likes

The GUI looks better now, but the fader caps are still BLURRED.

Look at the picture garymusic posted above

Please bring back the old fader caps!

3 Likes