OB-Xf by Surge Synth Team

[EvilDragon]

I don’t know if this has been discussed but, I noticed, that after modifying a preset then saving the Project in Cubase 15 (Mac), recalling the Project presented the OBXF with its original preset… not the modified one I saved with the Project. I can’t think of a single synth I have that does this, so I’m guessing it might be a bug?

Can you copy info from about screen here?

That sounds like you may be running an older alpha version. This should no longer be an issue in the current version.

[Aloysius]

That's probably SmartScreen being a smartass, since the binary isn't signed (IIRC). You'd have to add an exception. There's no reason why it wouldn't work on W11 (it works fine on my W11 machine).

Thanks. I might try again another day. Thank you to the hard working team.

[baconpaul]

I don’t know if this has been discussed but, I noticed, that after modifying a preset then saving the Project in Cubase 15 (Mac), recalling the Project presented the OBXF with its original preset… not the modified one I saved with the Project. I can’t think of a single synth I have that does this, so I’m guessing it might be a bug?

To be sure: You are using 1.0.x (0, 1, or 2) and not an older nightly?

We did have some such bugs in november but believe we solved them all.

I don't have cubase 15 to try, though.

[Weasel-Boy]

I don’t know if this has been discussed but, I noticed, that after modifying a preset then saving the Project in Cubase 15 (Mac), recalling the Project presented the OBXF with its original preset… not the modified one I saved with the Project. I can’t think of a single synth I have that does this, so I’m guessing it might be a bug?

To be sure: You are using 1.0.x (0, 1, or 2) and not an older nightly?

We did have some such bugs in november but believe we solved them all.

I don't have cubase 15 to try, though.

Version 1.0.1

Screenshot 2026-03-26 at 12.32.53 PM.png

[4_the masses]

Not currently.

OK, thanks

[EvilDragon]

Version 1.0.1

Hmmm, peculiar.

Could you record exact steps that you make? Can you also reproduce this in some other DAW?

[baconpaul]

Is there a PDF of the user manual ? The machine I use it on is not online.

Just put together a script which generates it and its now linked from the manual online.

The script doesn't run automatically when we update the manual yet. That's a next step. But at least current manual pdf is there.

[baconpaul]

Version 1.0.1

Hmmm, peculiar.

Could you record exact steps that you make? Can you also reproduce this in some other DAW?

Also look for things like program change messages in your project perhaps?

I wonder what it could be.

[Weasel-Boy]

Version 1.0.1

Hmmm, peculiar.

Could you record exact steps that you make? Can you also reproduce this in some other DAW?

Also look for things like program change messages in your project perhaps?

I wonder what it could be.

The steps are described precisely in my first post. Modded a preset, saved, relaunched Project, preset reverted back to original pre-modded preset. No such thing as a program change in my Project. Haven't used that one since the Cubase Atari days.

No other DAW. Just Cubase.

[EvilDragon]

Cannot confirm in Reaper, FL Studio 25, Studio One 7, Bitwig 6, Live 12.


Any other Cubase users here to corroborate or refute?

[felis]

Cannot confirm in Reaper, FL Studio 25, Studio One 7, Bitwig 6, Live 12.


Any other Cubase users here to corroborate or refute?

Just tried it. No problem here with Cubase 14 Pro on Win. 11.
Just added pulse to the saws on startup, recorded a couple notes, saved the project,
re-opened it and the pulse osc.'s were still on.

[EvilDragon]

Try loading any of the factory patches then modify them, tho?

[Weasel-Boy]

Try loading any of the factory patches then modify them, tho?

First things first: I am on an M1 Macbook Pro. Cubase is booted under Rosetta, because I still have some critical plug-ins that are still not silicon compliant. The OS is 26.4. The latest version of Cubase 15 is running.

I started with a factory preset called 016 Faxi Slap. I recalled it by simply pressing the "Next" button after launching v1.0.1 until it landed on that one.

I modified some parameters, then, just to make sure I could recall it again, I saved the modded version as a Cubase VST preset. Nothing saved internally to the OBXF.
I quit the program and relaunched, Faxi Slap showed up but sporting it's original factory settings. However, this time I could get back my edit by loading the VST preset I saved in Cubase. And before someone asks: it doesn't matter if I saved a preset in Cubase or not.

I can repeat this over and over. There's nothing else I can do or say that's going to change the results I'm getting. I reported it...and that's the best I can do.

[baconpaul]

Hmm so you are in Rosetta.

Let me think a bit but maybe I can make a debug log enabled build for you which would help.

Tough to figure out how to debug this.

If any other Cubase 15 Mac users are here would certainly appreciate a second test though

[Weasel-Boy]

Screenshot 2026-03-26 at 4.15.39 PM.png

My first guess is that there is some sort of conflict going on because your entire preset list shows up in the Cubase preset pulldown as well as OBXF's folderized internal preset list. If I save the modded version as a VST Preset and give it a new name, That name doesn't show up in the Cubase Preset name view of the recalled Project. Faxi Slap just stays there. I've discovered that by loading in my mod (with name change) the VST name remains: Faxi Slap, and when I switch presets up or down by one and return to Faxi Slap. the original is loaded. It doesn't have a clue I loaded a new preset into that slot. It appears when I reload the Project, OBXF loads the original Preset list and ignores the mods made to that slot (016) slot position.

And for the record: Cubase 14 on Win 11 and Cubase 15 on Mac are two different animals.
I don't think this is going to turn out to be a Rosetta issue.