Odd thing I noticed with Dorico and adding markers. If you select a frame in a video and then click add Marker at that frame, it at times seems to open the “Add Marker” dialog with the timecode set to 1 frame less than the timecode displayed in the video. For example, if I stop on 01:00:27:14 in the video, when I click on add marker for that location, the dialog opens up with the timecode set to 01:00:27:13. I’ve tried this now on both Mac & PC. Note that this does not necessarily happen every time. It seems fairly random. It would also be very useful if the app could display exactly where in the measure the marker is falling regarding the beats and/or how many ticks it may be off the beat. This would obviously helpful if adjustments need to be made.
An odd thing I noticed after trying out a few different videos synced to a flow in Dorico. Anytime you add a marker with either the plus sign or shortcut, the timecode for the marker always seems to be set at 1 frame less than what the timecode in the video is showing for that frame. For example, I stop the video on frame 01:00:16:08 and add a marker, it sets the marker to 01:00:16:07. Sometimes you can change it manually, and sometimes it won’t let you.
Anyone ever notice this before?
Looking at a video with BITC, 25 FPS I notice that the Dorico “add marker” dialog and the stopped BITC in the video are off by a single frame maybe 60% of the time? Rarely more than a frame but I have seen as many as 6.
Since we are here, I don’t understand what “valid range” means in that dialog.
For me at least, I haven’t been too bothered. I’m consciously trying not to Mickey Mouse, so…
I’ve been looking at this using a 29.97fps video with burned in timecode, and I also find that the variance is essentially in the region of only 1 frame. I suspect this comes down to some kind of floating point accuracy issue somewhere in the chain of calculations used to convert between the internal time and the timecode display.
However, the display in the Add Marker dialog always corresponds exactly (i.e. with zero variance) to the timecode displayed in Dorico’s own transport, so its own calculations are internally consistent.
It is of course not “locked” in any meaningful way to the video: the video transport and Dorico’s transport are independent.