Obxd synthesizer

[discoDSP]

The blurry may be caused by a bad downscaling from 2x bitmaps. Try using lanczos algorithm instead.

[discoDSP]

New 2.1 Nightly Build (macOS and Windows).

What's new

• Fixed Voice and Legato bitmap issues with 1x assets in Windows and Linux.
• Fixed Grey skin assets bitmap sizes.

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

[Funkybot's Evil Twin]

The new build fixes the reported issues.

Will look into rescaling images from prior skins.

[discoDSP]

@funkyboy I have downscaled your skin using XnViewMP Lanczos algorithm.

https://www.discodsp.net/obxd-nightly/t ... nkybot.zip

I think it looks good.

[EvilDragon]

I agree with Funkybot that using 2x assets is better even at 100% scaling. This needs to be an option in the XML IMHO. Please don't hardcode which assets get used depending on platform, there should be an override.

[discoDSP]

It's not better really. They look "sharper" but it's actually a very aliased and low quality interpolation scaling algorithm that's very noticeable when compared to macOS GUI window. Anyway will consider adding a force HiDPI mode.

[Funkybot's Evil Twin]

In most cases, I was able to improve the knob assets dramatically by changing the resampling algorithm. But unfortunately, the buttons on my own skin get visibly softer regardless of which algorithm I use.

That said, I'm using a modified version of Ilkka Rosma as my main skin, and that looks pretty good. I'd appreciate a force HiDPI option, but won't beat a dead horse. Especially since the skin I'm actually using looks pretty good as is. Thanks George!

On a 1-10 scale of "wishlist" items for OB-Xd, a "Preset Menu Bar" that displayed the current Bank name, allowed users to create new banks, and also showed current Preset Name with forward and previous buttons would be a 10. Bonus points if there was a display that showed the current parameter value. On that same scale, a force HiDPI option would be like a 3. A "Lock MIDI Map" option would be an 8.

[discoDSP]

@Funkybot feel free to add those to https://github.com/reales/OB-Xd/issues and label as enhancement so we don't miss them on this thread

[discoDSP]

New 2.1 Nightly Build (macOS and Windows).

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

What's new

• Fixed LFO buttons not working or reverted issue.

That's one of the most cumbersome bugs I've dealt with but looks finally fixed.
Further testing and reports are highly appreciated.

Cheers,
George.

[EvilDragon]

Can you please see if you can do the same thing to all other buttons, because I distinctly remember it also happening with keytrack, BP and 24dB, sometimes even Unison button?

[discoDSP]

Code has been updated for all button states so it’s very likely that those are fixed too. Please take a test to the latest nightly

[EvilDragon]

Will do!

[Funkybot's Evil Twin]

@Funkybot feel free to add those to https://github.com/reales/OB-Xd/issues and label as enhancement so we don't miss them on this thread

Added a few items to the list there. Will check out the latest build.

[Funkybot's Evil Twin]

New 2.1 Nightly Build (macOS and Windows).

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

What's new

• Fixed LFO buttons not working or reverted issue.

That's one of the most cumbersome bugs I've dealt with but looks finally fixed.
Further testing and reports are highly appreciated.

Cheers,
George.

George,

MIDI Control of buttons is completely broken in this release. I can't get any button to respond to MIDI CC messages. Knobs work as expected.

To reproduce:

1. Open OB-Xd
2. Move a hardware MIDI control previously mapped to a button

Result: nothing happens. Ok...

3. Click MIDI Learn
4. Toggle the button state using your mouse
5. Move the MIDI control on your hardware surface to learn the button

Result: The Learn mode light comes off. Now...

6. Move the controller you just assigned

Result: The button does not respond to MIDI messages.

This is true for all buttons I've tried (LFO, OSC Waveform, Sync). Using the VST2 or VST3 in Reaper, Windows 10.

[discoDSP]

Will check. Do button behavior in GUI works as expected now? At least here does.