I'm a big fan of VidChecker for file-based worksflows. Having demo'ed both Intera Systems Baton and Tektronix Cerify in the past I find VidChecker to be the better solution (who thought Crawley would put Tektronix in second place in any area?!). Hugh and I did a podcast on file-based QC last year.
So I keep a copy of VidChecker server on my laptop running in a VM for demo purposes. On Monday I got v.5.7.2 which brings the following;
- Test and correction of multiple loudness modes concurrently (I-mode, S-mode and M-mode)
- Multiple mono audio track detection
- Update of DPP templates to DPP spec 4.1
- Additional visual drop-out detections
- Test for breaks in 2:3 cadence pattern
- MXF timecode continuity check
- Minor improvements to UI (e.g. report options)
I would never have figured out the solution, but apparently a recent Windows update means that if you ever use "localhost" assuming it will translate to either 127.0.0.1 (local loopback IP address) OR your local IP address you'll be out of luck (unless your DNS does the right thing, but I think that's unlikely!). So edit the hosts file;
Once in the file remove the hash from the line below and save;
# 127.0.0.1 localhost
Which begs the question; why is it hash'ed out by default?