Loading...
 

VidSync News

Just a quick update, since things have been stable for a while

Jason Neuswanger Monday April 27, 2020

I know that when I'm looking into a new piece of software, I see a blog that hasn't been updated in a few years and wonder, "Does it still work?"

I'm updating this just to let people know that VidSync is still working just fine, as of macOS version 10.15.1 (Catalina) in mid 2020, and there's nothing on the horizon to suggest that will change. I am still checking it with each new OS version, and if something breaks I'll be quick to fix it.

There haven't been any updates to the program in four years because nothing has broken that would require an urgent update. I have collected a list of minor new feature requests and improvements to be made at some point, but I'm not sure how soon that will happen.

I am still happy to hear about projects for which you're using VidSync (or might plan to use it), and to answer any questions potential or current users might have about the program.

Another small update to 1.66

Jason Neuswanger Wednesday May 25, 2016
This update includes just minor but useful bug fixes. The annoying starting position of the floating synced-playback control panel has been fixed (it should now start in the top left corner of the screen as intended). More importantly, a recently introduced bug that was causing the program to hang for 2 to 15 seconds or so during certain tasks in certain videos has been fixed. These include resizing videos, calculating calibrations, and sometimes measuring points.

Tiny update to 1.64

Jason Neuswanger Wednesday March 23, 2016

I just posted another update with a minor improvement (version 1.64) over the big upgrades posted a couple weeks ago. Specificically, I changed the "reprojection error" reported for 3-D points to reflect the root mean square difference, across all cameras, between the input screen positions of a 3-D point and the expected screen positions based on back-calculating from the measured 3-D position. The previously reported reprojection error was the root of the sum of these squared differences (instead of the mean square), which reflected the same information but did not have the same intuitive meaning.

The consequence of this change is that reported reprojection errors will all be a bit smaller than they were before. This doesn't mean the measurements got more accurate; it's just a better error estimate. And I would stress that both the reprojection error and the PLD error are not indicators of real measurement error (with which they are only loosely correlated). Instead, they are primarily diagnostics to help pinpoint major calibration issues or mis-clicks during measurement.

This change only automatically affects new measurements. Old measurements will show their previous reprojection errors unless you recalculate the calibration on one of the videos, which forces all points to be recalculated.