Obxd synthesizer

[EvilDragon]

Methinks the back panel is a biiiit too bright on that one but it's all subjective.

[Funkybot's Evil Twin]

Methinks the back panel is a biiiit too bright on that one but it's all subjective.

See, I'm good with the back panel color (got to it by accident and just stuck with it), but I was trying to also tone down some of the lighting highlights which made the label text grayer than I wanted (look at the logo in particular). Without the original assets or really going nuts, it's a balancing act. But yeah, it was just a quick tweak job.

Anyone could just load up the original .png in an image editor and edit the background to their own taste. The hard part was adjusting the x-y-d-h-w coordinates to scale up the size. Also, I couldn't get the Legato/Voice count LED's scaled up correctly so left the size of those as-is and had to fudge the images to hide the borders.

If the original skin designer is around, maybe he can make a larger one that doesn't have such a hard-black background (looks great in 3D renders, not so great on a 2D UI) and a bit larger (1.25x or 1.3x). I have no doubt it would come out much better than my quick hack of an attempt.

[Spitfire31]

I agree that the black-on-black Ilkka Rosma Dark skin is in urgent need of a less black background. It's an ergonomic nightmare for longer sessions than three minutes. I use the discoDSP Classic skin that is maybe less dramatic, but it is a solid work environment.

[PTV]

George, not seeing any of the weird issues I reported before.

Also made myself a quick mod of the new skin. This is 1.3x larger and has a lighter background, which helps distinguish the buttons and knobs from the background. Looks lovely if I may say so. Kudos to Ilkka Rosma for the new skin!

I like it. Also the size is perfect for me

[EvilDragon]

OK yeah, definitely something very weird happening with the state of the plugin. VST3 here:

1. Open OB-Xd, the Accordion patch opens from FMR bank (at least it does so over here)
2. Bump up FREQ AMT knob in the modulation section, so that you can hear the filter modulation more
3. Now disable the Sine button - the LFO still keeps on running
4. Now enable Sine button again - the LFO is turned off now

This is perfectly reproducible here on every new instance of OB-Xd. It's almost like the state of UI controls is not properly initialized in the data structure used, even if the UI shows correct values for knobs and buttons.


EDIT: After clicking the Clear button for MIDI learn, the states of buttons are refreshed apparently. But this seems to be required on every new plugin instantiation.

[zzz00m]

Congrats on v2, well done!

But I still prefer using the VST2 version due to the presets are not visible or browsable from the host DAW using the VST3 plugin, except via the hamburger icon or the right click context menu in the plugin UI.

When using the host DAW plugin window with VST2 I can select the preset and see the preset name in use. It also allows next or previous preset selection, so browsing is much easier.

[Arashi]

George, not seeing any of the weird issues I reported before.

Also made myself a quick mod of the new skin. This is 1.3x larger and has a lighter background, which helps distinguish the buttons and knobs from the background. Looks lovely if I may say so. Kudos to Ilkka Rosma for the new skin!

This looks really good. I prefer your version for the reasons you stated.

[Halonmusic]

That is a beautiful gui

[the.new.me]

George, not seeing any of the weird issues I reported before.

Also made myself a quick mod of the new skin. This is 1.3x larger and has a lighter background, which helps distinguish the buttons and knobs from the background. Looks lovely if I may say so. Kudos to Ilkka Rosma for the new skin!

Nice! I also like this a bit more

Also, was wondering, maybe worth to implament pitch "locks" (sorry dont know how to say). On alot of synths when you move knob it moves per 1 semitone and on OBXD moves from 0.0000000 to 1, its hard to adjust the pitch when aiming for perfect accuracy.

[EvilDragon]

But I still prefer using the VST2 version due to the presets are not visible or browsable from the host DAW using the VST3 plugin, except via the hamburger icon or the right click context menu in the plugin UI.

Presets are browsable in VST3 over here in Reaper...

[EvilDragon]

Also, was wondering, maybe worth to implament pitch "locks" (sorry dont know how to say). On alot of synths when you move knob it moves per 1 semitone and on OBXD moves from 0.0000000 to 1, its hard to adjust the pitch when aiming for perfect accuracy.

Press the STEP button for that.

[the.new.me]

Also, was wondering, maybe worth to implament pitch "locks" (sorry dont know how to say). On alot of synths when you move knob it moves per 1 semitone and on OBXD moves from 0.0000000 to 1, its hard to adjust the pitch when aiming for perfect accuracy.

Press the STEP button for that.

The behaviour is the same with step button on or off for some reason. Using VST 2 on FL Studio

[planetearth]

But I still prefer using the VST2 version due to the presets are not visible or browsable from the host DAW using the VST3 plugin, except via the hamburger icon or the right click context menu in the plugin UI.

Presets are browsable in VST3 over here in Reaper...

I think he means you can't actually see which one you have open unless you use the pull-down menu. It's like you see in these recent examples of the lighter version of the new skin in the last few threads: there's no mention of which patch is in use on the synth. (And actually, this new skin doesn't even show the "hamburger" lines/icon to show where to access the presets or skins. It's the only skin that doesn't show the lines/icon. Fortunately, right-clicking anywhere in the synth gets you to the presets menu. Still....)

It's been the same way on my VST3 versions of this synth during development of the 2.0 version. George thought it was something with JUCE (I think) and that it would be fixed by the time he released this version.

I'd rather use the VST3 version of OB-Xd, but not being able to see on the synth which preset is in use makes it a bit more difficult to find that preset later, if you want to use or modify it. Yes, the preset pull-down list can show you which one is in use, but you can also accidentally choose another while accessing that list to find the one in use in the first place.

Steve

[planetearth]

Well, swapping out the latest VST2 and VST3 versions to test the preset pull-down menu (and compare to OB-Xd v1.5) has led to this:

OB-Xd1.jpg

Uninstalling and re-installing the VST2 or all 3 versions (VST2, VST3 & standalone) didn't help. The themes are where they're supposed to be:

OB-Xd3.jpg

During attempts to uninstall and re-install, the themes ended up in the wrong folder:

OB-Xd2.jpg

I had to drag them to where the error message says they're supposed to go, as shown in the screenshot above.

With the new installer, I can't simply copy the folders, as I used to be able to do with the beta versions. But since the folders are where they're supposed to be (and the necessary .PNG and .XML files are in them), I would think I shouldn't have to copy anything.

Any ideas on what to do, George? Clicking the hamburger icon to change skins crashes the plug-in in standalone mode and does nothing in VSTi mode.

Steve

[Crossinger]

@planetearth: Did you have a custom theme before? Try to rename/move the settings.xml file from the folder and restart everything again (settings.xml should be recreated automatically)