for as much as this software costs, it should save all the edits to the synth with theKTlin wrote: This seems to be an issue only with Omnisphere..
project. freeware synths do this ffs!
for as much as this software costs, it should save all the edits to the synth with theKTlin wrote: This seems to be an issue only with Omnisphere..
Indeed. Seems like it usually does save all the edits with the project but it has some kind of bug and sometimes it doesn't save them. The extremely nasty part is that this bug seems to be completely unpredictable, so you never know when this shit will happen. As musicdoc said earlier, it looks like Stylus also has this bug.layzer wrote: for as much as this software costs, it should save all the edits to the synth with the
project. freeware synths do this ffs!
I'm sorry for the loss of your work, but I think you're overstating what musicdoc said. Neither RMX or Omnisphere has this "bug", and both are host dependent.KTlin wrote:Indeed. Seems like it usually does save all the edits with the project but it has some kind of bug and sometimes it doesn't save them. The extremely nasty part is that this bug seems to be completely unpredictable, so you never know when this shit will happen. As musicdoc said earlier, it looks like Stylus also has this bug.layzer wrote: for as much as this software costs, it should save all the edits to the synth with the
project. freeware synths do this ffs!
That's a great question. Did anyone contact Spectrasonics support? If I'm reading Zvenx's post right, it sounds like deleting a file may cause the host to load the session properly and to contact support for details. Could be that something is getting corrupted and the issue can be resolved.mod.eater wrote:So what's causing it and what's the fix?
Years later I don't remember which file I had to remove... my guess it was either an authorisation or shortcut file....but spectrasonics made me do it and I have never had the issue since.Funkybot's Evil Twin wrote:That's a great question. Did anyone contact Spectrasonics support? If I'm reading Zvenx's post right, it sounds like deleting a file may cause the host to load the session properly and to contact support for details. Could be that something is getting corrupted and the issue can be resolved.mod.eater wrote:So what's causing it and what's the fix?
I've yet to run into this in Omnisphere (only had it a few months), but doesn't mean I never wil.
maybe it's been ironed out over three years?zvenx wrote:Years later I don't remember which file I had to remove... my guess it was either an authorisation or shortcut file....but spectrasonics made me do it and I have never had the issue since.Funkybot's Evil Twin wrote:That's a great question. Did anyone contact Spectrasonics support? If I'm reading Zvenx's post right, it sounds like deleting a file may cause the host to load the session properly and to contact support for details. Could be that something is getting corrupted and the issue can be resolved.mod.eater wrote:So what's causing it and what's the fix?
I've yet to run into this in Omnisphere (only had it a few months), but doesn't mean I never wil.
rsp
The same happened to me with SynthMaster and MuLab. I tweaked a patch in SM and later updated it (from 2.5 to 2.6). Then my patch was gone.zvenx wrote:But every DAW afaik should save the parameters of each plugin, whether you save the patch or not within the plugin.
rsp
TS-12 wrote: ↑Tue Sep 04, 2018 8:18 am Reading on the internet seems this happens to Omnisphere, stylus rmx and trillion, in all the daws, so definitely not daw related.
Spectrasonics support recommend deleting preference (.dat ? ) files after that omnisphere rebuilds the database.
(This fixes the problem temporarily for few weeks / months, but then later starts happening again. Contact support , delete preference files.. )
It's a good habit anyway, since you can back up those presets and use them in other projects/hosts.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement