See it, the fourth entry down? What’s frustrating is that there’s no information on why it’s not a file format that the video editor Final Cut Pro X can import, it’s just dead. Here’s our starting point, a few minutes of video shot with the new iPhone X:ĭouble click to open it up in QuickTime Player and it looks just fine:īut jump into Final Cut Pro X to import this particular video snippet and it’s greyed out and unavailable to choose: Let’s step through the process so you can see what I mean. I really don’t understand why, but… it works. MOV files from iPhones and iPads without an issue, and if you then export it with a different name, the resultant file has the same suffix (.MOV) but is in a format that works with Final Cut Pro X (1080p, H.264 or H.265, up to 1920 x 1080 resolution). Yes, QuickTime Player can play all of the. Nope, not this time.įortunately, the tool to fix the problem is already on your Mac, though it’s a bit tedious to work with, especially if you have a bunch of videos to correct: QuickTime Player. I mean, you’d think Apple would make sure that its pro level video editing tool would be able to work natively with video recorded on its own devices, and that if you were going to have any import problems, it would be from weird cameras, surveillance devices, downloaded footage from the Web, etc. I’ve encountered this particular Final Cut Pro X glitch too and from researching it believe that there’s some issue with the compression codec used with this particular video footage on the iPhone.
0 kommentar(er)
