To not be able to use HAP codec (which is widely used by visual artists in particular) or really any third party codec, was a huge oversight.Īnd you gotta love that the best solution to make a software I pay for monthly work properly, is to buy a third party extension for AME at $100 a licence. What they also didn't do is put in place any kind of alternative. But their decision to do so was a MAJOR shift, and was not adequately communicated to the users (as usual). Well, I realize Adobe didn't do this just to inconvenience me (and thousands of other users). There are plenty of things the Creative Cloud Desktop App could do to make updates more transparent (and people should file feature requests for those, such as disabling the "uninstall previous versions" button by default), but that's an issue for that app. I know most people don't do that, but it's our responsibility as users to know what we're installing. Confusion was created because people didn't read release notes when they upgrade.
If you still have access to them in CC 2017 then you should just use that. I would argue that most people are on the same versions of Pr, Ae, and AME-not necessarily the same version as everyone else, but on their own machine each is more likely to be the same than different.Īs for disconnecting those codecs from everything except AME, I think that would have added just as much confusion and is a seemingly pointless exercise.
Also, I feel like Dynamic Link backwards compatibility would be a waste of development resources. I've gotten different versions to work with older versions of AME by simply having them open in the background before sending a comp to it, but it's not a good idea. That's not to say that it's not possible. Dynamic Link gets updated just like the rest of the software, so having version mismatch could cause issues with connecting comps.
0 kommentar(er)
