Obxd synthesizer

[onerob]

Can confirm 2.0 overwrites all formats of 1.5 (VST2, VST3, AU) and also gave me an error about not being able to find the Themes folder, then it crashed my DAW (Live 10.1.17)

After some further investigation it looks like the issue may be related to the installer using the same package identifiers. I have compiled a new macOS build for testing at https://www.discodsp.net/obxd-nightly/

Thanks, it works. The 1.5 and the nightly installer copies now live together. My copy of 1.5 installs under the Datsounds manufacturer name. Both copies currently call themselves 'OB-Xd' within my DAW, but that's OK.

[martinique]

> EvilDragon
What you think? I eliminate the hamburger: the right click - to get it on the plug - is the best choice).
If anyone is interested I can upload the new 'coords.xml file'.

[EvilDragon]

I don't think hiding the hamburger is the best solution. Right click is hidden and not intuitive, having the hamburger there lets you know you have options.

[martinique]

>EvilDragon
Maybe something like this?
But the skin down is just graphic art...

The fact is that I am not yet able to find the ideal position in the 'coords.xml' file to place the hamburger just as I drew it in the photo.
Any idea about which measures to set 'x y d' to get exactly that position?

[mcbpete]

Maybe move the menu icon to on-top-of (or just below) the top left 'screw' as that section isn't really used for anything.

Before I update from 1.x to 2.x can anyone confirm or falsify whether 1.x presets (.fxb and/or .fxb) work on the new version? I notice in the changelog/release-notes (and also a post by someone in Gearslutz regarding preset-incompatibility):

Updated Banks with 2.0 compatibility.

Is there any way of modifying banks to make them work in the new build?

[Funkybot's Evil Twin]

1x is used for Windows and Linux because they don't handle HiDPI as good as macOS. Their resize scaling quality is quite bad to be honest. We will work in getting better HiDPI support for Windows and Linux later on.

1x images definitely don't get used on Windows here. Whenever I created skins for OB-Xd, only the 2x assets were used. The 1x assets were not used. I'm on Windows 10, 100% scaling, widescreen monitor but not UHD. And the 2x images downscaled to 1x look perfectly fine.

[george]

Then something is wrong in the code because 1x assets are forced to be used in Windows and Linux systems.

For example, check https://github.com/reales/OB-Xd/blob/ma ... r.cpp#L490

[Funkybot's Evil Twin]

Then something is wrong in the code because 1x assets are forced to be used in Windows and Linux systems.

For example, check https://github.com/reales/OB-Xd/blob/ma ... r.cpp#L490

Here is a test skin: if you see pink and blue assets for everything, that means the 1x assets work. If you get a functioning skin with stripes and knobs and buttons, then that means the 2x assets are being used.

https://www.dropbox.com/s/aiwfa5suuvs8g ... x.zip?dl=0

Here's what I see:

1. The 2x assets are used on Windows
2. EXCEPT for the menu button where the 1x asset gets used

Note: I'm not suggesting this get "fixed." I think the 2x assets downscaled to 1x look great. I'd rather see the 1x assets removed entirely and only 2x assets get used.

I'm using Windows 10. My screen resolution is 2560x1080 with scaling at 100%. My DAWs are Reaper, Studio One, and Cubase. Same result in all three DAWs. The 1x assets definitely do not get used except for the 1x menu button.

[george]

Right, #if JUCE_WIN || JUCE_LINUX conditionals were wrong. I have updated them to #if JUCE_WINDOWS || JUCE_LINUX and will upload a new nightly now. Thanks a lot for the report Funkybot, you have managed to be the golden tester!

[george]

New 2.1 Nightly Build.

What's new

• Windows builds now use proper 1x assets bitmaps.

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

[Funkybot's Evil Twin]

New 2.1 Nightly Build.

What's new

• Windows builds now use proper 1x assets bitmaps.

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

Just tried it out and while you technically fixed the bug, the problem is, the skins now look worse (softer)! They looked way sharper before. Windows does a fine job downscaling 200 down to 100. This is basically the same approach U-he takes. The only problem with Windows scaling is those in-between sizes can have weird artifacts. But I think you only offer 200 and 100 sizes, so I don't think this is an issue.

Also, now on a few themes, the legato mode and voice count images are broken, including the Ilkka Rosma Dark theme.

I'd really suggest ditching the 1x assets in Windows and trying out a build with 2x only.

EDIT: also, some skins are downright broken now. Try this:

1. Open OB-Xd
2. Go through the various included themes
3. Pay attention to the legato/voice LED dropdowns and the skin backgrounds (Disco DSP Gray for example has a huge background now but the legato/voice dropdowns work, many other skins the backgrounds are ok but the legato/voice dropdowns are borked)

[george]

Thanks for the report. All skins should be broken because the AddList function doesn't have the 1x assets conditional. Will fix and build a new nightly in a moment.

[Funkybot's Evil Twin]

Yeah, but the 1x skins are worse! I don't think you should fix them. I think you should ditch them!

[george]

1x aren't worse in my opinion. They are using a better interpolation algorithms hence the "softness". The sharpening effect actually makes them look jaggy as reported by Teksonik some pages ago.

[Funkybot's Evil Twin]

1x aren't worse in my opinion. They are using a better interpolation algorithms hence the "softness". The sharpening effect actually makes them look jaggy as reported by Teksonik some pages ago.

Here's a side-by-side compare using one of my skins...Left is 8/6 build, right side is 8/9 build.

OB-Xd Comparison.png

You may have to Open in New Tab to get the full-size image. Look at the buttons and knobs on the right side vs. the left. That's not better.

EDIT:
After posting, there was a substantial improvement to knobs by changing the resampling algorithm.