Can you imagine trying to use multiple, different, internet-based and hard-drive dependent methods, involving emails, registration apps, native access and all manner of other f*ckery to register multiple (100's of?) different plugins whilst sitting in a completely foreign studio, surrounded by expectant faces? I can't.
It's about being prepared for whatever the client isn't prepared for. you have a 128/256GB flash drive with all your essential, iLok only software set ups and one iLok 3 key. It'd be fine if you only used Fabfilter - or Steven Slate, or Solid State Logic. The fervent, anti-iLok enthusiasts should try and understand that there's simply no other efficient way for a working pro to take their tools from studio to studio. Everyone's happy! The masses are delighted and the pros get to keep moving. However, if like some of the responders here (myself included) you make your money as a pro engineer, you can request a one time switch to convert the plugin license to iLok for free. Buy their software with the normal, OE copy protection and live your life. More information on the original alert can be found here.I'll say this first. Having built a few systems with Windows 10 and Pro Tools I confess that I’ve not tried those particular combinations but otherwise I’ve found Pro Tools to work very well on Windows 10. What these problems are is anyone’s guess. With regular Pro Tools there appears to be no such limitations other than the usual feature of not being able to cope with anything but regular 2-powered buffer sizes. HD Native – avoid using these buffer settings: There are some provisos if you are using Pro Tools HD Native or HDX. I stumbled across someone mentioning it on Facebook, otherwise there seems to be no other press release or announcement. It’s a bit weird because you’d think it was a big deal but all they did was release a little “ALERT” (in capitals so it must be important) on the System Requirements page. All we know is that someone somewhere in Avid has said “yep, it’ll be fine, let’s not make a big deal about it”. Or maybe they’re aware that many people are actually using Pro Tools on Windows 10 and nothing bad has happened.
Maybe we’ve been waiting for the support staff to finish their Windows 10 training.
They haven’t released a software update that makes it compatible, it’s still the same Pro Tools 12.5 that wasn’t supported on Windows 10 just the day before.
0 kommentar(er)
