Gforce Software Oberheim SEM

[Shaetano]

Not sure I was clear enough, I have no problem saving a preset in a different location, but I can't find a way to load it back into the synth from there.

Same here, but my saved presets are in the default user folder. I suspect this maybe a demo limitation and it's a very good one if so.

Yes, currently SEM and OB-E can both only read patches from their specified user patch folder. This is also the default save location. SEM and OB-E demos can save user patches, but not load them.

FYI:
Mac: ~/Library/Audio/Presets/GForce/SEM
PC: C:\Program Files\GForce\SEM\Patches\User

[Funkybot's Evil Twin]

Not sure I was clear enough, I have no problem saving a preset in a different location, but I can't find a way to load it back into the synth from there.

Same here, but my saved presets are in the default user folder. I suspect this maybe a demo limitation and it's a very good one if so.

Yes, currently SEM and OB-E can both only read patches from their specified user patch folder. This is also the default save location. SEM and OB-E demos can save user patches, but not load them.

FYI:
Mac: ~/Library/Audio/Presets/GForce/SEM
PC: C:\Program Files\GForce\SEM\Patches\User

I hate when developers ignore all good advice and reason and put patches in Program Files\ or Program Data\ on Windows.

These things should really be in Documents\

[zvenx]

Isn't ProgramData the 'right' place at least for factory banks.
But indeed there doesn't seem to be a standard so I have to play guess where the patches are for almost each different developer.
For sure though, the one place I know I dont' want them is in the plugin folders themselves.
rsp

[e@rs]

Yes, currently SEM and OB-E can both only read patches from their specified user patch folder. This is also the default save location. SEM and OB-E demos can save user patches, but not load them.

FYI:
Mac: ~/Library/Audio/Presets/GForce/SEM
PC: C:\Program Files\GForce\SEM\Patches\User

I have my SEM activated, not demo. Please consider adding either a preset loader with a browse function like the vast majority of instruments out there have, or a user folder revealer inside the synth like U-He does. I like to keep all my personal presets from all my soft synths in one location for easy transfer to another machine.

[Uncle E]

I hate when developers ignore all good advice and reason and put patches in Program Files\ or Program Data\ on Windows.

These things should really be in Documents\

It’s the worst. Once spent weeks duplicating Alesis Andromeda presets in FXpansion Cypher. Sounded absolutely incredible. Then lost it all when I reinstalled OS and didn’t back up Program Files (Documents was of course backed up).

[Funkybot's Evil Twin]

It’s the worst. Once spent weeks duplicating Alesis Andromeda presets in FXpansion Cypher. Sounded absolutely incredible. Then lost it all when I reinstalled OS and didn’t back up Program Files (Documents was of course backed up).

Yeah, similar thing happened to me. I bought my new PC, got it all setup, restored my online backup, then discovered a bunch of presets across a few products didn't carry over because devs had them in Program Files or Program Data.

[Shaetano]

I have my SEM activated, not demo. Please consider adding either a preset loader with a browse function like the vast majority of instruments out there have, or a user folder revealer inside the synth like U-He does. I like to keep all my personal presets from all my soft synths in one location for easy transfer to another machine.

Yep. I don't think it's a secret that that's coming.

[NikkiA]

I keep all my presets in a specific location, then make junctions back into the presets folder wherever the vsti stores them, with most vendors (including GForce) this works fine, since user and factory presets are usually in different folders, but bx_oberhausen just craps them all out in the same place, which means that needs a separate backup procedure (which is irritating)

[morelia]

These things should really be in Documents\

I hate everything being in documents, but yeah, options are good.

[chk071]

These things should really be in Documents\

I hate everything being in documents

... and just like users, developers have their own preferences.

I personally like to have that kind of stuff in Documents as well though. ProgramData, not so good. Program Files, bad. User files shouldn't be in Program Files.

And then there's the developers who choose to put their stuff in the VST plugin folders. I don't like that either. VST plugin folders should be for the plugins, not the user files, or factore presets.

Yesh, I think Documents is the folder to go really.

[Funkybot's Evil Twin]

These things should really be in Documents\

I hate everything being in documents

... and just like users, developers have their own preferences.

I personally like to have that kind of stuff in Documents as well though. ProgramData, not so good. Program Files, bad. User files shouldn't be in Program Files.

And then there's the developers who choose to put their stuff in the VST plugin folders. I don't like that either. VST plugin folders should be for the plugins, not the user files, or factore presets.

Yesh, I think Documents is the folder to go really.

This.

There may not be a "perfect" place on Windows for stuff like this but there's one place that's outright wrong (Program Files), one place that can fit the bill (Program Data) and might even make sense for factory content [while not being meant for user content], and one place that's meant for user created content (Documents).

If someone doesn't like any of them, well then take it up with Microsoft.

One of my favorite things about the Mac, having recently gotten my first, is that everything just has one f*cking place it goes. Plugins go in the plugins folder. App support stuff goes in the Application Support folder, Presets go in the Presets folder. It's like someone at the company actually thought about where things should go and bothered to come up with standards. Whereas Microsoft's been a hodge-podge about where files go.

[SHall1000]

Does anyone else think this topic deserves its own thread? A list of which devs put what where might be useful.

[Uncle E]

Ironically, this sub-thread needs to be put in the correct place.

[chk071]

Does anyone else think this topic deserves its own thread?

Rather a "the world keeps turning" topic for me. But, hey.

[pough]

There may not be a "perfect" place on Windows for stuff like this but there's one place that's outright wrong (Program Files), one place that can fit the bill (Program Data) and might even make sense for factory content [while not being meant for user content], and one place that's meant for user created content (Documents).

Don't forget <user>/AppData/Roaming!

IMO there are no good places for plugin presets on a PC, only a distressingly large number of bad ones. ProgramData and AppData are both hidden by default and my Documents folder is full to the anus of things that I don't really consider to be my documents.

Anyways, I like SEM. It's pretty good. I wish it didn't sometimes forget where the current preset is in the list of presets; next is sometimes 10 presets back.