OB-Xf by Surge Synth Team

[digitalboytn]

How many forks does one need

Normally onë knife and one fork,plus a spoon if something wet is on the menu...

Two chopsticks if you prefer - because one chopstick just doesn't cut it...

Woah...that's punny...

If you're eating out,the fork and the spoon are for getting the food into your mouth and the knife is for protection...

Just in case

[skippy63]

As far as sonic differences, filters and oscillators sound identical from my tests. There's a detailed list of all the changes in post #1, so yes in a few places you can expect some differences (i.e. Crossmod knobs has 2x the range compared to OB-Xd, noise knob in the mixer has changed scaling to match up with scaling of osc 1/2 volume knobs, LFO has a higher maximum rate, etc.). This was a conscious choice to both allow some more "room to play with", and in case of mixer knob scalings, to ensure consistency.

I understand it would be possible to import presets banks from the OB-Xd with a routine « scaling » these different parameters. It would be so nice!

Even if I consider the OB-Xf as a fine synth for creating presets, I would like to get this function.

[EvilDragon]

It is not going to happen for 1.0 release, it needs a thorough phase of R&D.

In any case, it's not as if it's difficult to make patches for this synth, it doesn't have too many parameters.

[baconpaul]

So we've been a bit busy, but today i pushed the last code fix to an open 1.0 issue, so the nightly now should be code complete for a 1.0 release shortly.

Still some documentation and so on work to do, but the beta would be the 1.0 with just a tag, unless someone finds something next week or two.

Thanks!

[Funkybot's Evil Twin]

Congrats team! Milestone achieved!

[FrettedSynth]

Thanks to all involved

[el-bo (formerly ebow)]

Has the topic of FX been dealt with i.e Any chance of an advanced page that contained a handful of the basics?

[Vortifex]

Has the topic of FX been dealt with i.e Any chance of an advanced page that contained a handful of the basics?

Yes, and unless things have changed, the answer is almost certainly no:

Anyway, obxf 1.0 won't have effects. And I'd be surprised if we did the work to add them. But we do have the surge effects factored as a library mostly (although haven't factored the chorus yet!) which is how we get them shared across surge and short circuit. So maybe one day a volunteer would do the integration. Not impossible in the future but not on the roadmap for this project which is really a sort of constrained push to make the open source version of the synth runnable and bug fixed.

My vote as one of developers here goes to "no effects on this one". I want to keep it simple and, for the lack of better term, pure. Juno chorus was a necessity because that thing had just one oscillator. This one doesn't.

[el-bo (formerly ebow)]

Has the topic of FX been dealt with i.e Any chance of an advanced page that contained a handful of the basics?

Yes, and unless things have changed, the answer is almost certainly no:

Anyway, obxf 1.0 won't have effects. And I'd be surprised if we did the work to add them. But we do have the surge effects factored as a library mostly (although haven't factored the chorus yet!) which is how we get them shared across surge and short circuit. So maybe one day a volunteer would do the integration. Not impossible in the future but not on the roadmap for this project which is really a sort of constrained push to make the open source version of the synth runnable and bug fixed.

My vote as one of developers here goes to "no effects on this one". I want to keep it simple and, for the lack of better term, pure. Juno chorus was a necessity because that thing had just one oscillator. This one doesn't.

Thanks! Never really understand the purity angle, personally. Even less so, if any non-pure, elements can so easily be hidden behind an extra or 'advanced' tab.
And I'd even understand if it was a case of the company not having time to code their own FX from scratch. But the team have FX, by the ton

[EvilDragon]

It's practically a team-wide consensus on that particular matter.

[Echoes in the Attic]

Has the topic of FX been dealt with i.e Any chance of an advanced page that contained a handful of the basics?

Yes, and unless things have changed, the answer is almost certainly no:

Anyway, obxf 1.0 won't have effects. And I'd be surprised if we did the work to add them. But we do have the surge effects factored as a library mostly (although haven't factored the chorus yet!) which is how we get them shared across surge and short circuit. So maybe one day a volunteer would do the integration. Not impossible in the future but not on the roadmap for this project which is really a sort of constrained push to make the open source version of the synth runnable and bug fixed.

My vote as one of developers here goes to "no effects on this one". I want to keep it simple and, for the lack of better term, pure. Juno chorus was a necessity because that thing had just one oscillator. This one doesn't.

Thanks! Never really understand the purity angle, personally. Even less so, if any non-pure, elements can so easily be hidden behind an extra or 'advanced' tab.
And I'd even understand if it was a case of the company not having time to code their own FX from scratch. But the team have FX, by the ton

Could just load Surge FX plugin after it?

[ampetrosillo]

So we've been a bit busy, but today i pushed the last code fix to an open 1.0 issue, so the nightly now should be code complete for a 1.0 release shortly.

Still some documentation and so on work to do, but the beta would be the 1.0 with just a tag, unless someone finds something next week or two.

Thanks!

'tis called a Release Candidate.

[el-bo (formerly ebow)]

Has the topic of FX been dealt with i.e Any chance of an advanced page that contained a handful of the basics?

Yes, and unless things have changed, the answer is almost certainly no:

Anyway, obxf 1.0 won't have effects. And I'd be surprised if we did the work to add them. But we do have the surge effects factored as a library mostly (although haven't factored the chorus yet!) which is how we get them shared across surge and short circuit. So maybe one day a volunteer would do the integration. Not impossible in the future but not on the roadmap for this project which is really a sort of constrained push to make the open source version of the synth runnable and bug fixed.

My vote as one of developers here goes to "no effects on this one". I want to keep it simple and, for the lack of better term, pure. Juno chorus was a necessity because that thing had just one oscillator. This one doesn't.

Thanks! Never really understand the purity angle, personally. Even less so, if any non-pure, elements can so easily be hidden behind an extra or 'advanced' tab.
And I'd even understand if it was a case of the company not having time to code their own FX from scratch. But the team have FX, by the ton

Could just load Surge FX plugin after it?

I guess that solves the biggest of the potential downsides. Although, having the possibility of modulating parameters from the synth would be lost (Not that it's a modulation beast anyway, i guess).

[EvilDragon]

Yeah that is squarely in the "this is not that sort of synth" territory.

[el-bo (formerly ebow)]

Yeah that is squarely in the "this is not that sort of synth" territory.

A synth that won't be used with effects is certainly new territory for me. But it might catch on