Big problem with Soundbox 1.0.5

Help & Support
1

I just installed Soundbox 1.0.5, and when I opened the pieces I had done with 1.0.4, there was no sound on the Soundbox tracks. I opened Soundbox in Sonar, and the patch was set to the default with no sound. I uninstalled 1.0.5, and reinstalled 1.0.4, and the sound returned with the patch I had originally chosen.

There is no way I could have re-created those settings, as I had no record of which patch I had chosen. Fortunately, everything still worked properly in 1.0.4.

Soundbox was opened in a Unify track in Sonar.

2

I tried re-installing 1.0.5, and opened a test project that I had created in Sonar using 1.0.4 with 3 tracks of Soundbox directly loaded into a track without Unify. I had the same problem with none of the three tracks showing that a patch was loaded. When I uninstalled 1.0.5 again, and loaded 1.0.4 all of the sounds loaded properly in the Soundbox only tracks.

3

At this point, 1.0.5 is not usable for me.

4

Thanks for the information. Are these patches saved as custom (named) presets? Or you rely on save state for recalling these patches?

5

They are standard patches from Kompose Audio’s Soundbox instruments, and your Audiomodern instruments and are saved with the save state.

6

Understood, have you tried to simply save them with a custom name? They should then open with any new update(s)

7

I am sorry, but that is simply not acceptable. I have hundreds of VSTs and have never needed to save a patch every time I use an instrument for it to persist in my DAW through updates in the VST. If you’re going to be changing the format whenever you do an update, then I guess I will have to stop using Soundbox. That’s a shame, because I do like it, and have bought quite a few soundsets for it.

8

I should add that I rarely make changes to the presets that are included with an instrument. I use the stock presets almost exclusively.

9

I’m having the same experience. For reference I’m using Bitwig. All of the presets I’ve created and saved into Bitwig as a Bitwig preset open Soundbox to a default initialized state. I do have all of those sounds saved as Soundbox presets, so I do see them there. But they no longer open by default as a Bitwig preset.

Additionally, I just re-saved a Soundbox 1.0.5 preset into Bitwig, then removed the track, then attempted to reopen the Bitwig preset, and Soundbox still opens in a default initialized state. I’ve already saved over a hundred Soundbox presets as Bitwig presets, so I can no longer open Soundbox saved presets using Bitwig’s browser.

Since Soundbox presets don’t yet have the ability to save text notes per preset, I use Bitwig’s presets and browser to save all of my patch creation text notes.

How can I get access to version 1.0.4 until this issue in 1.0.5 is fixed? Thanks.

10

The question was intended to determine whether the save state function is causing the issue, not to suggest a workaround. We will conduct some tests and address the issue in the next update. Thank you for your patience.

11

Apologies for the inconvenience; we’re investigating the issue and will provide a quick update to resolve it. In the meantime, please check your PM for the previous version.

2 Likes
12

Thank you. I had already saved and am using the previous version. I see that someone else had saved a preset, so I will not try that. 1.0.4 is fine for me until you get this resolved.

13

We identified the issue, which stemmed from DAWs sending a PC0 command after loading, functioning as an “INIT STATE” command. This problem has been resolved in version 1.0.6, which is now available.

2 Likes
14

Thank you very much for addressing this so quickly. Sorry if my initial message sounded confrontational, it was not my intent.

15

I tested 1.0.6 in Sonar, and it works perfectly. Great job! Thanks.

I still am not able to use midi with the stand alone version of 1.0.6, but this is really not a big deal for me as I only use it for importing new packs. It would be nice if I could test them, but not really a problem. Might be different for others though.