To the developers of TOPAZ:
Prompted by user SkyDude, I’ve now tested FFV1 as well.
In principle, Topaz behaves the same way here.
That is, the more data-intensive the selected codec variant, the sooner the error appears:
BUT THERE IS A VERY INTERESTING DIFFERENCE!
(which can be seen in the screenshots)
While with ProRes and AVID (JPEG-based/intraframe-compressed codecs), the error is accompanied by a drop in GPU performance (see screenshots above),
with FFV1, on the other hand, there is an increased demand on the CPU!
The GPU continues to operate at around 100%.
In my opinion, this is an interesting clue that might show the programmers where they need to look?
utilization and start of problem after 24 min from start:
… after 60 min
System during the TOPAZ outage:
ffmpeg.exe ran “smoothly” for many hours until the end, after Topaz was shut down in Task Manager:
kind regards
1 Like
Just a thought… Are you sure the SSD drives are not getting too hot when writing (and reading) that much over longer periods of time?
I have the ‘SamsungMagician’ tool, and it says everything is fine 
Well, the hours of READ operations caused by Topaz could potentially become a problem, but as described above, I just shut down Topaz in Task Manager after starting the task, and then everything runs smoothly …
see the last screenshot!
… but I’ll never make FFV1 my default, unless I work for Hollywood and earn $50,000 or more for it…
… I just tried it → 200 gigabytes for an 18-minute file (4K at 60 fps via AION)
… but it runs well in DaVinci …
… the VLC Player can’t play it smoothly; the data rate goes from about 1.2 Gbit/sec to briefly almost 2 Gbit/sec … a disaster
kind regards
1 Like
I like to MAX it all out, even if I work for myself on hobby projects… 4:4:4 can have a minor impact on clarity, especially if doing additional scaling in post…. And if running Starlight Mini for days, or even weeks, it is a waste (in my eyes) to not go for the best lossless format.
MPV can probably play it back smoothly for you (if Resolve does). 
1 Like
