(The MP4 standard's container is about 99% identical to a regular MOV container after all.)
Also, do not confuse the QuickTime container (.mov) with the QuickTime API - the container is alive and well and still supported by the new frameworks. It has no bearing on which apps can read them, so they can still be read by both 32- and 64-bit apps or codecs. You can have a file stored on a 32-bit file system or in a container with a 32-bit size header but the result of this is that these files will be limited to 2 or 4 GB in size. So to clear up some of the misunderstandings in that thread: there isn't really such a thing as a 32-bit file. There is a Reddit thread with quite a lot of misunderstandings about what the change means. (Sure, you can go to a lower level and write your own parser but if you've reached that point, why bother using Apple's media frameworks at all?) I filed an enhancement request to support third-party codecs several years ago and Apple closed it as "won't fix" so their position on that seems pretty clear. Why would an app still use QuickTime over the newer and non-deprecated AV Foundation? Because AV Foundation does not support third-party codecs. But it affects video software the most because the only reason for an app to still be 32-bit in 2018 is because it uses QuickTime. To be clear, it's not that 32-bit codecs are going away, it's that all 32-bit software is going away. The article is fairly sparse and doesn't go into detail about the change or explain why it is occurring. You may have read Apple's article about "legacy media" being phased out in the next version of macOS or even been alerted by an error message in the new version of FCPX. Thoughts on 32-bit codecs being phased out in macOS
0 kommentar(er)
