![]() For instance, a sequence with half DNxHD 36 and half 115 will report a bitrate of about 80. The resulting QT file will still report "DNxHD" as the codec, but the bitrate will be an average of the different formats within. It appears that a "Same-as-source" Quicktime Movie can in fact contain multiple "flavors" of DNxHD- e.g. Also, the "Commercial Name" tag is missing- whatever that means. ![]() It's interesting that the bitrate in the non-working example is ~46 Mb/s, which does not correspond to any flavor of DNxHD at 1080p. The latter is an export of a sequence composed of DNxHD 36 clips, with the occasional DNxHD 115 imported title. The former is a single DNxHD 36 clip, exported directly from the source window. Still, the SAS method used to work just fine.įor what it's worth, here's the mediainfo description of a file that DOES work in Media Encoder:Īnd here's the mediainfo description of a file that DOES NOT work in Media Encoder: This isn't too terrible for us since we only do short-form material, and an extra transcoding step doesn't slow us down too much. ![]() Render your video to a different lossless codec first and then re-encode it back to the desired codec.Our assistant editors have all taken to exporting Prores QT's as an inermediate instead of Same-as-source. Like so:Ĭhange the export encoding "Performance" setting to "Software Encoding" if you're using h264 or h265 codec. Yes, not very intuitive.Ĭhange renderer in Media Encoder to "Mercury Playback Engine Software Only". Media Encoder uses your project's render engine setting, not the one displayed below the queue. It seems that Media Encoder is trying to render your video with the graphic card, which does not have enough memory for a particular frame to render.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |