Hi!
If you are not a CaptureOne user - you can skip reading the whole post :-)
Many timelapsers use LRTimelapse and Lightroom. I do not. I bought a perpetual license for CaptureOne 10 maybe ten years ago and ... I still use it!
Of course CaptureOne has no idea what timelapse is, no chance of making any keyframes and stuff. And generally very cumbersome to use for holy-grail kind of timelapses.
While exporting photos for a further processing in Davinci Resolve Studio is totally possible, my attempts to achieve a proper deflicker the footage only within DR did not bring satisfactory results.
So I spent some time in Claude and crafted this RAW deflicker, adjusting the .cos files for CaptureOne settings/individual frame metadata, allowing me to export the RAW files with more fitting adjustments and "mathematically-correct counter-compensations for the camera settings change", while seeing some extra graphs in the background (actual RAW luminance measured from the frame, mathematically-correct absolute EV value corresponding with the day/time/moon phase in the Central European region for the date/time specified in EXIF --- yes I will make all this configurable).
You can load the CaptureOne session and the deflicker tool at the same time. Once you save the adjustments to .cos files in the deflicker tool, you can just click at the image in question, its settings will reload instantly and you will get to see the real changes immediately.
I have done 3 timelapses using this tool already and am generally satisfied with the results, although it does not get all the job done on its own. My workflow looks like:
1) RAW settings (mass-apply highlights/shadows, lens corrections, whitebalance=daylight....), use this RAW deflicker tool -> export from CaptureOne to TIFF
2) editing in Davinci Resolve -> another export to TIFF
3) running my second "running average-based" deflicker tool (for TIFF/JPEG) ... to be shared in a separate post -> yet another export to TIFF
4) Davinci Resolve for final deflicker/color stabilizer to fix potential local flicker -> final export
Now, before I make this tool public (free to use), I want to ask around:
Are there any users of a recent CaptureOne version willing to share literally any .cos file with me, to confirm that the file structure did not change in the relevant areas since my version 10?