KVR Audio

zmix · Post by **zmix** » Fri May 01, 2020 3:26 pm

Exciting news...

When I load the standalone App (OB-Xd V 1.5.0) the state is not recalled, but at least it can be loaded, which now recalls the saved CC assignments!

Recalling the saved state does not recall the selected skin however, and the default is a bit of a mess:

Screen Shot 2020-05-01 at 11.23.24 AM.jpg

Loading either of the "Classic" skins fixes that:

Screen Shot 2020-05-01 at 11.24.30 AM.jpg

Unfortunately the state cannot be loaded in the Audio Units version, and the skinning is still a mess:

Screen Shot 2020-05-01 at 11.30.54 AM.jpg

george · Post by **george** » Fri May 01, 2020 6:43 pm

Why are you mixing 1.5 and 2.0 data folders? Considering 2.0 is under development, I’d use it for testing purposes only.

zmix · Post by **zmix** » Sat May 02, 2020 12:37 am

discoDSP wrote: Fri May 01, 2020 6:43 pm Why are you mixing 1.5 and 2.0 data folders? Considering 2.0 is under development, I’d use it for testing purposes only.

Not intentional.. I simply launched the standalone (didn't even know it existed) and posted when I saw there.

As far as I know there is no 2.0 standalone..?

It's encouraging that the 1.5 standalone has the ability to remember assignments though!

Halonmusic · Post by **Halonmusic** » Sat May 02, 2020 2:19 am

what a mess.

george · Post by **george** » Wed May 06, 2020 6:50 am

New nightly builds: https://www.discodsp.net/obxd-nightly/

Parameter automation refactor isn't compatible with 1.5 or older releases. Manufacturer ID has been changed as workaround. 1.5 or lower (Obxd filename) and 2.0 (OB-Xd filename) can be used together without conflicts now.
2.0 Skins folder has been renamed to Themes to avoid mixing and messing up GUI windows between versions.

Cheers,
George.

planetearth · Post by **planetearth** » Thu May 07, 2020 1:13 am

discoDSP wrote: Wed May 06, 2020 6:50 am New nightly builds: https://www.discodsp.net/obxd-nightly/

Parameter automation refactor isn't compatible with 1.5 or older releases. Manufacturer ID has been changed as workaround. 1.5 or lower (Obxd filename) and 2.0 (OB-Xd filename) can be used together without conflicts now.

2.0 Skins folder has been renamed to Themes to avoid mixing and messing up GUI windows between versions.

Cheers,
George.

Thanks for your work on this, George. I've been following it for a couple of weeks, and I'm wondering if you'd say that v2 is now at the point where it can be installed alongside v1.5. This is a non-production machine, so even if both installations go sideways, it's nothing critical. But now that more parts of v2 have been "separated" from v1.5, I'd like to start testing it.

Steve

george · Post by **george** » Thu May 07, 2020 4:53 am

v2 has different filename now, loads themes from a different location and is using a new manufacturer code, so you can test it safely as it won't interfere with 1.5 or older. Previous builds didn't had these new changes and thing could get messy, especially with GUI themes and parameter code changes.

Current bank files have the child element names for program and parameters starting with numbers, which are not valid starting XML characters and when the plugin starts getXmlFromBinary makes an assertion (over 9000 to be precise) and debugging is extremely hard. Because of this issue we need to write a 1.5 importer (already done) and refactor the parameter engine with a better design (pending, but half way right now).

planetearth · Post by **planetearth** » Thu May 07, 2020 9:50 am

discoDSP wrote: Thu May 07, 2020 4:53 am v2 has different filename now, loads themes from a different location and is using a new manufacturer code, so you can test it safely as it won't interfere with 1.5 or older. Previous builds didn't had these new changes and thing could get messy, especially with GUI themes and parameter code changes.

Current bank files have the child element names for program and parameters starting with numbers, which are not valid starting XML characters and when the plugin starts getXmlFromBinary makes an assertion (over 9000 to be precise) and debugging is extremely hard. Because of this issue we need to write a 1.5 importer (already done) and refactor the parameter engine with a better design (pending, but half way right now).

I'll take that as a "Sure, why not? What's the worst that could happen?".

Thanks again, George!

Steve

george · Post by **george** » Thu May 07, 2020 9:53 am

Reports are welcome

planetearth · Post by **planetearth** » Thu May 07, 2020 11:43 am

discoDSP wrote: Thu May 07, 2020 9:53 am Reports are welcome

Good, 'cuz here's what I found....

Using the VST3 version in the latest build of Cakewalk by Bandlab, I don't see any indication of which preset is in use, or any way within the synth to change presets. I can change banks using the "hamburger" fly-out menu, but I can't choose a preset within the bank unless I then go to the "Programs" fly-out. And I can use the VST3 window's control for changing presets, but there's still no indication as to which one is in use.

OB-Xd.jpg

And, the synth wants you to put the "skins" (now called "themes") in the Documents/DISCODSP/SKINS folder, but that's not where they're supposed to go, according to the readme file.

OB-Xd2.jpg

Minor issues like those aside, shouldn't the "Banks" fly-out be above the "Programs" one, since you'd choose a bank first?

Also, the size of the screen when it shows the error about the missing "skins" is much larger than the actual synth's default screen is, for some reason. (You can't see it in the screenshots above, since KVR limits the dimensions of images, apparently.)

Steve

george · Post by **george** » Thu May 07, 2020 12:20 pm

planetearth wrote: Thu May 07, 2020 11:43 am Using the VST3 version in the latest build of Cakewalk by Bandlab, I don't see any indication of which preset is in use, or any way within the synth to change presets. I can change banks using the "hamburger" fly-out menu, but I can't choose a preset within the bank unless I then go to the "Programs" fly-out. And I can use the VST3 window's control for changing presets, but there's still no indication as to which one is in use.

That's probably has todo with current JUCE framework used. I think latest 5.4.7 solves this but it needs updates some outdated code before. I think VST2 was OK, can't remember clearly.

And, the synth wants you to put the "skins" (now called "themes") in the Documents/DISCODSP/SKINS folder, but that's not where they're supposed to go, according to the readme file.

Yep, it's fixed already on the development branch, maybe it's time for another nightly today

Cheers,
George.

planetearth · Post by **planetearth** » Thu May 07, 2020 12:42 pm

Thanks, George. I forgot to mention that I used the latest nightly build, the one dated May 6.

Steve

george · Post by **george** » Thu May 07, 2020 12:43 pm

Yep, I will try to compile another one tonight.

rasmusklump · Post by **rasmusklump** » Thu May 07, 2020 1:12 pm

Where do I have to put the skins?
Can't open it at all right now...

zzz00m · Post by **zzz00m** » Thu May 07, 2020 2:25 pm

planetearth wrote: Thu May 07, 2020 11:43 am
Using the VST3 version in the latest build of Cakewalk by Bandlab, I don't see any indication of which preset is in use, or any way within the synth to change presets.

I get this issue when using the release 1.5 version of the VST3. It just says "No Preset" in the plugin preset window within the upper bar of the Cakewalk plugin window, and the dropdown menu there is blank. But the VST2 version always shows the patch in use there, and the dropdown shows the list of available presets in the chosen bank.

Of course, the right-click flyout menus on both the VST2 and VST3 show the patch menu, including the patch in-use.

I can also confirm that there is a similar issue in Ableton Live 10 and Studio One 4 with VST2 vs. VST3.

The presets info is inaccessible in VST3 except via the right-click flyout menu.

Obxd synthesizer