OB-Xf by Surge Synth Team

[EvilDragon]

OB-Xf internal patch storage works as a "live bank". All patches are always saved automatically on any tweak you do, without any explicit action, then stored in plugin state (your DAW project). I'm not sure how is this confusing ^_^;

If you want to have patches on your disk, you use the export patch/bank options (and then import option to load those files). So, saving an FXB is "making your own bank", but it's not yet directly browsable from within the plugin. You have 256 patches in a bank stored per plugin instance, and if you need a different bank, you just load a different FXB (once you have one created, of course).

An improved patch browser is going to be a topic for 1.x, it's not in scope for 1.0 release.

[muki]

unfortunately the AudioUnit crashes auval in logic 10.5.1 under mojave
crashreports available

[baconpaul]

whats the number of mojave?

We have a minimum os requirement of macOS 10.15

(edit) mojave is 10.14. Yeah we build 10.15 and higher.

I'll try a 10.14 build and if it checks out will update back here.

[baconpaul]

Yeah there's things which make 10.13 and 10.14 both hard, but the thing which was giving me trouble on 10.14 got fixed in a change i did earlier to day for linux, so 10.14 builds fine.

I just pushed the change. New build in about 30-45 minutes should work on mojave. Edit: 10.14 nightly is now up.

Can't guarantee that our future projects will be as amenable though. 10.14 is getting pretty long in the tooth and its getting trickier to target it if you want to use new features of the languages and tooling.

[Funkybot's Evil Twin]

Loving this so far. Vector skin is a nice touch and well done. Is it ok to report issues here?

1. MIDI Learn doesn't work on the noise color button.

2. When it comes to OSC 1 & 2's primary frequency, a MIDI value of 64 results in a tuning of +0.019 semitones. Expected: 64= 0.0 semitones.

3. In Reaper, Windows, typing in a preset name with a space triggers the spacebar action assignment. I know the easiest solution is "Send all keystrokes to plugin" or remember to shift+spacebar, but would be nice if that could "just work" out of the box.

[Funkybot's Evil Twin]

OB-Xf internal patch storage works as a "live bank". All patches are always saved automatically on any tweak you do, without any explicit action, then stored in plugin state (your DAW project). I'm not sure how is this confusing ^_^;

First off, thanks to you and Paul and the rest of the Surge team.

I wouldn't say it's confusing, but if you're a tweaker, you may load a patch, play around with it some, then decide "nah, that sucked, I made it worse", and go to the next patch. But then you return to the first patch, and suddenly "nah, that sucked, I made it worse" has unexpectedly overwritten what might've been a fine patch in another context. I think there's a reason just about every synth makes you actively save.

I'd personally really like a Save button. And a copy/paste patch menu item.

[EvilDragon]

1. MIDI Learn doesn't work on the noise color button.

Confirmed, will be fixed. EDIT: Is now fixed, next nightly will have it working!

2. When it comes to OSC 1 & 2's primary frequency, a MIDI value of 64 results in a tuning of +0.019 semitones. Expected: 64= 0.0 semitones.

I'm not sure we can fix this easily or at all. MIDI learned parameters are simply linearly scaled across the parameter range, for all parameters...

3. In Reaper, Windows, typing in a preset name with a space triggers the spacebar action assignment. I know the easiest solution is "Send all keystrokes to plugin" or remember to shift+spacebar, but would be nice if that could "just work" out of the box.

This is a Reaper peculiarity.... don't think we can do anything about it from JUCE. But you can use Shift+Space and it will work.

[EvilDragon]

And a copy/paste patch menu item.

This does exist in the big red menu (which you also get if you right click on the UI background), as you can see in this post.

[Funkybot's Evil Twin]

And a copy/paste patch menu item.

This does exist in the big red menu (which you also get if you right click on the UI background), as you can see in this post.

Thanks, that's handy! My apologies for missing it. Was skimming the thread at work then posted that request hours later.

Any thoughts on turning off Autosave and adding a Save button? The other downside to Autosaving is people will accidentally overwrite any factory patches you eventually ship which will suck for users and patch creators both.

[Funkybot's Evil Twin]

I'm not sure we can fix this easily or at all. MIDI learned parameters are simply linearly scaled across the parameter range, for all parameters...

I was thinking special case logic for those two params that says basically, "IF MIDI control value = 64, set Semitones to 0.00, ELSE [existing logic]". Might be more complex than that though. Things are almost never that easy.

But if the main concern was a jump in the params and it not being scaled evenly, that would be preferred to current state and only needed for those two controls.

[EvilDragon]

Any thoughts on turning off Autosave and adding a Save button? The other downside to Autosaving is people will accidentally overwrite any factory patches you eventually ship which will suck for users and patch creators both.

It's not super straightforward, but we acknowledge this can be an issue for some users. The patch browser needs to be designed first and that will take some time, so our thinking is that initial release of OB-Xf will be fine as it is (since basically this is also how OB-Xd worked too all these years), and then 1.1 will improve the workflow.

One idea we have been tossing about is to have an extra buffer bank which is what you actually import patches/banks into, while the current "live" bank is your temporary edit bank. As soon as you edit a parameter the preset name gets an asterisk, if you change to another patch those edits will be gone. Then we'd need to modify the UI somewhat to add a Save button, etc. etc.

[muki]

I just pushed the change. New build in about 30-45 minutes should work on mojave. Edit: 10.14 nightly is now up.

YES !!!!
super THANKS!
that was fast

working great now (in logic and under mojave)

thank you!

[baconpaul]

I'm not sure we can fix this easily or at all. MIDI learned parameters are simply linearly scaled across the parameter range, for all parameters...

I was thinking special case logic for those two params that says basically, "IF MIDI control value = 64, set Semitones to 0.00, ELSE [existing logic]". Might be more complex than that though. Things are almost never that easy.

yeah we were discussing instead a special case of `if bipolar then value = clamp((cc-1)/126,0.1)` so basically we make cc value 0 and 1 have the same value so you otherwise get exact center.

we've not fully decided yet but my guess is we'll do something like that either for all bipolar controls or at least for the pitch ones.

[Funkybot's Evil Twin]

I'm not sure we can fix this easily or at all. MIDI learned parameters are simply linearly scaled across the parameter range, for all parameters...

I was thinking special case logic for those two params that says basically, "IF MIDI control value = 64, set Semitones to 0.00, ELSE [existing logic]". Might be more complex than that though. Things are almost never that easy.

yeah we were discussing instead a special case of `if bipolar then value = clamp((cc-1)/126,0.1)` so basically we make cc value 0 and 1 have the same value so you otherwise get exact center.

we've not fully decided yet but my guess is we'll do something like that either for all bipolar controls or at least for the pitch ones.

Awesome. Thanks!

[Funkybot's Evil Twin]

Any thoughts on turning off Autosave and adding a Save button? The other downside to Autosaving is people will accidentally overwrite any factory patches you eventually ship which will suck for users and patch creators both.

It's not super straightforward, but we acknowledge this can be an issue for some users. The patch browser needs to be designed first and that will take some time, so our thinking is that initial release of OB-Xf will be fine as it is (since basically this is also how OB-Xd worked too all these years), and then 1.1 will improve the workflow.

One idea we have been tossing about is to have an extra buffer bank which is what you actually import patches/banks into, while the current "live" bank is your temporary edit bank. As soon as you edit a parameter the preset name gets an asterisk, if you change to another patch those edits will be gone. Then we'd need to modify the UI somewhat to add a Save button, etc. etc.

Sounds good. Thanks for listening!