I believe that trim by frame specification can be supported.
FFMPEG can also be trimmed by specifying the frame.
-vf trim=start_frame=10:end_frame=30
There may be some implementation issues such as how to handle frames on the GUI side, how to work with vfr, and how to handle audio (audio is not in terms of frames, but samples).
2020 iMac,128 GB Ram, 10th gen 10 Core i9, 5700XT 16 vram, source dv to progressive, enhance and upscale from 640 to 1920 with both Artemis low quality and and Proteus manual. Source on very fast SSD and Exports on Very fast SSD. I’m am seeing amazing performance and quality improvements. I’ve seen 8 frames per second exports when previously I might get .something other output. That’s incredible. Also, I’ve been working on a creative directors spots and the problems with faces for example has dramatically improved. He may be able to show at 1920 progressive what was once 640 interlaced to clients now given the Improvement you folks have made. Well Done! And godspeed to further quality improvements. Beta v3.1.1.1.B
I also added selections for medium and high quality as well (for FHD and UHD, respectively), since the default is the highest quality setting if none where specified.
I had actually bought a Cineform license a few months before GoPro bought them out years ago and back then had talked to the guy who had invented the codec about the quality levels to use for various resolutions.
His advice had been that with the way the wavelet encoding worked, while using higher quality settings resulted in a larger file, there was no actual gain in quality for HD material above the medium setting, and no gain for 4K (UHD) material above the high setting. And while 8K resolution was a pipe dream at that time, that would be where you would use the film setting of the codec.
Over the years that’s shown itself to be true in my experience.
Yeah, it took me an ignorant amount of time saving up for it, so I’m in no hurry to upgrade, hell, it would take me a year or so of saving up to upgrade my rig to the current gen!
It’s not actually lossless. Wikipedia says it’s a high quality visually lossless codec.
So not totally lossless, it just looks the same visually (but may be losing details that you can’t easily see but which might be useful later in editing). eg. a totally lossless codec could be a bit better for keying.
No codec is “ lossless” per se. Anytime VEAI exports it is re-encoding no matter to what or the codec. Anytime you re-encode you’re loosing a generation. Therefore by definition the export is not lossless. No export is. Practically speaking though exporting to Prores HQ and TIFF 16 bit is lossless. In other words and as you mentioned, one can’t tell the difference between the original and the export-even on a big screen. Even exporting to 4444 isn’t lossless. Yet, practically speaking if you export from the raw to 4444 the export will still be perfectly fine for both VFX work and color grading. 422 HQ is great for keying although 4444 or the raw is ideal. Though never as good as the original source, the difference is so minuscule, practically speaking, that it’s irrelevant. You make good points however. I’m just being pedantic.
100% lossless doesn’t exist…but UT Video I think it’s the best in this…TIFF doesn’t work for me because of how I edit afterwards. I think that UT Video is not due to copyright issues… but since it is (ffmpeg) I thought that it could be implemented in some way.
After this update. I’ve been having trouble with the software, it’s not exporting videos. and some get the message “Unknown error” - “last FFmpeg messages”. I’m sure if I’m the only one having this problem. But, I’d like some feedback on this.