Obxd synthesizer

[Kriminal]

My window of spare time has passed, so cant do the gui till after xmas.

Im sure you can find another kind chap to help.

[2DaT]

Edit: Speaking of mono mode, I would have one suggestion. Legato playing doesn't work as it's kinda supposed to. When you hold one key and then press another key and then release it, the holding note shouldn't get cut off. But the perfect implementation of mono mode would be having legato like that and "retrigger" mode when the envelopes get retriggered. In plain legato mode they don't get retriggered. It is also preferable to have a choice which envelopes get retriggered.

Analog-like voice allocation is planned, aswell as different legato modes

Next update i am going to create a gui prototype.It will take some - about 2 weeks.Nice looking visuals can be added later with ease.

[Andywanders]

New version, folks.

Congratulations 2Dat, that's much better than the last one I tried.

Good job

[Rah]

Sounds boss, looking forward to a GUI version.

[sinkmusic]

2Dat, did you consider making an open call for a GUI designer on the KVR developer forum, or on the Reaper forum?

[PAK]

I am really satisfied soundwise, what do you think?:?:

The reason some called things "lifeless" was likely because of not copying the OBX's voice card structure. Although you've added a global filter/env detune, which helps, it's still limited in comparison to OPX, never mind Arturia SEM V's individual control of voices. I don't think global controls suffice if the aim is to provide an OBX emulation.

On Sonic Projects OP-X, even with its present filters (which would benefit from ZDF methods), if you turn up the res and listen to some longer envelope releases, it's places like this where OP-X has had a lot of tweaks and sounds very musical in terms of the harmonics produced. I'd even call it exemplary in this regard. This plugin seems to behave more linear (lifeless? ) by comparison, even with all the detunes maxed.

Assuming you could improve things like that, there's also env "punch", phase behaviours, and the lack of low-end compared to the hardware - which are all things Monark went some way towards addressing for the Mini, but are differences which seem common to many synths and their emulation attempts. To me these things are as important, if not often more important, than ZDF filters.

Just as a plugin, and not OBX related, what's there sounds good, and the price is right. It should be a popular synth, even as it is, if you add a GUI.

[2DaT]

I am really satisfied soundwise, what do you think?:?:

The reason some called things "lifeless" was likely because of not copying the OBX's voice card structure. Although you've added a global filter/env detune, which helps, it's still limited in comparison to OPX, never mind Arturia SEM V's individual control of voices. I don't think global controls suffice if the aim is to provide an OBX emulation.

...
Just as a plugin, and not OBX related, what's there sounds good, and the price is right. It should be a popular synth, even as it is, if you add a GUI.

Thanks for try

In digital world there is no "copying" analog, but only "approximating"
To be honest - i specially removed per-voice knobs to reduce number of parameters.

About the filters and overall audio path: Of course obxd sounds nothing like an OP-X , but there is nothing bad. Obxd is specially designed to sound bright in high frequencies. Resonance cap on obxd is significantly higher than on op-x, also resonance on obxd have more sensitive scale in upper region.




P.S The filter now is a bit overtweaked after last update ( too lound on high resonance). Also i found one bug that causes unpleasant clicking noise in some situations.

[PAK]

digital world there is no "copying" analog, but only "approximating"

The word "copying" doesn't necessarily mean to "clone" or "duplicate". It only infers something is not the original. So its usage is appropriate in these contexts, and its meaning can be used just like words such as "mimic" or "mime".

To be honest - i specially removed per-voice knobs to reduce number of parameters.

There's already about, what, (quickly checks) 60 things there? To be on a similar level, to OPX, would take another 18 assuming a 6 voice structure. Most hardware controllers already aren't up to the job of mapping 60 things, and another 18 is no big deal to the ones which are. Most people are too lazy to map anything more than basic ADSR/filter controls to hardware anyway

On the software side avoiding a cluttered GUI means adding a 2nd page to go "under the hood". Some software synths suffer from too much emphasis on keeping the main controls exposed at all costs, especially when those "calibration" settings would usually be used on a per preset basis, rather than used as realtime performance controls. I understand why you'd want to simplify, but I think the trade off is far too big for a synth like the OBX..

Obxd is specially designed to sound bright in high frequencies. Resonance cap on obxd is significantly higher than on op-x, also resonance on obxd have more sensitive scale in upper region

Obxd is much brighter, and that makes a big difference for open filter sounds (Jump! ). But people judge filters on more than just that. The way OP-X decays the voices, and how the harmonics behave, can be very musical.. it's not just about ZDF

[layzer]

New version, folks.
Filter_warm switch is internal oversampling which can be used to produce bright sounds even at low sample rates.
Filter drive can be used to add a bit of harmonics to resonance .
Oscillator pitch quantization now switchable.
Massive code optimizations - up to 2x performance boost on my machine.

I think its time to do a gui. I am really satisfied soundwise, what do you think?:?:

https://dl.dropboxusercontent.com/s/fhw ... y/Obxd.zip

i hope the gui version doesnt crash EXT2 on winxp sp3 like the current version does

[Debutante]

If you would be so kind, it's sort of standard fare in topics like this to have the latest version on page 1. I'm not sure what one I have because I took it from a link within a quote - nobody really wants to read through the entire thread just to find a single link

all the same ... I really like this synth soundwise, and the panning, in this giu-less whatever version is a fabulous implement - no manual - OK, but some release notes would be nice... preferably on page 1 Very high CPU usage on my AMD X4 955 - just starting the plugin up is %30. The dll is dated Nov 7. 08:23

[DuX]

You have the last version Debutante, the same I'm using. It's odd that it uses 30% of your CPU as here on my Phenom II 965 [@3.6GHz] it uses only 5.8% with the default patch in Reaper without the "anticipative FX processing".

But what I'm worried about is that I noticed that presets don't work any more. That means that the automation shouldn't work, either... let me check something.

Edit: weird, automation is working but when I save and load a preset, or a project, all I get is all parameters at zero. Even the "reset to factory default" doesn't work unless I restart the plugin.

Yap, I tried to load a project with Obxd and all I get is silence from it. Doesn't save presets. Something got broken.

[Mutant]

Also if i spawn a second instance in REAPER, it gives no sound.

A feature request: CC64 MIDI Sustain - make it work please.

[2DaT]

Also if i spawn a second instance in REAPER, it gives no sound.

A feature request: CC64 MIDI Sustain - make it work please.

Do you really need this? On a synth?
Well i tried 2 instances of obxd and they work together.

Currently obxd do not have proper program system and i wonder why it worked before

[DuX]

It worked in Reaper because Reaper has its own preset system that works through parameter automation, not through FXP/FXB VST preset system. That's why I am puzzled that it doesn't work any more since the automation works, and that's why I said something must be broken.

How can possibly parameter automation work but recalling the parameter automation presets doesn't? Maybe sending more parameters simultaneously breaks Obxd somehow?

It must be something related to parameter automation. Reaper just stores the parameter automation values and then send them to the plugin when you load a new preset. If I'm not mistaken.

Since you're using Reaper, you could make a preset and then look under "User Presets" folder within the Reaper folder. You'll find Obxd.ini there and you can examine what's being send to the plugin and why it doesn't work. What puzzles me the most is that even "reset to factory defaults" doesn't work, but it works [you get the default preset, not all parameters at 0] when you reload the plugin.

[Mutant]

A feature request: CC64 MIDI Sustain - make it work please.

Do you really need this? On a synth?

How i usually program synths:

Toggle CC64, hit a key and let go, tweak knobs and buttons with 2 hands until i get the timbre i want, tweak LFOs and envelopes.

Without a working MIDI sustain i would have to put something heavy on the key for the synth to keep giving me the sound LOL...

And almost ALL good VSTi synths support that CC + MIDI program change message.