Thanks Bee Jay for your clarification, but I still think the whole "mess" with the Atmosphere/Trilogy on Intel machines looks a little bit shady to me.
I don't care about the difference between an "Intel version" and an "Intel solution" as long at it works. Most of the user of the wrapper solution would agree that this is not a "workable" solution, more a "workaround" than a "solution". It doesn't live up to the standard that we are used from Spectrasonics. It feels more like something an intern put together on a weekend assignment. I still would call it a band aid, and a real bad one.
Spectrasonics should have known what their pro clients are expecting from them and they also should have known what kind of inferior product they were about to release to them after a year long development. BTW isn't it still a beta version. A beta version of a fix!
Maybe Eric Persing posted that information somewhere to warn their customers about the detail of the solution, I don't know. I only remember the big disappointment on the forums when they release it. "What the ^%$ is that, we waited a year for THAT?"
I know, transitions must be a pain in the butt for software developers (OS9 - OSX - Intel). But I judge a company not only how good of a product they release at a given time, but also how much they care to help their customers with their product through a transition. As an end user we also have to go through some growing pains to go through the transitions, not only financially , but also with the logistic: Two issues.
1) Saved Settings
I like to invest time to use and organize the Plug-in settings in most of the software plug-ins. With so many patches to choose from, I build my own library of Plug-in presets that I can fall back. When an old plug-in gets "folded" into a new version, like Atmosphere (or FM7-FM8, Absynth3-Absynth4), all those Plug-in setitngs that I have neatly organized in subfolders are not accessible form the updated Plug-in even if they use the same sound patches. I have to start all over again, or rebuild my folder structure.
2) Backward compatibility
I often have to open up older projects for remixes. Now on a MacPro with Leopard I still can open a Logic project from a year or two years ago but not all the plug-ins come up. I have to keep a legacy machine around to open them up and maybe bounce those tracks and import the file into the new machine. I read a post from Eric Persing where he suggested exactly that. Quite frankly, I consider that a slap in the face. It is like, "instead of us (Spectrasonics) spending the time (= money) to create a workable solution, we prefer you (the user) to spend the time (=money) to work around the issue.
About the UVI option. Bee Jay, you said that Eric explained that it wasn't possible. I don't know if that is true. One thing I know is that I had the old PlugSound plug-ins with the old UVI engine and now I have the new PlugSound Pro plug-in with the new UVI engine. I have the old Atmosphere/Trilogy plug-ins with the old UVI engine and now I have a lousy wrapper workaround NOT using the new UVI engine. I think the PlugSOund Pro was even released before the Spectrasonics wrapper. So why is it possible for other companies and not Spectraonics?
I sill think the best solution would have been to invest the time/money to work on true Atmosphere/Trilogy Intel version. That would have saved Spectrasonics from the PR damage. Omnisphere would have still be the new killer app like Stylus RMX was when it came out.
All I'm saying is, Spectrasonics lost my respect as a software company, that I thought cared about their user.