It appears that the "system time" timecodes are not updated on every frame, even when 'Embed system time as timecode' is checked, and 'Frame Interval' is set to 1.
The timecodes routinely latch onto a certain value, so that several timecodes in a row will report the same system time.
To study this behavior, I recorded a video of a computer screen displaying the current time as an epoch timestamp in milliseconds, and, from the recorded .flv file, read back the timecodes from each video frame as well as the timecodes embedded as amf0 'onFI' events as recorded by FMLE.
You may consult the data I collected below:
A graph showing embedded timecodes above video time:
The complete data:
The FMLE-created video file used:
This data was collected on a 2008 MacBook.
Has anyone else seen behavior like this? I look forward to doing more tests, on different machines and with different settings, but because they're so laborious to compute, I thought I'd reach out first.
Unfortunately this is quite urgent, so I'm afraid I'll have to investigate other technologies. Any help is greatly appreciated, THANKS!
For what it's worth, frame rate appears to be a factor. I see this issue consistently at 30fps, but never at 24fps or 25fps, where the amf0 timecodes are fairly evenly spaced, at about the duration of one frame.
I'm using VP6 at 640x360, a Logitech C910, Mac OS 10.7.3, FMLE 220.127.116.11.32.
This behavior seems pathological to me. Has anyone else seen this?
Europe, Middle East and Africa