Skip to content
This repository was archived by the owner on Sep 1, 2026. It is now read-only.

owlcms jury replays 2.2.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Apr 23:02
· 47 commits to main since this release
2.2.3
9eb57e8

Change log

  • 2.2.3: robustness. trimming time now computed from end of recording

  • 2.2.3: fixes for encoder settings to acheive more reliable trimming, esp. on Intel w/ QSV.

  • 2.2.3: fixed epileptic reload of the replays browser page during recording

  • 2.2.3: robustness fix for the end-of-ffmpeg processing on windows

  • 2.2.2: changes to support new improved Jury Replays user interface in owlcms-tracker 2.16.0

  • 2.2.1: configuration page fixes: changes are applied on the apply button for more predictable behaviour

  • 2.2.0: Improved RTSP reconnect

  • 2.2.0: Fixed windows QSV support

  • 2.2.0: Fixed pixel format issues for MJPEG conversion

  • 2.2.0: For older laptops where ffmpeg 7 does not work due to now unsupported GPU, will back out to system ffmpeg

    • the user is expected to have installed an ffmpeg 6 as the system version

  • 2.2.0: User interface cleanup

  • 2.2.0: when running without the Cameras Streams in autonomous mode, replays will now accept both the auto.toml autodetected items and manually added items in config.toml (e.g. for RTSP cameras)

  • 2.1.0: cameras: Added support for RTSP feeds

  • 2.1.0: cameras: Restructured the user interface

  • 2.0.0: replays and cameras are now installed and started from the control panel

    • preferred resolutions and fps and GPU settings are stored in a shared ffmpeg.toml config file
    • a shared copy of ffmpeg 7.1 is downloaded in the control panel installation directory

  • 2.0.0: replays will now, by default, use the H.264 streams created by the cameras program

    • with normal consumer-grade switches and routers you want to use unicast mode in your cameras config file but this requires knowing your OBS destination addresses
    • from the control panel, start the cameras program to autodetect your cameras
    • check which port is camera 1 etc.
    • if you have cameras attached to several machines, start the cameras on each, and adjust the ports so they don't conflict
    • start replays, and adjust the cameras if needed (change the ports so camera1 is the correct one, etc.)
    • If you want the old behavior, tell replays to stop using multicast

  • 2.0.0: The cameras module uses MJPEG instead of H.264 because dshow cannot recover from startup sync issues.

    • Linux v4l2 has no issues. Windows laptop needs a good GPU to process.

  • 2.0.0: The cameras module can do both multicasting/unicasting

    • When using customer-level switches the traffic from the video propagates up to the main network
    • Use point-to-point unicasting if you only have one or two OBS listening, the overhead is minimal
    • added wallclock timestamps to better support unicasting vs tee mux

  • 1.9.0 added a new cameras (cameras.exe on windows) to start a multicast UDP H.264 stream for each of the detected cameras

    • use -includeraw to include the laptop built-in cameras during testing.

  • 1.9.0 Add Auto-detection of cameras: an auto.toml file is written that can be edited, and has priority over config.toml.

Instructions

For installation and usage instructions, see the main README.md

Supported platforms:

  • for Raspberry Pi : use the replays program
  • for Windows: use replays.exe
Assets 8
Loading