Menu
What's new
By:
Filters

Cubase 10

Started to experience my first crashes, seems to be linked to editing expression maps. When I try to edit an articulation Cubase quits.
 
I've been using 10 all day for some quite heavy Sound Design work. A few things...

When I first started using it, I had 5 crashes within about an hour. Can't exactly reproduce the crashes but I sent the crash reports in to someone at Steiny. Once I sorted it out, it's now been solid as a rock since.

What I did and what I think was something causing the problem. Preferences...

Obviously when you install a new version of Cubase it will copy over prefs from a previous version. In my case 9.5.41. If you don't want previous prefs to copy across automatically (I think it's just a convenience thing and a complete waste of time in my experience on OSX), then just hide your Cubase 9.5 folder either by removing it or renaming it to anything but the original name of folder. Cubase 10's new prefs will be recreated as designed and everything will be "clean". Restart Cubase again instead of using it straight away. Now, I tried this both ways as just described (prefs automatically copying and then deleting them and having them build from scratch). Here's where I noticed something a bit odd...

Before I renamed the Cubase 9.5.41 folder, I deleted (trashed) the Cubase 10 prefs folder and started Cubase. The new Cubase 10 Prefs were in fact still being copied from 9.5's pref folder. This, I think is odd (I understand it on a new install but not something I personally want to happen after), so make sure you hide the 9.5 folder. When you do, completely new prefs will be created for 10.

Then the hard swallow of this stuff... I copied my PLE commands, LE commands and port set up xml files from 9.5 and replaced the Cubase 10 versions (far too much work has gone into losing that stuff and starting from scratch). And that was it. I decided to just completely do the prefs from scratch in 10 and it's a bit of a pain in the ass (unless you know all your settings you prefer - which I do fortunately) but in doing so, 10 is running faultlessly. It's like buying a new house. Who wants to walk in from the street and tread dogs brown into the lovely new carpets. Best keep those dirty ole shoes out in the porch.

Obviously there are people that know all of this but some may not and honestly, save yourself the hassle and just build the prefs from scratch. The "convenience" of the previous prefs automatically transferring isn't convenient (for me). It's massive waste of time doing what I should have done from the start.

Cubase 10's laggy GUI problems seem to have gone now, the cursor doesn't look like it has Parkinson Disease anymore, Render in Place seems to render a little faster and yeah, the performance on my machine is fantastic. Anyway, probably time for a beer to celebrate! :)
 
jononotbono said:
I've been using 10 all day for some quite heavy Sound Design work. A few things...

When I first started using it, I had 5 crashes within about an hour. Can't exactly reproduce the crashes but I sent the crash reports in to someone at Steiny. Once I sorted it out, it's now been solid as a rock since.

What I did and what I think was something causing the problem. Preferences...

Obviously when you install a new version of Cubase it will copy over prefs from a previous version. In my case 9.5.41. If you don't want previous prefs to copy across automatically (I think it's just a convenience thing and a complete waste of time in my experience on OSX), then just hide your Cubase 9.5 folder either by removing it or renaming it to anything but the original name of folder. Cubase 10's new prefs will be recreated as designed and everything will be "clean". Restart Cubase again instead of using it straight away. Now, I tried this both ways as just described (prefs automatically copying and then deleting them and having them build from scratch). Here's where I noticed something a bit odd...

Before I renamed the Cubase 9.5.41 folder, I deleted (trashed) the Cubase 10 prefs folder and started Cubase. The new Cubase 10 Prefs were in fact still being copied from 9.5's pref folder. This, I think is odd (I understand it on a new install but not something I personally want to happen after), so make sure you hide the 9.5 folder. When you do, completely new prefs will be created for 10.

Then the hard swallow of this stuff... I copied my PLE commands, LE commands and port set up xml files from 9.5 and replaced the Cubase 10 versions (far too much work has gone into losing that stuff and starting from scratch). And that was it. I decided to just completely do the prefs from scratch in 10 and it's a bit of a pain in the ass (unless you know all your settings you prefer - which I do fortunately) but in doing so, 10 is running faultlessly. It's like buying a new house. Who wants to walk in from the street and tread dogs brown into the lovely new carpets. Best keep those dirty ole shoes out in the porch.

Obviously there are people that know all of this but some may not and honestly, save yourself the hassle and just build the prefs from scratch. The "convenience" of the previous prefs automatically transferring isn't convenient (for me). It's massive waste of time doing what I should have done from the start.

Cubase 10's laggy GUI problems seem to have gone now, the cursor doesn't look like it has Parkinson Disease anymore, Render in Place seems to render a little faster and yeah, the performance on my machine is fantastic. Anyway, probably time for a beer to celebrate! :)
Click to expand...

You mentioned in another post that you have a large template. How's that working for you in 10?

I'm yet to hear any response from Steinberg (worst support ever) but I am willing to try your method.
 
HelixK said:
You mentioned in another post that you have a large template. How's that working for you in 10?
Click to expand...

Haven't tried big template and VEPro yet. Been too busy trying other stuff out and working. I'll test it out this weekend. Oh, and it looks glorious on a 4k screen now.
 
HelixK said:
You mentioned in another post that you have a large template. How's that working for you in 10?

I'm yet to hear any response from Steinberg (worst support ever) but I am willing to try your method.
Click to expand...
I've been building a largish disabled instrument track template (no VEPro) well over 1000+ tracks right now and it's performing great. Have had a couple of crashes when I open up 10 Kontakt's at once, but other than that no problems. Everything is zippy, looks great and the save times are around 3 seconds, couldn't be happier! Haven't installed all the expression maps and drum maps, gonna do that once most of the tracks are in place so we'll see what save times are like after that...
 
InLight-Tone said:
I've been building a largish disabled instrument track template (no VEPro) well over 1000+ tracks right now and it's performing great. Have had a couple of crashes when I open up 10 Kontakt's at once, but other than that no problems. Everything is zippy, looks great and the save times are around 3 seconds, couldn't be happier! Haven't installed all the expression maps and drum maps, gonna do that once most of the tracks are in place so we'll see what save times are like after that...
Click to expand...

I use vepro but disabled instrument track templates always fascinated me. What about project file sizes, any smaller?
 
HelixK said:
I use vepro but disabled instrument track templates always fascinated me. What about project file sizes, any smaller?
Click to expand...
They are actually a lot bigger. Mines about 1GB right now, ouch! I'm saving to an m2 drive that's really fast. I don't like when it gets over 5 seconds though so we'll see. The disabled instrument template is nice though as the routing is dirt simple. The rack is empty when you start it up and fills up when you enable but all you see is the enabled tracks, no extra midi or VEP audio tracks, just a simple stereo pair per track, easy automation as well...
 
jononotbono said:
Then the hard swallow of this stuff... I copied my PLE commands, LE commands and port set up xml files from 9.5 and replaced the Cubase 10 versions (far too much work has gone into losing that stuff and starting from scratch). And that was it. I decided to just completely do the prefs from scratch in 10 and it's a bit of a pain in the ass (unless you know all your settings you prefer - which I do fortunately) but in doing so, 10 is running faultlessly. It's like buying a new house. Who wants to walk in from the street and tread dogs brown into the lovely new carpets. Best keep those dirty ole shoes out in the porch.
Click to expand...

Did you import only your PLE/LE etc or redid all preferences from scratch ?

Did you have to redo your huge template ?
 

Attachments

  • image.png
    image.png
    464 bytes · Views: 3
Last edited:
InLight-Tone said:
They are actually a lot bigger. Mines about 1GB right now, ouch! I'm saving to an m2 drive that's really fast. I don't like when it gets over 5 seconds though so we'll see. The disabled instrument template is nice though as the routing is dirt simple. The rack is empty when you start it up and fills up when you enable but all you see is the enabled tracks, no extra midi or VEP audio tracks, just a simple stereo pair per track, easy automation as well...
Click to expand...

Ouch indeed, 1GB for 1000 tracks is a lot. Do you work with single instruments per Kontakt or multis?
 
HelixK said:
Ouch indeed, 1GB for 1000 tracks is a lot. Do you work with single instruments per Kontakt or multis?
Click to expand...
Single instruments per Kontakt. As Guy Roland has pointed out the recall of midi to instruments isn't quite reliable as regards routing. The weird thing is, is that my template from 9.5 had over 1000 tracks and is only showing 373mb. I did upgrade to Kontakt 6 this round otherwise everything is the same. Odd...
 
Last edited:
Hmm. Come to the end stages of a very small project (only 6 VI tracks, Fabfilter EQ and Limiter) and the UI has slowed down to a crawl.

Starting or stopping the transport has a delay of 2-3 seconds once the key commands have been pressed.

On mixdown, about half a second of the beginning of the track has been chopped off.

Transferred the project to Logic to finish without any issues.
 
Speaking of Cubase 10’s GUI and anyone who owns Genesis Choir, have you tried it in Kontakt 5 loaded inside Cubase?

On my system, when I push the mod wheel up/down, the “blue dynamics ball” in the Genesis Kontakt GUI is very choppy/laggy. When I try this is Cubase 9.5 and Logic, it’s very smooth like it’s supposed to be.

Edit: I should say it doesn’t affect Genesis’ performance, but this GUI lag seems like a concern since C9.5 does not do this.
 
jononotbono said:
Obviously when you install a new version of Cubase it will copy over prefs from a previous version.
Click to expand...

Up until some version in the past, Cubase would never copy preferences from previous versions. The normal procedure I believe was to do a manual copy of preferences with repeated warnings that you could also copy over bad/infected/inapplicable preferences. Users, and especially new users complained upon every new Cubase upgrade. But now it seems the opposite. Preferences for most users anyway, get copied over into C10 automatically and now the user has to do exactly what you describe to achieve a virgin template .cpr.

IMO, bad preferences is the cause for many user problems. To achieve a virgin template, with most of your own prior preferences copied over takes a lot of time discerning what to copy over. So manually re-building as much as possible without spending too much time can be a better way to go.
 
You must log in or register to reply here.
Top Bottom