I just updated from 1.0.2d to 1.0.3f on a Mac Pro Intel dual core 2.66GHz/4GB (Tiger 10.4.11) running the latest patches in Logic Pro 7.2.
Prior to the update, my experience of Omnisphere was that it was a flawless instrument - perfect sound quality, and no issues. ARP sequences blended well from note to note and I discovered no problematic patches (no noise, hiss, odd filter behavior, etc.). Working with this instrument has been a dream come true.
I feel much less comfortable after the update, however, as I have already found a couple of problem patches, as well as ARP issues. I don't know if the problems are with the patches themselves or with the 1.0.3f engine. My sole reason for updating was the new patches, but I wish I had waited. Now I have that sick feeling as my favorite instrument is suffering from sound quality problems that rule out using a number of sounds in a composition. Though Omnisphere is a new instrument, I am already "entrenched" with Omnisphere as I have used it on a finished work, and am using it in a number of works in progress.
Again, I had no issues with ARP patches before, and I see that this very issue is in the list of fixes. The fix seems to have had the reverse effect in my case.
Issues I have found:
(All of my tests were running Omnisphere as a single instance, with just one track in Logic, with nothing that would interfere with a valid test. As I said, I had no issues with Omnisphere before the update.)
Some ARP patches don't start properly or the timing seems off. The timing sometimes falters when switching from one single note to another in time with the ARP rhythm.
Problem patches in particular:
Dramasweeper Trance Lead: There are some clicks that echo, plus some fuzz, mostly on the left.
Gates of the Secret City 2: Has some small short duration pops.
One of the pre-1.0.3f voice patches that I had arpeggiated behaves differently in a song I am working on. It's going to require some edits. This makes me nervous as one of the patches was a core component to a recently completed work. I'll need to go back and test it within Logic.
I submitted this to Spectrasonics tech support on Tuesday morning and received a reply on Thursday simply asking me to submit a Logic session file. My question was unanswered and it is this:
Q: Is it possible to downgrade to 1.0.2d by simply re-running its installer? I understand that the newer patches will not load. It would be nice to be able to implement an exclusion search filter in this case to search for non-1.0.3 patches.
Q: What will happen if I accidentally select a 1.0.3 patch after downgrading? Will it simply not load, or will something more dire occur?
Q: Is this a problem with the update to the module itself (the engine), or are these just bad patches that didn't get QC'd? If the problem is with the engine then the downgrade is well worth the tradeoff for now.