FlashFilter v0.2.0 Release Notes - News

After another couple weeks of work we have ported our control GUI to use a different library which should make furthur development simpler as well as fixed numerous bugs. If you find any additional bugs in this version we would love to know! Send us an email at [email protected].

1. Single GUI for flashfilter connections

Affected: Linux, MacOS, Windows

In the previous version opening FlashFilter Control multiple times would result in the first window connecting to the running FlashFilter and the others sitting in an offline state.

2. Screen freeze bug on turning filter off

Affected: Windows

Windows is currently hard coded to use the opaque filter mode which previously resulted in the screen freezing when the filter was turned off (since the filter feed stopped being updated). The filter and screen capture are now completly removed when the filter is turned off.

3. Console pops up on when running GUI

Affected: Windows

Console will no longer appear.

4. Adjust profile parameters according to refresh rate.

Affected: Linux, MacOS, Windows

The previous release assumed people were running the filter at exactly 60 Hz which is not generally the case across operating systems. This resulted in different amounts of filtering and artifacts depending on the Operating System and Desktop Environment for the same configuration.

The algorithm parameters are now adjusted according to the refresh rate of the target monitor.

5. Linux Bug: Close button when DE does not provide Window Decorations.

Affected: Linux

Some Wayland compositors do not provide client window decorations. FlashFilter Control did not provide a close button in such cases which led to an issue where users could become unable to close the window. In such environments the app will now provide a close button in the top right.

6. Lack of code signing prevented install of the app.

Affected: MacOS

We currently do not pay Microsoft and Apple the subscriptions (have made $0 so far) for signing certificates which are needed to avoid security flagging. On Windows it is possible to work through the big scary dialogs to run the program but on MacOS a user would have needed to manually go into the terminal and remove the com.apple.quarantine attribute.

We have started signing with self-signed certificates so that it is at least possible to jump through the various dialogs to run the app.