Here is what I am running into. Any help or insight would be apprecaited:
Test:
Cubase 13 Pro
Cubase 14 Pro
Spitfire BBCSO Pro
Cubase 13
500+ Tracks of BBCSO Pro Violins 1 Long
Open Track 500 instrument and mouse scroll up and down through the list to choose another instrument such as oboe
Load it in and choose articulation and no crash
Cubase 14
Load maybe 40 or more tracks
Open last track and scroll thought instrument selection and Cubase 14 crashes
Cubase 13 stable at over 500 plus tracks
Cubase 14 can hardly handle 40 when mouse scrolling in selection menu of Spitfire BBCSO Pro
Current Workaround: Don’t use the pop open menu to choose instrument but use the back and forth clickable selection and no crash
Does anyone know of a fix or aware of this issue?
Any help would be appreciated
Machine Specs
24 Cores
64 GB RAM
1 TB Nvme2 Windows
4 TB NVme2 Storage
Cuabse 13 and 14 at latest patches
Windows 11 at latest patches
All test done from starting point of empty project so no shrapnel or leftovers from project corruption.
Also tried in Reaper and over 500 tracks no problem. Just seems to be the way Cubase 14 Pro handles BBCSO Pro.
Sadly i have to confirm this issue. Its also not just Bbc pro. Its for Kontakt instruments too.
Because of that i have switched to reaper.
The developers should enable a way to load external plugins as seperated CPU process. Something Reaper has for years. I can load the entire bbc orchestra plus a spitfire air reverb as insert for each individual instrument in reaper and reach barly 25 cpu peak . Its because i can load any process fx or plugin as seperated or dedicated process.
Dear developers in the 21 st century where send fx are a outdated method outside of the cubase world where hundreds of people crying about the poopies performance of cubase 14 pro you should please listen to give us what it needs that is realtime 3d reverbs high cpu demanding plugins all this is only possible in limited capacity in cubase 14 pro.
Besides that i will take a look into cubase 13 maybe thats also a good option.
Sadly cubase 14 pro is also not capable of reading keyswitches streamed from dorico pro into cubase 14 correctly. Reaper and Ableton have not this issue
Made a test in Cubase 13 pro and it is working better but still poopies performance. Its interesting to see how differently the peak and asio guard is working. Also the interface is significantly faster than cubase 14 pro
Completely Reinstalled Windows
Installed Cubase 14 Pro Latest Update
Installed all latest windows and driver updates
Everything FRESH and pristine
Now here is the kicker.
Open Cubase 14 Pro loaded nearly 400 tracks of BBCSO Pro no crash
Saved the project and reloaded.
CRASH!!!
Totally re-producable!!!
Cubase can have hundreds of BBCSO Pro tracks loaded BUT ONCE YOUSAVE AND RELOAD the project it will crash when you open the menu interface on any of the tracks for BBCSO Pro
Hopefully Steinberg sees this thread. There is something wrong with Cubase 14.
Reaper, Studio One and Pro Tools do not have this issue.
I get the same as you with a lot fewer tracks. It crashes when I try to change the sound in BBCSO (core version). It works in CB 13 but not in 14. The dmp file shows a crash in BBCSO.
I’m using the expression map from Spitfire.
I wish Steinberg would see this thread and have a look instead of just saying your computer is the problem. I went down the rabbit hole believing their tech support BAD IDEA and wipe my whole system and just put on BBCSOPro Cubase 14 and it still crashed. 2 Days of solid work down the drain. At least now I seem to have nailed it down to when you save it to the project file and then try to load and use it.
The project works its just you cant open the drop down menu in BBCSO to choose a different instrument. You have to use the left and right change instrument buttons or else it will crash
Hopefully this will help anyone else who runs into this with Cubase 14 and BBCSO,
@Mads_Vinding Thank you. Now I know its not just Pro but Core as well.