- Posts: 29
- Thank you received: 2
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
10.4 Release
... and latest iMovie imports and plays said H265 file smoothly. Looking good for FCPX 10.4 then. :whistle:
Please Log in to join the conversation.
- DmitriZigany
-
- Offline
- Platinum Member
-
- Posts: 730
- Thank you received: 26
I'm thinking sooner rather than later because they showed it...
Or do you think there will be an additional event for the release of the iMac Pro in December where FCPX 10.4 will be released as well?
Pointless speculation, I know. But I'm itching to update to High Sierra but trying hard to hold out until FCPX 10.4... gah!
Please Log in to join the conversation.
- mark.manning
-
- Offline
- New Member
-
- Posts: 8
- Thank you received: 0
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
- Posts: 971
- Thank you received: 46
Please Log in to join the conversation.
Please Log in to join the conversation.
- mark.manning
-
- Offline
- New Member
-
- Posts: 8
- Thank you received: 0
As Tom points out, it's available with Compressor, which the cynic in me believes is the primary reason why FCP doesn't do it natively, because, well, Apple sells Compressor!
Please Log in to join the conversation.
mark.manning wrote: So 10.4 is here and... still can't find an option to export in H.265. Looks like they've only added an option to import videos so encoded.
Exporting to H265 requires using a Compressor setting.
You can export from FCP X, but need to have Compressor installed.
An alternative if you don't have Compressor is to export in ProRes or H264, and then use Quicktime Player to export. In the QT export window there is a checkbox for "Use HEVC".
Please Log in to join the conversation.
- Posts: 971
- Thank you received: 46
Of course we have no idea, but Apple does like to do things we don't expect...So maybe both..but the name AV1 sounds very close to AVFoundation... :blush
OH that is what I wanted to say...HEVC is a bag of hurt...who said that before...Steve about Blu-Ray, and the reason it failed..royalties and such...the same issues with HEVC..Apple was not able to "buy' the rights or was prepared to sacrifice FCPX with HEVC if AV1 is the replacement...
Makes every sense to shove it in an related app, that at a moments notice HEVC can be uninstalled from compressor and replaced with AV1...
Please Log in to join the conversation.
- mark.manning
-
- Offline
- New Member
-
- Posts: 8
- Thank you received: 0
Please Log in to join the conversation.
- mark.manning
-
- Offline
- New Member
-
- Posts: 8
- Thank you received: 0
Please Log in to join the conversation.
Please Log in to join the conversation.
mark.manning wrote: ....As Tom points out, it's available with Compressor, which the cynic in me believes is the primary reason why FCP doesn't do it natively, because, well, Apple sells Compressor!
That is *extremely* unlikely. HEVC/H265 is heavily patent-encumbered. There have been major disputes over licensing, royalties and intellectual property. At one point the patent holders were demanding a % of gross revenue from each individual end user who encodes H265 content. That is one reason Google developed the open source VP9 (and later AV1) codecs. The HEVC/H265 patent holders later retreated from their more egregious demands, but that negatively tainted H265 and has delayed deployment.
The licensing and royalty issue is why the evaluation version of Premiere Pro does not have H265 -- even though Adobe claims the eval version is 100% full featured. It is due to H265 licensing issues.
I don't know for sure but I suspect that is also the reason why iMovie only imports HEVC/H265, but does not export it.
I doubt Apple is concerned about nickel-and-dime revenue from a few additional $49 Compressor sales. I more suspect the HEVC/H265 licensing royalties require a per-unit payment if that intellectual property is (a) bundled in a software product or if (b) certain features are used. Apple sells a lot more copies of FCPX than Compressor.
If that is true then Apple would have to pay HEVC/H265 licensing fees on every copy of FCPX sold, whether the purchaser ever used that codec or not. By putting it only in Compressor, it is still easy for the FCPX user to access and it may reduce Apple's licensing payments. This is only speculation but I think it's far more likely than Apple wanting miniscule additional revenue from Compressor sales.
Please Log in to join the conversation.
Please Log in to join the conversation.
- mark.manning
-
- Offline
- New Member
-
- Posts: 8
- Thank you received: 0
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
joema wrote: ……If that is true then Apple would have to pay HEVC/H265 licensing fees on every copy of FCPX sold, whether the purchaser ever used that codec or not. By putting it only in Compressor, it is still easy for the FCPX user to access and it may reduce Apple's licensing payments. ….
Would make sense.
But, as mentioned before: EVERY installation of HS includes the QuicktimeX Player, which allows to encode to HEVC…
Please Log in to join the conversation.
Please Log in to join the conversation.
You can use HandBrake (free soft) if you don't want to buy compressor. You can export in H265 (exactly X265 free version of H265) in Handbrake. I don't know for H265, but for H264 HandBrake make a better job than Compressor.
Please Log in to join the conversation.
Does it really? I can't find it. That would be great if it did.
BTW, it is simply called "QuickTime Player" now, Apple dropped the X.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.




