It would be interesting to try with ProRes, but I guess you don't have a Mac around.
In my old tests, I got different results from SAS export of DNx vs ProRes, with RGB vs 709. Dnx and ProRes were identical with RGB flag set, and not identical with 709 flag set.
Cheers,
--Michael
Just tested RGB vs 709 QT export of a mix down with DNxHD (I'm on Win, but I assume the same goes for ProRes)
The option does nothing more than setting some 12 bytes different in the QT metadata.So, it's up to the decoder if this setting is honoured or not.
And we could know this, as you have the same option by exporting as a QT ref, where obviously the source is the same in both cases.
IOW, the actual data is the same. There is NO RULE OF THUMB if you have to choose one or another.Only way to be sure is to test. (Where in some cases it won't matter.)
hth,
On Oct 7, 2016, at 07:21, Michael Brockington mbrock321@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
My comment was very specifically about exporting ProRes codec same-as-source. In my testing, the output would come out full-range (RGB-levels, in the old nomenclature) regardless of how the RGB/CCIR flag was set.
But looking back at my notes, I see I tested this way back in 2012 on v.6.x, so it may have been fixed by now!
Cheers,
--Michael
I have definitely seen differences in how Adobe Media Encoder treats QT ref files exported from Avid when it comes to Full Range vs. Legal. Given the QT ref file is referencing what is Rec 709 video essence I assume it is just a metadata flag that gets set in the case of a QT ref.
My practical experience is that when I export a legal level QT Ref of Avid DNX 175X timeline and use Adobe Media Encoder 2014 to make an XDCam 50 file the levels are low. If I do the same thing checking Full Range on the Avid QT ref export the resulting AME XDCam50 file is proper levels.
I'm not sure how the behavior is with other codecs but in that specific instance I have to export Full Range. From this experience I have begun to think that AME in general wants Full Range level material but I don't really know if that's true. It may well be that the QT ref path differs from how AME deals with a self contained .mov. At a past Editor's Lounge I asked some Adobe folks about this sort of stuff and was told the AME doesn't really handle QT ref correctly. They didn't elaborate on that as it was not their product specialty but I use AME all the time with QT reference files to save space and time. Of course I do tend to live on the edge when it comes to files. ;-)
---In Avid-L2@yahoogroups.com, <cutandcover@...> wrote :
It definitely does for me. Not in the video content - that is always legal. But the way apps display the content on an RGB screen changes, and the way some apps (like Compressor) treat the levels differs if you choose keep legal instead of expand to full. Therefore I almost always choose expand to full so the next apps see it correctly.
On Thu, Oct 6, 2016 at 12:23 AM, Michael Brockington mbrock321@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
Mixdown. Export SAS. Works every time.
I do the same thing, and it always seems to work fine. I don't believe the full-range/video-range checkbox has any effect when exporting SAS ProRes, BTW.
Cheers,
--Michael
Posted by: Michael Brockington <mbrock321@gmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (19) |
No comments:
Post a Comment