Re: [Avid-L2] Lavc57.24.102 netflixprores 3840_2160 What is this codec that I can ama but not transcode or consolidate?

How long does it take AME to spit out a new ProRes file, John?

If significantly longer than it takes to just copy the file, then it's clearly transcoding, not re-wrapping.

Cheers,
--Michael

_________________________________  Michael Brockington, film editor  www.minusblue.ca  .oO=Oo.

On 2020-11-20 10:19 AM, John Moore wrote:

I did find that using a "Save As" in QT Pro7 carried whatever issue Avid has over to the newly saved file.  Same if I did export in QT7Pro instead of "Save As."  I'm thinking after hearing from my Netflix contact that they use FFmpeg and other in house custom apps to make their own kind of prores files.  Don't know what it facilitates but I'm sure it makes sense in their workflow.


On Fri, Nov 20, 2020 at 09:01 AM, Mark Spano wrote:

Almost positive any transcode in AME is a transcode and not a rewrap. I only ever got rewraps from Apple Compressor, and that was in the FCS3 era. I don't think the newer Compressor can do that anymore. In the ffmpeg world, you can rewrap very easily, but then you are preserving the Lavc data and only rewrapping into a new container, so I would bet you'd still have the consolidate issue in MC.

On Fri, Nov 20, 2020 at 11:38 AM John Moore <bigfish@pacbell.net> wrote:

So given I took a ProResHQ file into Adobe Media Encoder to spit out an identical but properly branded or signed or whatever the proper term is that makes Avid not see this ProResHQ file not as foreign compression it is theoretically possible that it could be no loss, it sounds like this is unlikely to be the way AME is coded.  So basically I'm asking when going from ProResHQ to ProResHQ does AME rewrap or transcode.  Since there is no change in the codec other than whatever metadata makes it a "blessed" proreshq in the eyes of Avid I'm wondering is there a chance it's a lossless process?

 

 

_._,_._