Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support timecodes #506

Open
3 tasks done
mifi opened this issue Nov 18, 2020 · 4 comments
Open
3 tasks done

Support timecodes #506

mifi opened this issue Nov 18, 2020 · 4 comments

Comments

@mifi
Copy link
Owner

mifi commented Nov 18, 2020

Timecode can be embedded in a file.

Possible features

  • Set custom time offset automatically to the read timecode when loading a file
  • View timecode in a file (stream info for video stream)
  • Edit timecode in a file (stream tag editor for video stream)

Separate stream

For example in GoPros

Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
Metadata:
  creation_time   : 2016-03-22T20:29:00.000000Z
  handler_name    : GoPro TCD
  timecode        : 00:36:32:10

Other example:

Stream #0:2(und): Data: none (rtmd / 0x646D7472), 736 kb/s (default)
Metadata:
  creation_time   : 2019-10-15T12:06:02.000000Z
  handler_name    : Timed Metadata Media Handler
  timecode        : 00:13:17:24

Inside video stream

See example files from this site

ffprobe -v error -show_frames -of json tc_25fps_01min.m2v | grep timecode

"side_data_type": "GOP timecode",
"timecode": "00:00:00:00"
"side_data_type": "GOP timecode",
"timecode": "00:00:00:10"
...

Separate audio track

Timecodes can also be a separate audio track with a special LTC encoded sound. See libltc

mifi added a commit that referenced this issue Nov 27, 2020
@Timvrakas
Copy link

I'm trying to ingest a bunch of GoPro video, which has a built in timecode. When I trim the video, it still shows the same starting timecode, even though the start of the clip has changed. Am I doing something wrong, or is this still a WIP?

@mifi
Copy link
Owner Author

mifi commented May 9, 2022

probably a shortcoming in ffmpeg. you could try with ffmpeg v5 and see if it's fixed

@alinsavix
Copy link

It looks like ffmpeg definitely does the wrong thing here (tested with 5.0), but it might be worth considering calculating the appropriate timecode for a given cut and adjusting it automatically when calling ffmpeg to do its thing. It would be a -very- useful feature.

@mifi
Copy link
Owner Author

mifi commented Sep 29, 2022

I wonder if ffmpeg ignores timecode when cutting only for some files or all files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants