Skip to content

Releases: defl/videoprocessor

0.3.0: Clocks and any DirectShow renderer

02 Jul 20:44
Compare
Choose a tag to compare

Version 0.3.0. This release focuses on getting the clocks perfect and supporting any DirectShow renderer.

  • Always uses the best clock available (=card hardware clock)
  • HDR info is now in CIE image
  • Added final handler for throws which pops up a messagebox upon thrown exceptions, this allows the user to understand what's going on in many situations
  • Removed all mutexes (outside of directshow), it now runs lock-free with a few atomics to ensure correctness
  • Version number visible in window title
  • Mouse not visible anymore in video render window, both windowed and full-screen
  • Pressing return closed the window, now takes context dependant action with a default of restarting the renderer
  • Our queue dropped frame counter (excluding renderer-dropped frames)
  • Missing frame counter (never delivered by capture but found by timestamp-gap analysis)
  • Process priority is now set to high on start
  • User selectable frame-interval determination modes, clock-clock, clock-theo, theo and none
  • Renderer reset button, which stops, clears the queue and starts playback again
  • AVX required (requires < 10-year old CPU)
  • Disable screen saver/power save when running
  • VideoProcessor is now DirectShow renderer independent, you can use any installed DirectShow renderer.
  • Optional auto-tune params based on renderer queue and exit latency.
  • FIX: Deadlock situation with blackmagic callbacks
  • FIX: frame timestamps now correct
  • FIX: Correct process name in task list

v0.3.0-beta1

01 Jul 20:51
Compare
Choose a tag to compare
v0.3.0-beta1 Pre-release
Pre-release

0.3.0 beta 1: Clocks & all DirectShow renderers

  • User-selectable (frame) interval method
  • Always uses the best (=card hardware clock)
  • HDR info is now in CIE image
  • Added final handler for throws which pops up a messagebox upon thrown exceptions, this allows the user to understand what's going on
  • Removed all mutexes (outside of directshow), it now runs lock-free with a few atomics to ensure correctness
  • Version number now in window title
  • Mouse not visible anymore in video render window, both windowed and full-screen
  • Pressing return closed the window, now takes context dependant action with a default of restarting the renderer
  • Our queue dropped frame counter (excluding renderer-dropped frames)
  • Missing frame counter (never delivered by capture but found by timesamp-gap analysis)
  • Process priority is now set to HIGH on start
  • There are new frame-interval determination modes, clock-clock, clock-theo, theo and none
  • Renderer reset button, which stops, clears the queue and start again
  • AVX required (requires < 10-year old CPU)
  • Disable screen saver/power save when running
  • VideoProcessor is now DirectShow renderer independent, you can use any installed DirectShow renderer.
  • Optional auto-tune params based on renderer queue and exit latency.
  • FIX: Deadlock situation with blackmagic callbacks
  • FIX: frame timestamps now correct
  • FIX: Correct process name in task list

experimental 2021-06-30

30 Jun 22:42
Compare
Choose a tag to compare
Pre-release

https://www.avsforum.com/threads/videoprocessor.3206050/#post-60848704

  • Render independent, you can now pick any renderer you have installed on your system.
  • Removal of madVR specific items & naming

experimental 2021-06-29

experimental 2021-06-28

28 Jun 21:53
91a83cf
Compare
Choose a tag to compare

0.2.0

03 Jun 21:05
Compare
Choose a tag to compare
  • SSE2 build config, not using AVX anymore until needed
  • Losslessly convert RGB formats which madVR cannot handle natively with ffmpeg, right now supports r210 and r12b; both are used by PS4Pro
  • Added FAQ to readme
  • FIX: Displaymode frequency bug

0.1.1

30 May 09:32
Compare
Choose a tag to compare
  • Figured out why my keyboard commands were not working, madVR has anti-debugging protection which triggers when running inside
    of MSVC debugger. That also disables the keyboard shortcuts. They just worked. Cleaned up the code to remove the needless paths.
  • Now has the /fullscreen command line option which can be given. As soon as the program detects a renderable input it'll change to
    fullscreen mode
  • Enable/disable buttons based on presence of renderer
  • If the renderer fails to start ensure no more fullscreen and give user a retry button
  • Fix: Error upon switching capture card input which remembers old state
  • Fix: GUI elements & state related to capture device were uninitialized at start and not cleared when restarting capture

0.1.0

24 May 18:37
Compare
Choose a tag to compare

We're now at 0.1.0 because you can fire it up, go full screen and don't bother with looking at it again.

Changelog since 0.0.4:

  • Full screen now works and remains full even when modeswitching.
    Will full-screen to current monitor.
    Toggle with alt-enter, exit with escape.

0.0.4

21 May 21:30
Compare
Choose a tag to compare
0.0.4 Pre-release
Pre-release

Overridable DirectShow inputs to madVR

0.0.3

20 May 20:58
Compare
Choose a tag to compare
0.0.3 Pre-release
Pre-release

If the renderer throws this is now shown in the GUI and properly handled. You can actually get out of full-screen with alt-f4