Omnisphere not retaining patch info in DP9?

[Gravity Jim]

Just so this doesn't become a established fact: DP projects open with the proper Omnisphere II patches (just as it did with the original Omnisphere). No problem here.

[dix]

Just so this doesn't become a established fact: DP projects open with the proper Omnisphere II patches (just as it did with the original Omnisphere). No problem here.

Correct. Though there's a few other people here and there on this thread and the on the rest of the internet with this problem, it's largely the exception.

Spectrasonics is on it now btw. A few emails back and forth, but no solution yet. ....making things more difficult is the fact that I can no longer reproduce the problem! Files that were opening up with blank Omnisphere multis are now opening as expected even though I've taken no steps to fix the issue.

I recommend anyone else with the problem contact Spectrasonics and send them any DP docs that forget the Omnisphere patch settings.

[dix]

I finally connected with Spectrasonics they were able to fix the issue. Anyone with similar problems should definitely contact their tech support and they'll walk you through it.

[Blimpy101]

Hey there,

Know I'm arriving pretty late to the party here, but just wondering what the steps were that Spectrasonics walked you through in order to get Omni functioning normally in terms of loading multis. Appreciate any thoughts!

Thanks

[dix]

Sorry. I don't remember. You'll need to call.

[David Polich]

Because saving a patch/preset within
a plugin or VI's own GUI has always been
hit-or-miss for me, I just save patches
as AU presets within DP. It works 100% of
the time

In case anyone does not know how to do this...

Open a plugin or VI's GUI by double-clicking
on the plugin or VI's name in the insert
slot you placed it in.

Make your edits and tweaks.

Then, in the upper left hand corner of the
plugin or VI'd GUI, clickmon the drop-down
menu and select "Save Preset..". Here you
can save your work as an AU preset,with
a name you choose.

Now, your preset is saved and can always
be recalled.

[buzzsmith]

Because saving a patch/preset within
a plugin or VI's own GUI has always been
hit-or-miss for me, I just save patches
as AU presets within DP. It works 100% of
the time

In case anyone does not know how to do this...

Open a plugin or VI's GUI by double-clicking
on the plugin or VI's name in the insert
slot you placed it in.

Make your edits and tweaks.

Then, in the upper left hand corner of the
plugin or VI'd GUI, clickmon the drop-down
menu and select "Save Preset..". Here you
can save your work as an AU preset,with
a name you choose.

Now, your preset is saved and can always
be recalled.

Not exactly...'

Even with saved presets, sometimes the VI comes up with the preset name that I gave it, but no instrument(s) are loaded.

Workaround: Call up another preset and then recall up the one that you need.

Buzzy

(Recently began happening. Email sent to Spectrasonics.)

[buzzsmith]

Now, it's Stylus RMX. Create a Multi.

Save Preset.

Close project and re-open.

Preset name is in the correct place, but no patches are loaded.

I did download the newest version before I left for the gig.

I'll install tomorrow. Hopefully, this will fix it.

I've been writing down all of the patches and that helps to recreate the multi, but it's time consuming!

Buzzy




Sent from my iPhone using Tapatalk

[dix]

Same drill as Omnisphere in that case: Call Spectrasonics they'll walk you through the fix. I'm pretty sure I had to do this too when I swapped my CPU as I believe you have also done. As I recall they had me fix Stylus preemptively on the same call when I fixed Omnisphere.

[buzzsmith]

I've emailed. I'll try a phone call after I upgrade to the latest version.


Sent from my iPhone using Tapatalk

[buzzsmith]

Update:

I installed the latest version (I think) of Stylus RMX and, so far, it's retaining the presets.

I'm still a little wary, however, and will continue to write down what patches I'm loading and then saving as a Multi.

(Didn't need to call Spectrasonics...so far.)

Buzzy


Sent from my iPad using Tapatalk

[dreamuse]

Hey all,

I just hit this problem, and indeed it occurred after I got a new processor tray in my system. It's a problem of permissions, and Spectrasonics has indeed addressed it here:
https://www.spectrasonics.net/support/k ... egoryID=13

This fixed my situation with Omnisphere not storing patches.

Len

[buzzsmith]

Hey all,

I just hit this problem, and indeed it occurred after I got a new processor tray in my system. It's a problem of permissions, and Spectrasonics has indeed addressed it here:
https://www.spectrasonics.net/support/k ... egoryID=13

This fixed my situation with Omnisphere not storing patches.

Len

Well, that fits my situation as I replaced the CPU 8 or so months ago.
The link requires me to login, so I'll check that out tomorrow on the studio Mac.

I'm having the preset save issue on all 3 Spectrasonics products including Trilian and Stylus RMX.

Buzzy


Sent from my iPad using Tapatalk

[dreamuse]

Please let us know if it fixes the problem for you.

I'd love to know how changing the hardware affects the permissions. I've been surprised by how few issues I've had with upgrading the processor tray, but this is a weird one for sure.

Len

[dinobass]

This happened to me once a few days ago. Never happened before and hasn't happened since. I looked at the Spectrasonics fix and it's just a permissions issue. I checked and all my permissions are set correctly, yet I did have the disappearing patches once.

Now that I think of it, it might have happened after I did the latest security update for OS X 10.12.6. When the computer rebooted, I had to set up my Apple ID again (along with some other settings). Omnisphere patches since the update have been saving fine. I'll go check recent projects that I worked on before the security update to see if the patches are still there.

Yep, looks like older projects have lost their saved Omnisphere patches.