11/19/2023 0 Comments Adobe premiere clip h.264![]() I exported as quicktime, preset "match source", and it took 38 seconds The 2.8 file took 38 seconds again.Įxported as Quicktime, gopro, and then did "use previews", the export took 38 seconds, it did therefore not seem to use the preview. The other created a 9GB file, so decided that was not what I needed. I tried both, one created a 2.8GB preview file, slightly smaller, however with no audio. Format: GoPro, codec: Quicktime, or Format Quicktime and codec: gopro. I set sequence settings to custom, and saw two choices. It transcoded using "Match source - GoPro CineForm YUV 10bit" as ingest setting to a 2.8GB mov file in 38 seconds I have an MTS file, 1920x1080 50fps which is 1.03mins and 212MB I have screenshots, however won't upload them unless needed, hopefully my description and numbers will make sense. I am also in a position where I have to make a 2 second tweak, and then wait for the whole file to render out, so smart rendering looks good, even if the final file is large. I've failed to get smart rendering to work. In any case, at least now I can edit with ease! That said, who wants to edit with H.264 anyway, not me! Right, H.264 doesn't work with smart rendering, but wouldn't that be wonderful if it did? Perhaps in the future. I generally want to export either for home video use, to display at events, or for YouTube, so I've always exported in H.264, however that won't work with smart rendering as it's the slow format. That's why a hybrid "smart rendering" workflow exists where you edit with proxies (or the camera originals at a very low resolution) and at the very end, change back to the H.264 masters and render the entire timeline to ProRes, Cineform, or DNxHD/HR-then export. However, if you do not have any render files attached to a clip, smart rendered transcodes with zero effects work the same way. ![]() Yes, your previews have to be in the same format in order for this workflow to function properly. The second part sounds like export is fast, as your previews use the same format, however, the link doesn't work The first part really helps, as I see I can have it auto convert on import, and also on drag into project files. You're going to tell me Google is my friend, however I am also curious about a workflow that suite video editors well. ![]() The other benefit to conversion would be that I could go Ryzen with my next upgrade, however I'd have to be sure it's a lossless conversion. If I did do this, I'd discard the original files, and only keep the newly converted, as otherwise I'd run out of space. I would prefer some quick batch process like handbrake, but the same question arises. I could create the previews in same res like now, but I am not sure if I am losing information. If I do that what's the best tool to use and the best format to use to avoid any loss of quality? This led me to think why don't I just convert all the files into a new format before I start my project. R Neil Haugen also mentioned that h.264 used to be often transcoded before use. I Believe It's all down to the native codec I'm using having a lot of compression. In fact I use the same resolution for those files. Those files use QuickTime and the gopro cineform format. Scrubbing and editing has been painfully slow and I've started using proxy files instead. My camera produces HD avchd files using h264 and after editing I then render out files for YouTube which use the same codec.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |