Cubase 13 released! Now available for purchase
- Thread starter mducharme
- Start date
vibrationisreality
Active Member
Do you have a link?
I think it's always a balance...just to survive. Unfortunately, users tend to think the way they use Cubase is the way most do which may or may not be true.
And, naturally, in this business there is a lot that the company can't say for obvious reasons, however that aspect is sometimes forgotten by the user, who continually wishes for improved developer and end user communication.
ALittleNightMusic
Professional Amateur
Cool video from Christian, interviewing Andy Gray - who used to be a diehard Logic user and moved over to Cubase and loves it. Has some cool comments on Halion as a sampler - I need to try it out.
Guy Rowland
Senior Member
I've got my new Win 11 PC up and running (a 65w Ryzen 9 7900, DDR5 RAM, Gen 4 NVMe system drive). It's overwhelmingly good news - projects that brought my i7 7820x to its knees at 512 don't begin to break a sweat at 256, load times are halved and it even uses about 25w less power. Also I finally see what people say about the project close times improving drastically - didn't for me on the i7 but does on this.
One mad new irritant (there's always something). About 1 Cubase project opening in 3 I get no audio. If I move to a different RME soft output in Audio Connections (Babyface soundcard) and back again, audio is restored. Inexplicable. This has happened since I first installed Cubase 13.0.20. Anyone with any theories or ideas to try I'm all ears - thanks.
One mad new irritant (there's always something). About 1 Cubase project opening in 3 I get no audio. If I move to a different RME soft output in Audio Connections (Babyface soundcard) and back again, audio is restored. Inexplicable. This has happened since I first installed Cubase 13.0.20. Anyone with any theories or ideas to try I'm all ears - thanks.
stigc56
Senior Member
Hi
Please allow me to ask for your help tegarding the issue I raised in my post in Soundboard: https://thesoundboard.net/viewtopic.php?p=80945#p80945
Guy Rowland
Senior Member
Sorry! Did mean to come back to that, will reply to you there.
EDIT have updated the original post with new images and a few changes that have happened over the years - https://thesoundboard.net/viewtopic.php?p=2701#p2701
Last edited:
Your new system sounds like something that I'd like to build. I've been using my laptop as a stopgap measure until I felt comfortable switching to AMD (I've always used Intel CPUs).
Would you mind posting a parts list?
Dan L
New Member
I was planning to buy Cubase Elements to use Cubase to start my orchestral compositions, then moving on to do the orchestration and mixing in my main DAW (Logic). I love the idea of the Chord Track/Editor and Arranger Track. But as it seems right now it is quite buggy.
Some examples:
If you create a major chord and add the tension b9, the editor produces a wrong result by adding 6/13 instead. This also happens with #9, b5/#11, #5b13 …
It gives you the wrong tension for other combinations aswell, turns out that more complex tensions often results in an 6/13 …
And when it comes to minor chords, b9 and b11 results in adding an 9.
And to go on: Choosing a minor chord with the tension #5/b13 instead resets the Chord Editor, and deselects the chord and tension I have selected.
And further on ... you can’t for example select the tension 11 for major chords (it's “greyed out”). Maybe that’s a conscious choice of Steinberg, but I think it’s better to have more freedom as a music creator.
It seems that the Chord Editor is quite buggy in Cubase LE 13, at least on Mac. Is that the case for other Cubase versions?
I was thinking of buying Cubase Pro further down the road, to make Cubase my main DAW. But I just have to wait and see, until these issues are resolved.
I’m running Cubase LE 13.0.20 Build 148 (Intel) on an MacBook Pro 2019, Intel Core i9, Mac OS Ventura 13.2.1.
Some examples:
If you create a major chord and add the tension b9, the editor produces a wrong result by adding 6/13 instead. This also happens with #9, b5/#11, #5b13 …
It gives you the wrong tension for other combinations aswell, turns out that more complex tensions often results in an 6/13 …
And when it comes to minor chords, b9 and b11 results in adding an 9.
And to go on: Choosing a minor chord with the tension #5/b13 instead resets the Chord Editor, and deselects the chord and tension I have selected.
And further on ... you can’t for example select the tension 11 for major chords (it's “greyed out”). Maybe that’s a conscious choice of Steinberg, but I think it’s better to have more freedom as a music creator.
It seems that the Chord Editor is quite buggy in Cubase LE 13, at least on Mac. Is that the case for other Cubase versions?
I was thinking of buying Cubase Pro further down the road, to make Cubase my main DAW. But I just have to wait and see, until these issues are resolved.
I’m running Cubase LE 13.0.20 Build 148 (Intel) on an MacBook Pro 2019, Intel Core i9, Mac OS Ventura 13.2.1.
jneebz
Senior Member
July-August I believe....
stigc56
Senior Member
Thanks a lot.
devonmyles
Senior Member
Although I'm using Nuendo 13 on W11, I think the Chord Track has all the same functions as Cubase 13 Pro. If I'm understanding your post correctly, it's all working for me and not 'buggy'.
Have you been into preferences and ticked the tensions, and maybe created custom chords?
It's possible 'Elements' doesn't have all the chord editing options that 'Pro' has?
Attachments
Last edited:
Guy Rowland
Senior Member
There's a whole thread on it here - https://vi-control.net/community/threads/updating-to-ryzen-9-advice-gratefully-received.144330/ . Skip to the end for where I ended up.
easyrider
Embracing the Absurd
Might upgrade then after the bug fixes…
Dan L
New Member
Thank you for your reply! You have added the tensions 7 and b9. Then you get the right result for b9. But if you want major chords with just tension b9 (aswell as #9, b5/#11 or #5b13) without the 7:th you don't get the right result.
I have posted on the Steinberg forum about this issue too, and others are reporting that the problem was present already in Cubase 12. But as it turns out, setting the Voicings mode to Basic (instead of Piano) seems to solve the issues. The downside is that you lose the bass note for the chords in the chord editor when you switch to Basic.
devonmyles
Senior Member
Yes, sorry, I was going to mention that after I posted, but forgot. Although, it seems you are now aware of a way around the issue(s), although as you say, there is one downside.
I had this problem long ago with 11 Artist. 13 Pro is doing it still. To fix it, check the "release audio driver while in background" checkmark and just switch between another window and Cubase until the audio engine gets properly initialised.
It gets disconnected after I/O connections edit (F4), or buffer size change.
But this workaround works like a charm everytime this happens even if I need to switch the windows a few times.
