will you add them??
how??
Presets can be found here:
Downloads, Banks, Patches, Presets, etc. (kvraudio.com)
I think with some thinkering they can be added to the LV2 package…
Oh I’d love a GUI for the beta plugin, being a synth noob and all
Who and how??
Hey, what is the status on this? Need some help?
@krullebolle the status hasn’t change.
You can fork GitHub - spunktsch/OBXD-mod-gui.
The Layout needs to be converted to flexbox instead of grid. To keep max. compatibility according to @falkTX.
Then you can send a pull request to GitHub - moddevices/mod-lv2-data: MOD LV2 data (plugins, presets and pedalboards)
On the code-side a blocker is gone now.
The OBXD build in the MOD store comes from DISTRHO-Ports which is quite the old version now. But I switched to use “meson” (fancy new build system) on the DISTRHO-Ports to replace the old “premake” system.
The mod-plugin-builder cannot support meson right now due to technical debt sorta issue, and having OBXD on that big repo/project is not exactly the best way to handle it so I have a fork at DISTRHO-Ports/OB-Xd.
I have yet to port the custom changes made to OBXD in this new repo (but it just needs a build with desktop GUI disabled).
The good news is that the JUCE side is done now, I have spent some time during holidays setting up my juce fork at DISTRHO/JUCE to support 5.x, 6.0, 6.1 and 7.0 versions of JUCE. That covers pretty much all versions used in plugins.
Then did the mod-plugin-builder side too to match, as can be seen in https://github.com/moddevices/mod-plugin-builder/tree/master/plugins-dep/package
So we have packages for 6.0, 6.1 and 7.0 versions of JUCE with all the patching needed for cross-compilation, LV2 support (relevant only in version < 7) and with desktop GUI disabled.
There are some licensing issues that have popped up due to DiscoDSP getting the rights and artwork license for the plugin.
While the code remains open-source and GPL, the artwork is their IP and they do not allow to be reused or redistributed. So the target is to use a version before DiscoDSP got in control, backporting any fixes that do not touch the artwork side of things.
For MOD this doesnt matter much as we can use the custom gui @spunktsch has started.
A few posts above @spunktsch mentions the TODO items for the GUI. If anyone wants to try to tackle those it would be very welcome.
The part with updating and building new OBXD version can happen in parallel, it does not block any GUI work. We can use the OBXD in the beta store as reference point, the parameters have not changed.
Do you have an example from a plugin already using the flexbox css style format?
Its been a longtime since I done CSS, but if I find time I`ll look into it.
For users without programming knowledge, can they wait until the plugin is released with a GUI and appears in the store?
There’s currently some parameters that act like buttons, but that are represented as dials in the MOD web editor. Would it be at all helpful to list these here or somewhere else? I’d love to see OBXD on the official store, I’ve been using the current Beta version a lot and it’s been functioning well.
Cheers
Yes please !
So, I got around to tinker about with it. Fixed some visual bugs, added presets.
Im not good at creating from scratch, merely a fixer. So I wont be creating the code again from scratch.
Please test this, so I can change stuff for the better.
Not sure if MOD GUI
makes sense as “brand name”, maybe we just omit it?
My only remark would be that the “glide slope” is not aligned with the other knobs.
Looks fine otherwise.
haha that’s a flemish-dutch meme and it had me laughing out loud
That looks slick indeed and since we aim for optimal user experience; a nice update to a full blown downloadable plugin with GUI would be a nice wrapper for this gift
What’s the next step?
Haha thanks, I won’t touch the gui anymore
So basically it’s about ready except for… Still grappling with this:https://discourse.zynthian.org/t/mapping-instrument-effect-property-values-to-labels/5366/8
as in the first post of this topic, the voices and the legato mode should be enumerated lists… I would hate to scale these from 0-1 to eg 0-7 as that would mean we have to rewrite all presets…
Thats my last issue to solve and then I think its ready.
you really are forcing me to go update the obxd version in distrho-ports. I really should just go and do it soon…
not sure if there were any parameter changes between the old and updated version of discodsp, still need to check that.
but worst case we keep the current version as in the store as-is
Not forcing you to do anything
For me the current (1.2 ? ) version is ok. DiscoDSP did in fact quite some visual changes with his latest version.
Actually, he added alot of small buttons and some dials.
https://www.discodsp.com/obxd/#home
If you update, I can adapt. I see all the parameters for the new version already in the obxd.ttl file. But it will clutter the gui more, I quite like the style @spunktsch started.
If you don`t update, also good for me, I like the synth as is.
So, fixed my last problems. Have some screenshots:
To do:
- add more presets
- change names to be more correct in the settings tab.
Will prolly do this sometime this week.
So I did it, finished this thing as far as I am concerned. I did however still change the GUI slightly
Will do some basic troubleshooting if necessary.
Preset Banks added: They are ordered the one bank after the other from [A-Z]
- A selection of 27 interesting presets made by Steven Grace
- The OB-Xa patchbook bank http://www.electrongate.com/obfiles/OB-Xa/patchbook.html
- The KVR community bank
I hope these have enough (300 ish) interesting presets.
What I did not do was rewrite the whole CSS thing in flexbox style, I know, its not flexible at the moment. Sorry @spunktsch ! I just like to troubleshoot and fix, I hate restarting from scratch…
The GUI:
There are some knobs and buttons present in the settings tab that are not on the gui, these are from version 2 of the OBXD plugin. Version 3 from DiscoDSP has even more, but I would not update to that one, as no presets make use of these and they are really not necessary for the OBXD sound.
I am curious to make a drone with the filter self oscillating (self osc pushb).
If anyone has any remarks, make them now, I will make a pull request this evening? Unless @falkTX has some remarks still…