Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Solution for Poor Apple TV Exports?

So I've been doing many export tests from FCP X. My main goal being for Apple TV 2 playback. I even used thed the Current choice from the basic Export Media option. I expected that to look like the original. I hardly looked better than the Apple TV 2 exports though. The I grabbed a Current Frame. It looked bad too. It made me think that FCP was grabbing from the proxy media. In prefs I went back to original media for playback and the frame grab was perfect. I then export again using Current and it was perfect. I thought I hit on something so I tried the Apple TV 2 export again. It looked bad again though. This really bothered me. For the heck of it, I took that Current export and used that to export from QuickTime instead using the Apple TV option. It was BEAUTIFUL - relatively speaking. Why though? NowI know I won't export from FCP like using those presets. I swear its using the proxy media. In fact, maybe I'll try again after deleteing the proxy media. Is Compressor worth the money for basic exports?

Posted on Jan 29, 2012 6:26 PM

Reply
14 replies

Jan 30, 2012 10:17 AM in response to innocentius

Thank you. And here is an update. The issue was still happening but appeared to not be quite as noticeable with progressive footage as interlaced. I just did another test from 1080i footage froma different camera. Again, the resolution of the final H.264 file way WAY better when it was exported from FCP X via Current from Export Media, then creating the Apple TV version from that file in QuickTime. But I noticed something about that file made from that camera - when pausing on movement, I can see a ghosted image that isn't in the poorer quality H.264 file created directly from FCP X. Is this from the second field in each frame? If a project is interlaced, is exporting in FCP Xsimply throwing out half the information where the export from QucikTime is not? I want to say when not pausing that the Quicktime export is still way better because of the much better resolution, regardless of the motion blur. How would Compressor handle this? I hope this helps someone and thanks for any answers or comments.

Jan 30, 2012 4:03 PM in response to Michele Gardner

The more I look into this, it simply appears that if I export Apple TV 720p H.264 from FCP X and the project contains an interlaced 1080 file, then FCP throws out one of the fields on export (basically giving me 540p video in a 720p file, where if I export via Current from Export Media in FCP X, I get both fields, which when I export from QuickTime to Apple TV, I get both fields and MUCH better resolution. Wonder which would happen if I used Compressor.

Also, I do see a difference in 1080p footage exported both ways too. Direct from FCP X is not as good but it is very very slight.

Anyway, I hope this helps someone, but if I'm totally wrong, please feel free to correct me.

Billy Gardner

Jan 31, 2012 11:10 AM in response to Michele Gardner

Great news. The new update to FCPx seems to solve this Apple TV issue of droping half the fields. The Apple TV export now looks as clear as can be. The blending of fields for fast motion is superior to the other way I did it through QT as well. When pausing on fast motion, I'm not seeing double images even though the resolution is all there. I'm very happy now.

Jan 31, 2012 3:06 PM in response to Michele Gardner

After many, many export tests, I believe I figured it out and it has to be a bug(s). And remember, as far as I can tell, I'm only having this issue when exporting to Apple Devices (specifically the Apple TV setting), not when using the Export Media option. This is not an issue with mixing file types in a project like I last thought was possible. This is an issue with proxy media. First, I was under the assumption that regardless of if you were using proxy media for your playback, your export would be created from your original media. To me that makes sense in a pro application. If I'm wrong about that, someone please chime in. It appears that if your playback is set to proxy media, your export is created from proxy media too. This is bug number one. If this is how it is meant to be though, there is still another bug. Lets say you've exported using proxy media and got a low res output. So you go to prefs and turn that option off so you're now using original media. Now you export again. Here's the next bug. Your output is still low res. The only way I found to correct this is to make a small change in the project while using original media. Once I do that, the project exports to the h264 720p Apple TV setting beautifully. When I get home, I'm going to use Provide Feedback in FCP to submit this issue.

Billy Gardner

Jan 31, 2012 10:15 PM in response to Michele Gardner

The bug you're talking about has been discussed here - https://discussions.apple.com/thread/3688356?answerId=17417401022#17417401022.


You need to change your prefs when you export - playback preference MUST be set to original/optimized NOT to proxy - I was told on this thread that it's a feature and how it should preform but it's just strange weird as if you look at the bitrate I swear that its PROres 422 std but output looks like proxy :

Solution for Poor Apple TV Exports?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.