KVR Audio

KTlin · Post by **KTlin** » Mon Mar 30, 2015 11:44 am

Hi guys

This is very annoying. Yesterday I started a new project in Ableton and I worked for several hours programing some patches in Omnisphere. I had 4 patches loaded in a Multi in one instance of Omnisphere.
Today, when I opened the project, all the patches (parts) are empty (default settings)

Only the settings for the Multi were kept (level, pan, aux, midi channel and output channel for every part).

WTF happened?

zvenx · Post by **zvenx** » Mon Mar 30, 2015 11:56 am

This has happened to me in the past with Omnisphere and RMX....Support will tell you what to do to ensure it doesn't happen again.
It hasnt' happened again for me, but it certainly encouraged me to save each patch and multi I use for omnisphere, both within omnisphere and within Cubendo.
Sorry to hear.

rsp

wagtunes · Post by **wagtunes** » Mon Mar 30, 2015 11:58 am

KTlin wrote:Hi guys

This is very annoying. Yesterday I started a new project in Ableton and I worked for several hours programing some patches in Omnisphere. I had 4 patches loaded in a Multi in one instance of Omnisphere.
Today, when I opened the project, all the patches (parts) are empty (default settings)
Only the settings for the Multi were kept (level, pan, aux, midi channel and output channel for every part).

WTF happened?

Did you actually save the patches? If you don't save the patches they won't save with the multi. If you did save the individual patches then they should be in the patch portion of your browser. All you then have to do is find them and load them into your multi.

zvenx · Post by **zvenx** » Mon Mar 30, 2015 12:08 pm

But every DAW afaik should save the parameters of each plugin, whether you save the patch or not within the plugin.
rsp

KTlin · Post by **KTlin** » Mon Mar 30, 2015 12:15 pm

wagtunes wrote: Did you actually save the patches? If you don't save the patches they won't save with the multi. If you did save the individual patches then they should be in the patch portion of your browser. All you then have to do is find them and load them into your multi.

No, I didn't. But as zvenx said, I was sure all the settings in the patches will be saved with the project, even if I didn't save each patch.

wagtunes · Post by **wagtunes** » Mon Mar 30, 2015 12:20 pm

KTlin wrote:
wagtunes wrote: Did you actually save the patches? If you don't save the patches they won't save with the multi. If you did save the individual patches then they should be in the patch portion of your browser. All you then have to do is find them and load them into your multi.
No, I didn't. But as zvenx said, I was sure all the settings in the patches will be saved with the project, even if I didn't save each patch.

Well, I'm just speaking from experience. If I bring up a multi and say load up the first 4 slots with "patches" but don't save the patches upon saving the multi, when I bring the multi back up, the "patches" will be gone and all set back to default.

Always save ALL your work. I learned this lesson the hard way many years ago.

zvenx · Post by **zvenx** » Mon Mar 30, 2015 12:31 pm

wagtunes wrote:
KTlin wrote:
wagtunes wrote: Did you actually save the patches? If you don't save the patches they won't save with the multi. If you did save the individual patches then they should be in the patch portion of your browser. All you then have to do is find them and load them into your multi.
No, I didn't. But as zvenx said, I was sure all the settings in the patches will be saved with the project, even if I didn't save each patch.
Well, I'm just speaking from experience. If I bring up a multi and say load up the first 4 slots with "patches" but don't save the patches upon saving the multi, when I bring the multi back up, the "patches" will be gone and all set back to default.

Always save ALL your work. I learned this lesson the hard way many years ago.

I also agree this is a valuable work ethic, that I too learned the hard way.

Although my first response which spoke of this happening to me, was using saved patches....
fortunately I always name my track name after my presets, so I was able to recreate.
rsp

KTlin · Post by **KTlin** » Mon Mar 30, 2015 1:21 pm

Thanks for your help, guys!

This seems to be an issue only with Omnisphere. When I use Halion I never save patches or Multis and when I reopen the project, all the settings are there.

Passing Bye · Post by **Passing Bye** » Mon Mar 30, 2015 1:34 pm

I heard this things happening on Trilian too for single patches, so you must save the patch if you want to have it again and reload every time you open that project....

KTlin · Post by **KTlin** » Mon Mar 30, 2015 2:01 pm

Passing Bye wrote:I heard this things happening on Trilian too for single patches, so you must save the patch if you want to have it again and reload every time you open that project....

indeed

And here's some more. I just created another project, like the one I did yesterday, just to test this issue, and although I didn't save the patches and the Multi, this time, when I reopened the project everything was there.

So it looks like there's some sort of bug here, and only sometimes the settings for the patches and Multi in Omnisphere don't get saved with the project. That explains why I didn't get this weird issue before, and why I was so sure I don't have to save manually every patch and the Multi.

2ZrgE · Post by **2ZrgE** » Mon Mar 30, 2015 3:05 pm

KTlin wrote:Thanks for your help, guys!

This seems to be an issue only with Omnisphere. When I use Halion I never save patches or Multis and when I reopen the project, all the settings are there.

Imagine you have to do that for all your VSTs - ridiculous..must be a bug indeed.

zvenx · Post by **zvenx** » Mon Mar 30, 2015 3:09 pm

Btw are you on 32 or 64 bit OS and DAW?
I seem to think it is memory related.
Mine was anyway.

there is a file support will ask you to remove and let omnisphere rebuild.
Since I did that it hasnt' happened again and that might have been four or five years ago. Back then I was on Windows XP 32 bit..
But still messed up when it happens the first time.
rsp

KTlin · Post by **KTlin** » Mon Mar 30, 2015 3:24 pm

zvenx wrote:Btw are you on 32 or 64 bit OS and DAW?
....
there is a file support will ask you to remove and let omnisphere rebuild.
Since I did that it hasnt' happened again and that might have been four or five years ago.

I'm running Ableton Live 64bit on Windows 7 64bit.

How did you do that rebuild process for Omnisphere? Did you just uninstall and reinstall it?

Tnx

zvenx · Post by **zvenx** » Mon Mar 30, 2015 9:58 pm

nope.
just one file that has to be deleted and omnisphere builds it back next time.
ask support.
rsp

musicdoc · Post by **musicdoc** » Tue Mar 31, 2015 6:41 am

I don't use Omnisphere but in Stylus 32bit, I used to have situations where if a bit too much RAM was being used in the project, when reloading the project individual sounds/parts would all be missing from the multi. Highly aggravating. I too learned with that with spectrasonics you have to save your multi's/patches.

It's not this way with most other manufactures -that I use anyways.

Omnisphere - all work lost