You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of implementing this export is to keep universal support in mind for future archival use and re-muxing of the data, ideally which would mux TC values as SMPTE TC stream into the final video file Y4M/V210/FFV1 etc.
Thanks again to @atsampson for adding VITC to the suite!
Sony RCTC
Initial support in the .JSON metadata should be considered for Sony's Video8 & High8 RCTC (Rewritable Consumer TimeCode)
As Video/HiFi/PCM/TimeCode are all on different carriers this timecode could be extracted during initial decoding. (samples required)
It would be nice to have the .JSON have fields for this standard timecode format
0:35:01:15 03:45:51PM FEB 6 1996
Runtime - hours : minutes : seconds : frames
Time Of Date - hours : minutes : seconds MMM D YYYY
SMPTE LTC Inside ld-analyse
Add option to look for an LTC track if a .wav or .flac file is found with timecode then readout to counter.
<TBC-Name>_LTC.wav
The text was updated successfully, but these errors were encountered:
As we now have initial VITC timecode support, it would be valuable to flush this feature out.
Implimentation
VITC Export Information
Export of VITC data in a standard FFmpeg formatted .txt text document via ld-metadata-export
FFMPEG's filter standard export looks like the following:
The idea of implementing this export is to keep universal support in mind for future archival use and re-muxing of the data, ideally which would mux TC values as SMPTE TC stream into the final video file Y4M/V210/FFV1 etc.
Thanks again to @atsampson for adding VITC to the suite!
Sony RCTC
Initial support in the .JSON metadata should be considered for Sony's Video8 & High8 RCTC (Rewritable Consumer TimeCode)
As Video/HiFi/PCM/TimeCode are all on different carriers this timecode could be extracted during initial decoding. (samples required)
It would be nice to have the .JSON have fields for this standard timecode format
Runtime - hours : minutes : seconds : frames
Time Of Date - hours : minutes : seconds MMM D YYYY
SMPTE LTC Inside ld-analyse
Add option to look for an LTC track if a .wav or .flac file is found with timecode then readout to counter.
The text was updated successfully, but these errors were encountered: