← all posts site ↗

the resolve convert loop

free resolve on linux cannot read phone footage. the h.264 and hevc files straight off the phone get refused at import, so there is no way around a conversion step before anything lands on a timeline. and since free resolve also cannot export mp4, the loop has two conversions in it. the editing itself is just the middle of the sandwich.

the size numbers were the scary part until they got measured on an actual clip. a five second 4k clip at best quality becomes about five hundred megabytes, which is over six gigabytes per minute of footage. 1080p best quality is about 1.6 gigabytes a minute. but a light 1080p mode lands at twenty six megabytes for the same five seconds, about 335 megabytes a minute and nineteen times smaller, with quality somewhere around proxy level, which is fine for phone clips and posting. the final mp4 came back at thirty megabytes. and all of it is scratch. you convert only the clips you edit, they live for the length of the project, and they get deleted after the render. nothing permanent grows.

other linux editors do exist and they just read the phone files directly, no conversion ever. considered it, and then decided to stay resolve only anyway. so the loop is: tell the assistant which clips, it converts them and drops the files in a folder on the desktop, they get imported into resolve, edited, rendered out as the intermediate codec, and then the assistant converts the render into the mp4. the user side is import, edit, render. demo files are already sitting in the folder waiting, one converted clip and one finished export, so the whole pipeline can be watched working before committing a single real video to it.