None of my compressors or other processors rely on copy protection to function. Stuff like this is why I hate copy protection, especially when it's a system (like i-lok) that is common to a large number of popular software publishers (so a problem originating with one upgrade can bork a bunch of other programs due to the shared protection utility), and one of several reasons that I've kept my system abgout 90% analog hardware. It also may be, as someone else mentioned, that the new i-lok software is simply not comparible with your current OS and you'll have to upgrade - which may or may not require updating any amount of other stuff on your machine - from the chatter I've read regarding similar problems this appears to be a not infrequent problem with Apple OS upgrades. I don't know about Apple, but on Windows there are commercial 3rd party uninstallers that specialize in these problems. You can contact the Pace customer service people (if they have online chat that would be a good place to start) and give them full info about your OS (with all updates, list of software, etc.) and they might be able to help. If that's what's happening, what to do about it is a good question. Just because there's no i-lok vissible in the applications folder and no i-lok listed in whatever utility analog that Apple has for the uninstall utility that Win uses, does not mean that all aspects of of the old software have been wiped from the computer - there may stll be fragments or background services left that might interfere with the new installation. Faster processors allow new power for new systems. It's tough to say goodbye to some of these old technologies (I don't miss RTAS), but that's the reality of the world we live in. I think many other developers have procedures that aren't so different. I don't keep the old installers available for very long, since I've found that people may still purchase something I no longer support and I don't want them to have unrealistic expectations. In all cases, I try to make that last build as solid as I can. The end of 2017 will mark the end of support for 32-bit AAX (Windows 10). I dropped Windows XP three years ago, RTAS a couple of years back, and then dropped 32-bit AU, VST and VST3 at the start of this year. Support engineers don't want to stay too far behind the technology curve, since it dims their future employment prospects. The sales pool for those systems has dried up and-even if the original pricing has accounted for a certain period of support-you just can't afford to pay somebody to keep up with the old stuff. And if you don't have an image backup or every single installer, then you'll be faced with updating your whole studio.Ī developer of any size has limited resources and it simply makes no sense to try to maintain (and validate) software for obsolete systems. Sooner or later you'll hit the update that breaks the system-either the thing you updated or something else. If you're running a legacy system (and Snow Leopard really fits that description), then keep it legacy and don't update anything. That sums it up pretty well (and Mike Thornton has a nice take on this same subject a couple of weeks ago on PTE).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |