I was wondering if anyone else had this issue. I've had OP-X and OP-X II (both 32bit VSTs) for a while. When I moved to X3, I made the leap from 32bit to x64 in Sonar. Now, I have other 32bit VSTs (like VB3) that I have no issue with, but for some reason, whenever I add one of these oberheim synths, any changes I make (whether it's picking a preset or twiddling a knob) isn't retained after a save/close.
 
I've tried this both in new projects and in existing projects from X2 that already had them added. I've gotten in the habit of making a manual save of any setting changes into a new bank and then referencing that bank name in the track name (so I can manually recall the sound between sessions), but it's a bit of a PITA.
 
Has anyone else encountered this issue?

I recently found out OPX-II Pro does this in BrainSpawn Forte too but honestly I hadn't noticed yet. There is a fix for Forte that requires the manual editing of some text file, perhaps there is a similar fix for Sonar? Googling Forte OP-X Pro should get you there quickly.

ok - thanks. I did some searching and found that the "fix" was to modify some xml data in files inside Forte itself, not OP-X. I then did some digging in my VST directory and did things like verify full perms on the directory for my user. Also, running Sonar as admin (I don't usually) made no difference.
 
 

Sorry for sending you on a wild goose chase then :(
I guess OPX is non-standard in this respect at least. I'll try fidgeting with JBridge settings.

no worries - any little bit helps. I did some searching on SonicProject's website and came across some things related to Vista. I'm going to remove and reinstall the plugs tonight and set Sonar to run as admin full time (while the IT guy inside me cringes) and see if the behavior changes.
 
I'll also do some comparisons to VB3 (which also uses Jbridge, but seems to work) and see if I can correlate any differences. The way I understand it, both were written using synthedit, so I might be able to find something.

locating your vst folder outside the program files hive can resolve permission issues, if that's what this is. don't some synthedit plugs write ".sem" files, or something?

also if it's 32 bit it's the bitbridge process that needs admin rights?

lawp
locating your vst folder outside the program files hive can resolve permission issues, if that's what this is. don't some synthedit plugs write ".sem" files, or something?

all of my plugins are in one of these 4 folders:
c:\Program Files\VSTPlugins
c:\Program Files (x86)\VSTPlugins (Where the OP-X files are)
c:\Program Files\Cakewalk\VSTPlugins
c:\Program Files (x86)\Cakewalk\VSTPlugins
 
I verified NTFS perms for everything (it all is using top down inheritance and my user has privileges)
 
I do recall seeing some *.sem files in an OP-X subdirectory where the DLL is. I will spot check those tonight to make absolutely sure that NTFS perms are inheriting down properly.
 
 

lawp
also if it's 32 bit it's the bitbridge process that needs admin rights?

It's possible - although I'm not aware of anyone (on this forum at least) mentioning having to manually set the execution permissions on that. The way I understand how the "run as administrator" function operates in Windows is that when the root PID executes as administrator, all spawned child processes execute at that same permissions level.
 
Tonight I will run some tests to verify that the bitbridge processes are running with the proper privileges when I execute Sonar as administrator
(pasting this link for reference later)
http://www.sevenforums.co...istrator-elevated.html

ok, I tried the following
 
1. removed both OP-X and OP-X II (and saved/removed the leftover program directory.
2. Reinstalled both as administrator
3. Manually gave "full control" NTFS permissions to the local "users" group on my PC
4. changed the Sonar shortcut to run as administrator
5. Launched Sonar and opened my test project.
6. Set one of my OP-X instances to the non-default patch.
7. Opened up task manager and verified that Sonar.exe and all bitbridge.exe instances are running with elevated permissions.
8. Saved my test project, closed and reopened Sonar.
9. Reopened my test project, all OP-X patches are back to the default.
 
This sucks. I think I'm going to reach out to SonicProjects and Cakewalk to see what they say.