> Some have complained the lack of h264/265 import on Linux version of
> Davinci Resolve, but you can always transcode to "pseudo-lossless"
> codec such as DNxHR/DNxHD (or ProRes if on Mac) using ffmpeg first. This
> step is usually automated using script to convert raw footage. Most pro
> workflow also involves this extra step, because editing on h264 source is
> really painfully slow and inefficient.
The preferred workflow would be import h264, edit using proxies, then render the result from the original files. A pro workflow shouldn't involve a gratuitous transcoding step. Mind you a real pro workflow wouldn't involve ingesting h264 files at all.
But it might be true that I should just get over myself and transcode the files before editing.
> Davinci Resolve, but you can always transcode to "pseudo-lossless"
> codec such as DNxHR/DNxHD (or ProRes if on Mac) using ffmpeg first. This
> step is usually automated using script to convert raw footage. Most pro
> workflow also involves this extra step, because editing on h264 source is
> really painfully slow and inefficient.
The preferred workflow would be import h264, edit using proxies, then render the result from the original files. A pro workflow shouldn't involve a gratuitous transcoding step. Mind you a real pro workflow wouldn't involve ingesting h264 files at all.
But it might be true that I should just get over myself and transcode the files before editing.