OS: Win 10 64-bit Home
Mobo: Gigabyte X570S AORUS Elite AX
CPU: AMD Ryzen 9 5950X 16-core, 32-Thread, no overclocking
RAM: 64 Gb. Crucial Ballistix 3200 MHz DDR4 DRAM
______________
I’ve read both threads here on issues with Cubase but even the more recent for Cubase 13 where the user loaded it through the VSTi rack instead of the Project windows - didn’t work for me.
I just got my first SoundBox instrument - Tranfigured Orchestra by Sonora Cinematic, so for now the only SB instrument I have.
Symptoms of problem:
1. No Sound
As seen in opening screenshot, I can get the instrument to load, but even though the virtual keyboard responds to both MIDI notes on the track and live playing, so sound. I have everything set to Any and all MIDI inputs - or global.
I’ve loaded this as a duplicate of another track and as a “virgin” new one. Same thing happens.
2. Hide or Delete SoundBox Track = Cubase 12 & 14 Freeze (Crash)
Have to nuke them in Task Manager. This sometimes also corrupts my .cpr file where I get a Steinberg “can’t find license” as I fire the progs up again. So have to use a .bak file before Sound Box was every loaded.
I’m not an engineer or pro musician but have been using Cubase for 23 years, so not a newbie to the DAW environment and to VSTi and how they work (i.e. have NI Kontakt Komplete and others).
I have uninstalled SoundBox through a thorough uninstaller (Revo Uninstaller) that removes any and all traces that most uninstallers leave behind, and then re-installed. Due to that Cubase phased out VST2 in v.13, I no longer install those versions or the Mac AU since I don’t use a Mac.
I’ve also rebooted my OS two times. Still stuck in no-sound and there is no point in using Sound Box right now.
Help appreciated.
Hello @Soniclight
Thanks for reaching out and sorry to hear about that. Which Soundbox version are you using? Do you have the same problem in Standalone mode as well?
As stated in the subject line, SoundBox v.1.1.0. When I reinstalled it, I only installed the VST3 version as explained above, and did not install the standalone because I never use those versions of VSTi or fx - I only use the in-DAW versions. Because I want to be ready to record in case I come up with something fabulous… 
But I did try the standalone when first installed before the issue started to happen in Cubase but at that time couldn’t figure out how to load the sound patch/VSTi.
Thanks for the information, that does sound unusual.
We encountered a similar issue once before with a user loading our Opacity library. In that case, providing a fresh download of the library resolved the problem after re-importing it. It was an isolated incident among thousands of users, so quite rare. I can only assume it was a corrupted download or extraction.
I’d recommend requesting a fresh copy of the library and importing it again. Would it be possible to ask the developer to provide that?
OK, downloaded another copy of Transfigured Orchestra, but before I do this again, question:
I keep all my NI/Kontakt and other VSTI, samples, audio and video projects, etc. on my D:\ drive due to how much space these take. And I like a streamlined OS that a backup every evening.
So I created a folder for SoundBox there too and put the .sbpack in there, then loaded it in SoundBox in Cubase.
— Could this be causing the problem (maybe .sbpacks only work when on the OS?) Probably not, but figured I’d ask before I end up where I was with all of this…
Thanks.
PS: My deleted post below was a musing on if I had Cubase rescan the entire D:\ including the SoundBox folder. But it didn’t do anything - the folder is empty in the MediaBay due to Cubase is not programmed to recognize SoundBox content. As I understand it.
You can change the default library location from the Settings tab. When a new location is selected, all content will be moved there, and Soundbox will use this new location moving forward.
Got a fresh new copy of the instrument, created a new track, loaded it - I now realize that one has to double-click on the instrument to turn the choice to red font for sound to happen. Most presets in VSTi are single click. So audio issue is fixed.
But:
… when just disabling or deleting the track with the Sound Box instrument, Cubase still freezes and I have to nuke it through Task Manager.
Cubase does not create a DMP file for a freeze but I looked online and would have to download, install and then run ProDump64 while Cubase is launched and used to recreate this and then provide that DMP file.
Getting complicated, but will see if I can do this.
1 Like
I’ve sent you a PM with our upcoming version 1.1.1, which we believe resolves this issue. This version will be officially released in a few days, along with some new features and a tutorial.
Please let me know if it addresses the problem on your end.
1 Like
YES, v.1.1.1. solved the issue! Thank you.
Testing on disabling and deleting a SouncBox track that froze Cubase every time… now no problemo.
One thing I noticed - or didn’t see with v.1.1.0 – was needing to restart Windows after fresh install. Maybe that locked in something for Cubase and/or Windows to work right with SoundBox that the previous version didn’t.
At least on my OS which I have tweaked some under-the-hood over the years since Windows XP. But I’m no programmer - just a bit geeky - and doubt that those changes affected SoundBox.
Just glad things are working.
