Scene detection video recombine ignores export quality settings

On 1.2.0, I was trying to improve an export from a Blu-ray which had been poorly authored and did not interlace the video, leaving it at 1080p h264 at 29.97fps.

I used:

  • Proteus model with dynamic settings,
  • Framerate interpolation to 59.94, no slomo, Chronos model, Replace 10 (default), AND Scene Detection: Enable
  • Stabilization: enabled, full frame, defaults 50
  • Codec settings: H264 High Profile: Dynamic, High Quality, Dynamic bitrate, convert audio to aac320 in an MP4 container.

This took a few days to render on a 5070.. it broke the video down by scene into about 180 pieces.

Before I went in for such a long render I did a couple of shorter exports, one with and without stabilization, but I canceled the render after a few partials were made and looked good, and went on with the full export.

During the 3 days I could check the individual parts as they were created, and did so occasionally..

All the individual pieces were great. H264, high quality output, same as previewed and tested on small sample size. Variable bitrate between 170-220 Mbps.

A FEW of the tasks failed over the course of the few days of the render, requiring a “Retry failed tasks” click at the end. Those few were successful and Topaz proceeded to combined all the partials.

BUT – after it combined all of the intermediary partials, which were each 170-220 Mbps H264, the resulting combined video was 13-22 Mbps H264.

A very significant degradation of the final output quality. It looked worse than the original input video. But all the previews and pre-renders and all of the generated partials were much higher quality.

Soo. Please fix. It seems to be triggered during the final splicing of scenes when Scene Detection: Enable is set.

I ran a much smaller render again (though with 1.2.1 now, which I updated to), with the same settings above, but ONLY turned off the scene detection setting. It came out in the expected 170-220 Mbps range.

I’m currently re-running the smaller render with Scene Detection turned ON to see if it happens again in order to further validate the issue.