Ffmpeg tvai_up filter writes text to STDOUT instead of STDERR

Topaz Video Bugs and Issues
1

Running the Topaz Video version of ffmpeg from the command line produces diagnostic messages, starting “[TopazAuthManager]parseAuth got details{“auth_studio”:” that go to STDOUT (standard output). Similar messages from the open-source parts of ffmpeg all go to STDERR (standard error) and can be silenced with the option “-loglevel error”

It’s often useful to send the video output of ffmpeg to STDOUT (by specifying the output file “-” or “pipe:”) for immediate processing but this can’t work if diagnostic text is also sent there, corrupting the video data. Not sending to STDERR also means that diagnostic messages are not seen in cases where STDOUT is being redirected.

Could you please update your ffmpeg tvai_up filter to send diagnostics only to STDERR, and to have them controlled by the ffmpeg “-loglevel” option, in line with standard practice. Thanks.

This is with Topaz Video version 1.0.4 on Microsoft Windows 10 Home version 10.0.19045 Build 19045.

2

I will pass that along to the devs for consideration and see what they say. There are some changes coming up that have been in the works for a while regarding CLI workflows and aspects in the app. So we will have to see when those can take effect and how that affects this aspect as well.

4

I don’t like the sound of the part about “changes coming up …regarding CLI …”. Knowing the way Topaz works by now, it’s almost certainly going to be bad news for us CLI users.

It appears I was right to warn people about the change to the EULA regarding the CLI for Personal Licence users - which crept in very quietly in v1.0 as though Topaz hoped we wouldn’t notice.

Then there’s the removal of the CLI documentation etc. It’s all adding up now.

No doubt there will be more weasel words about this from those in authority at Topaz.

Andy

2 Likes