Sorry, not planning on doing that.
My reason behind this is that,
Not planning to do that (reasons above), but I attached you a modified vsViewer version which you can use as replacement for the existing one.
Cu Selur
My reason behind this is that,
- usually the log output is only interesting, if an error occurs, in which case the preview should fail and show the code (main window view) and the error.
- I don't really see much gain in running a benchmark.
- to properly integrate vsViewer main window with Hybrid, it would need additional adjustment of vsViewer (and Hybrid). This probably would then trigger the next request to be able to freely edit code in vsViewer and expect Hybrid to use that code (that is not going to happen). Also, vsViewer like Vapoursynth editor can encode on its own. A better option would be to rewrite vsViewer, remove some of the stuff is can do (like encoding) and incorporate it more into Hybrid. The best option would be to integrate the viewer directly into Hybrid and not keep it as a standalone tool.
(I don't have the time and motivation for that.)

Not planning to do that (reasons above), but I attached you a modified vsViewer version which you can use as replacement for the existing one.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.