I think this is the safest solution for now Even thou now I have 15+ Omnisphere instrument tracks. Also Bounce into audio track for back up. Name the instrument track with the patch name. So from now on I use separate instance of Omnisphere for every patch. Ot delete all that and reinstall Omnisphere) dat files and zmap file again and restart Omnisphere. I hope to be able to help some with this and ask for your indulgence for the original posters that I publish here! Thank You! There were and are no timebombs in Omnisphere. Maybe vkDanilov has forget some time bombs?Ĭlick to expand.I've been using Omnisphere since it came out and have never had any problems, it always worked and timenbombs is more of a rumor. Before that, my Reaper freezes 2 seconds + cursor timer. But it seems there is issue with omnisphere patchs which are changed when I work on my DAW. Until now, no issue with the preset recall when I open a project with the vkDanilov version. A different hacking method is used here, so there are no time bombs and multis are saved. Omnisphere has long been able to detect R2R authorization. "Our comrade vkDanilov clarifies that R2R keygen was not used at all. When SEPECTROASONIC tried to contact him to solve the problem, the type disappeared from the traffic.
It's a myth created by a liar who made believe that he was a legit use while it was not the case. There is no legit omnisphere user who has this issue. Why not the same protection with Omisphere? I have to remind it, but the preset not recalled is used like time bomb with other plugs (for exemple: randomly with Imposcar 2 or always with Chiptune). Lots of people say that is not a time bomb, but how to explain that issue not happens with the vkDanilov omnisphere version? There are hundreds of complaints on the net. The time bomb happens even when Omnisphere is authorized.Īnd i'm not alone to having this issue. This version has exactly the same issue than their previous releases: the same time bomb with presets which are not recalled when we open a project.