Bzzrt 1.1.1

Bzzrt 1.1.1 adds the app icon and fixes a few bugs. The tests and measurements are unchanged from 1.1.0.

⬇️ Downloads

System	File	Start
🪟 Windows 10/11 (x64)	bzzrt-1.1.1-windows-x64.zip	double-click vrrdiag.exe on the monitor you want to test
🐧 Linux (x86_64, glibc 2.34+)	bzzrt-1.1.1-linux-x86_64.tar.gz	./vrrdiag-launch
🏔️ Arch Linux and derivatives (x86_64)	bzzrt-1.1.1-1-x86_64.pkg.tar.zst	sudo pacman -U the link, then start Bzzrt from the app menu or run bzzrt
🍎 macOS 12+ (Apple silicon)	bzzrt-1.1.1-macos-arm64.zip	open Bzzrt.app (first time: right-click → Open; macOS 15: System Settings → Privacy & Security → Open Anyway)

Check the files against SHA256SUMS.

🖼️ App icon

• Windows: vrrdiag.exe and its window have the Bzzrt icon.
• macOS: Bzzrt.app has the Bzzrt icon.
• Linux: the app-menu entry uses the new icon. Run ./package-linux.sh --install again to update it.

🐛 Fixes

• --double-frames could freeze on Linux (Vulkan, Wayland or X11). When a repeated frame was already late, the app rendered it but never showed it. A few of those could stall the test. Late repeats are now skipped before they are rendered. The direct KMS mode, which the Linux results so far were measured with, was not affected.
• Bad command-line numbers are rejected. Values such as --fps nan, an empty value or a negative --duration used to slip through; out-of-range --seed, --gpu, --pattern and --spike-frames values are now reported instead of misbehaving.
• CSV logs keep display times after skipped frames. When frames were skipped (for example while the window was minimized), the next frames could lose their display_time_s values.
• Smaller fixes: an unexpected Vulkan error now ends the run cleanly instead of rendering to an invalid image, and the direct KMS mode no longer leaks memory when it fails to start.

The note from 1.0.0 still applies: the macOS build has not yet been tested on a real Mac with an Adaptive-Sync monitor.

Bzzrt 1.1.0

Bzzrt 1.1.0 is the first release under the new name. The project was previously called Synchora. The tests and measurements are unchanged from 1.0.1.

⬇️ Downloads

System	File	Start
🪟 Windows 10/11 (x64)	bzzrt-1.1.0-windows-x64.zip	double-click vrrdiag.exe on the monitor you want to test
🐧 Linux (x86_64, glibc 2.34+)	bzzrt-1.1.0-linux-x86_64.tar.gz	./vrrdiag-launch
🍎 macOS 12+ (Apple silicon)	bzzrt-1.1.0-macos-arm64.zip	open Bzzrt.app (first time: right-click → Open; macOS 15: System Settings → Privacy & Security → Open Anyway)

Check the files against SHA256SUMS.

🔤 Renamed from Synchora

• App name. The window title, --version, --help, the overlay and the saved report all say Bzzrt.
• Platform packaging:
  • macOS: the app is Bzzrt.app (bundle ID io.github.prajwaljb.bzzrt), and logs go to ~/Documents/Bzzrt.
  • Linux: the app-menu entry is Bzzrt. Run ./package-linux.sh --install again to replace the old entry.
• Saved VRR ranges now live in ~/.config/bzzrt, %APPDATA%\Bzzrt or ~/Library/Application Support/Bzzrt. Ranges saved by Synchora are still read and are moved to the new folder the next time a range is saved.
• Repository. It moved to Prajwaljb/Bzzrt, and old Synchora links redirect.
• Unchanged. The command is still vrrdiag, and all options work as before.

The note from 1.0.0 still applies: the macOS build has not yet been tested on a real Mac with an Adaptive-Sync monitor.

Bzzrt 1.0.1 (released as Synchora)

Renamed: this project is now called Bzzrt. This release was published under its old name, Synchora, so the downloads and the app inside them still say Synchora. Newer releases use the Bzzrt name.

Synchora 1.0.1 is a maintenance release: the program is unchanged from 1.0.0, while the documentation, packaging and licence are updated.

⬇️ Downloads

System	File	Start
🪟 Windows 10/11 (x64)	synchora-1.0.1-windows-x64.zip	double-click vrrdiag.exe on the monitor you want to test
🐧 Linux (x86_64, glibc 2.34+)	synchora-1.0.1-linux-x86_64.tar.gz	./vrrdiag-launch
🍎 macOS 12+ (Apple silicon)	synchora-1.0.1-macos-arm64.zip	open Synchora.app (first time: right-click → Open; macOS 15: System Settings → Privacy & Security → Open Anyway)

Check the files against SHA256SUMS.

🔧 Changes

• MIT licence. Every package now includes the LICENSE file.
• Linux app menu. The entry is now called Synchora, matching the window title and the macOS app. Run ./package-linux.sh --install again to update an existing entry.
• --help on Windows. It now states that --gpu defaults to the GPU driving the monitor.
• README and QUICKSTART now match the program:
  • the test list includes stable90;
  • the Windows low-refresh check runs seven steps;
  • ESC stops a running check, and quits on the start screen;
  • TAB in the advanced test bench returns to the guided check;
  • the KDE setting is under Display & Monitor;
  • a seed reproduces the same frame-time sequence on macOS as well.
• New README header with a banner drawn in the app's own style.

Everything in 1.0.0 still applies, including the note that the macOS build has not yet been tested on a real Mac with an Adaptive-Sync monitor.

Bzzrt 1.0.0 (released as Synchora)

Renamed: this project is now called Bzzrt. This release was published under its old name, Synchora, so the downloads and the app inside them still say Synchora. Newer releases use the Bzzrt name.

Synchora 1.0.0 supports any variable refresh rate monitor on Windows, Linux and macOS. It separates panel-side flicker from frame pacing problems on the computer.

⬇️ Downloads

System	File	Start
🪟 Windows 10/11 (x64)	synchora-1.0.0-windows-x64.zip	double-click vrrdiag.exe on the monitor you want to test
🐧 Linux (x86_64, glibc 2.34+)	synchora-1.0.0-linux-x86_64.tar.gz	./vrrdiag-launch
🍎 macOS 12+ (Apple silicon)	synchora-1.0.0-macos-arm64.zip	open Synchora.app (first time: right-click → Open; macOS 15: System Settings → Privacy & Security → Open Anyway)

Check the files against SHA256SUMS.

✨ What's new

🖥️ Any monitor, not just 48-200 Hz

• The VRR range is read from the monitor itself. Sources:
  • the EDID's FreeSync data block;
  • the DisplayID Adaptive-Sync block;
  • the HDMI VRR range;
  • the display range limits;
  • on macOS, the range the system reports.
• You can also enter your own range (R). The detected range and yours are kept side by side, A switches between them, and both are remembered per monitor. Detection is not always right: EDID range limits, FreeSync Standard/Extended modes and HDMI-vs-DP ranges can differ from the real range.
• If nothing is detected and you haven't entered a range, the check asks before it starts. --vrr-min, --vrr-max and --lfc-threshold set it from the command line.
• The eight tests are built from that range: in range, just above the minimum, below it, far below it, and crossing it. A 48-200 Hz monitor gets the same tests as before.
• The start screen says whether LFC is possible (maximum ≥ 2× minimum). For narrow-range monitors (e.g. 48-75 Hz), the conclusion explains that flicker below the minimum is a limit of the range, not a fault.
• The check notices when the display mode runs below the monitor's maximum (e.g. a 144 Hz monitor set to 60 Hz) and tells you to raise it.
• The Windows low-refresh test picks a suitable display mode for any minimum.

🍎 macOS (new)

• A native Metal app for Apple silicon, macOS 12+.
• Native fullscreen, timing from MTLDrawable.presentedTime, and the variable refresh range that macOS reports.

🔁 Frame doubling experiment everywhere

• --double-frames now works with Vulkan (Wayland/X11) and Direct3D too, not only with --api kms.

🧩 Also

• --version.
• Reports and CSV headers record the range and where it came from.
• The window title reads "Synchora".

📝 Notes

• macOS: built and smoke-tested on GitHub's macOS runners. The shader compiles and the app runs, but this version has not been tested on a real Mac with an Adaptive-Sync monitor yet. Reports are welcome.
• Linux: built on Ubuntu 22.04, so it runs on most current distributions. It needs a Vulkan driver.
• Software cannot see what the panel itself does. The monitor's own refresh-rate readout (OSD) is the final word.