Obxd synthesizer

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
OB-Xd - Virtual Analog Synthesizer

Post

aumordia wrote:obxd might be a candidate for a fork
Am I right in thinking this has already got 'forked' before. Didn't we have the original 2Dat version, then there was the dozius fork, then the Soshi Studio one (or was that the same branch), then the 2Dat version with Soshi Studio GUI, then the discoDSP one

Unless some of those later 'forks' are just the same ones but reappropriated by another company.

Post

mcbpete wrote:
aumordia wrote:obxd might be a candidate for a fork
Am I right in thinking this has already got 'forked' before. Didn't we have the original 2Dat version, then there was the dozius fork, then the Soshi Studio one (or was that the same branch), then the 2Dat version with Soshi Studio GUI, then the discoDSP one

Unless some of those later 'forks' are just the same ones but reappropriated by another company.
And why does the fact that it got forks already prevent someone to create another fork? Are we going to discuss semantics now? :roll:

If you want to add something, answer the question below:
aumordia wrote: obxd might be a candidate for a fork:

branch 1) keep the sound as it is, add some quality-of-life improvements like a preset browser, etc.
branch 2) in addition to the quality-of-life improvements, add new features that could impact the sound.
Fernando (FMR)

Post

Errr, no....easy tiger, think someone's unnecessarily on the defensive here ! Just mentioning there seems to be a lot of branches/forks out there so there might be an 'unbranched' fork that's been less hacked up and so easier to clean up and continue by whomever is taking the project on

Post

mcbpete wrote:Errr, no....easy tiger, think someone's unnecessarily on the defensive here ! Just mentioning there seems to be a lot of branches/forks out there so there might be an 'unbranched' fork that's been less hacked up and so easier to clean up and continue by whomever is taking the project on
Good luck with that. Open source... where everybody owns everything... and nobody owns anything.
You need to limit that rez, bro.

Post

mcbpete wrote:Errr, no....easy tiger, think someone's unnecessarily on the defensive here ! Just mentioning there seems to be a lot of branches/forks out there so there might be an 'unbranched' fork that's been less hacked up and so easier to clean up and continue by whomever is taking the project on
Sorry :D There's been so much heat and fires these days that I explode almost at the first spark. :clown:

I can't help feeling revolted these days.

Yes, I agree. But I think that the original code from 2Dat is still available in the repository. Don't forget to tell what's your option:
aumordia wrote: obxd might be a candidate for a fork:

branch 1) keep the sound as it is, add some quality-of-life improvements like a preset browser, etc.
branch 2) in addition to the quality-of-life improvements, add new features that could impact the sound.
Last edited by fmr on Wed Oct 18, 2017 6:48 pm, edited 1 time in total.
Fernando (FMR)

Post

If all the energy that went into arguing about this synth were spent on learning JUCE we'd have a preset browser, Osc drift, and maybe onboard chorus and delay :hihi: regarding compatibility, one of the benefits of JUCE is you build once and can roll out across multiple platforms. If I were a developer of software synthesis, I would take a look at learning JUCE. My wife who is a computer science grad and has worked as a developer said even I'm smart enough to figure it out. I remwmber her learning new programming languages regularly when she did that work, this isnt even that, just a new toolset. It just takes will and time. Don't bitch about it if you lack either, someone out there might be up to it and it would be worth it to them even if it isn't to you. And one more thing: are we there yet? :phones:
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

braj wrote:And one more thing: are we there yet? :phones:
Did you vote yet? :hihi:
aumordia wrote: obxd might be a candidate for a fork:

branch 1) keep the sound as it is, add some quality-of-life improvements like a preset browser, etc.
branch 2) in addition to the quality-of-life improvements, add new features that could impact the sound.
Fernando (FMR)

Post

Well, I think we should aim low right now and get a preset browser, which would be pretty isolated from the rest of the codebase I would think, and not likely to break anything. The developer that takes up the gauntlet could then determine what else they could do.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

braj wrote:Well, I think we should aim low right now and get a preset browser, which would be pretty isolated from the rest of the codebase I would think, and not likely to break anything. The developer that takes up the gauntlet could then determine what else they could do.

:tu:
Fernando (FMR)

Post

This shows a basic preset browser is possible:

https://forum.juce.com/t/custom-gui-for ... ding/22365
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

fmr wrote:Yes, I agree. But I think that the original code from 2Dat is still available in the repository. Don't forget to tell what's your option:
aumordia wrote: obxd might be a candidate for a fork:

branch 1) keep the sound as it is, add some quality-of-life improvements like a preset browser, etc.
branch 2) in addition to the quality-of-life improvements, add new features that could impact the sound.
I say .... branch 1 and then if all seems going well add branch 2 to branch 1. Like a big wonky stick :D

The reason I mentioned all the branches is I remember during the Soshi Studio 'incident' a year or so ago (which I'm still sore about paying for !) before DiscoDSP took it over that there was discussion about the sound of the existing build:

http://www.kvraudio.com/forum/viewtopic ... 5#p6589671
klinik wrote:please take a look why the 1.3 version is consuming more CPU but also the sound seem to be "different", worse for a lot of our ears.. :tu:
http://www.kvraudio.com/forum/viewtopic ... 5#p6589749
aesthete wrote:Yes please, the original was fatter and more authentic. 1.3 is thinner.

Here is the older version 1.2.1. Backup your presets/Use at your own risk.
https://we.tl/reW4KUKRGO
http://www.kvraudio.com/forum/viewtopic ... 5#p6589749
klinik wrote:the sound seem to be "different", worse for a lot of our ears.. :tu:
http://www.kvraudio.com/forum/viewtopic ... 0#p6590325
filter303 wrote:There are definitely big differences in the CPU usage between the new and the old version. New version is using more CPU per voice but the old one always uses the same amount of CPU no matter if it's playing something or not.
http://www.kvraudio.com/forum/viewtopic ... 5#p6590182
discoDSP wrote:The filters DSP are from latest 2Dat sources but it looks like people prefer the previous version one. Will check.
And I've no idea which 2dat build we actually have the source for that'll (potentially) be developed on !

Post

I vote for option #1 since is changing the sound but not to a something new, would be great to bring back the original filter sound. Also a more complete drift options (different setting for each osc and also for glide and filter) will make it behave more "analog" without changing the sound per se. Thanks!

Post

Does anyone have the 2 different filter versions, so we can confirm if "different filter sound" is not just psychoacoustics ?
[====[\\\\\\\\]>------,

Ay caramba !

Post

Mutant wrote:Does anyone have the 2 different filter versions, so we can confirm if "different filter sound" is not just psychoacoustics ?
There is a change in CPU use too....

Post

this is the stuff that you as users could really help out on -- can you pin down precisely which version "sounds best," and prove (e.g. through null tests) which versions "don't work" because they sound different? that'll make it a lot easier for somebody who wants to help, but doesn't totally understand the historical context, to actually be helpful, without inadvertently making things worse.

right now, if some dev looks for "obxd source code," this is what they find: https://github.com/2DaT/Obxd

any idea if this is the right basis or not?
Makin' Music Great Again 8)

Post Reply

Return to “Instruments”