[FFmpeg-trac] #3753(undetermined:new): '-timecode' & '-metadata' not working: not creating a stream (tmcd) in output MOV

[FFmpeg]

#3753: '-timecode' & '-metadata' not working: not creating a stream (tmcd) in
output MOV
-------------------------------------+-------------------------------------
             Reporter:  AgentJJ24    |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:
              Version:  2.2.4        |  undetermined
             Keywords:  mov,         |               Resolution:
  timecode, metadata                 |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by AgentJJ24):

 Replying to [comment:1 cehoyos]:
 > Is the problem you see reproducible with current FFmpeg git head?

 Yes.  Here is the output:

 {{{
 ffmpeg -i ./INPUT.mov -vcodec copy -acodec copy -timecode 01:02:03:04
 -metadata reel_name=ABCD1234 ./OUTPUT.mov
 ffmpeg version 2.2.git Copyright (c) 2000-2014 the FFmpeg developers
   built on Jul  1 2014 18:11:18 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
   configuration: --prefix=/home/captain/FFMPEG/ffmpeg_build --extra-
 cflags=-I/home/captain/FFMPEG/ffmpeg_build/include --extra-
 ldflags=-L/home/captain/FFMPEG/ffmpeg_build/lib
 --bindir=/home/captain/FFMPEG/bin --extra-libs=-ldl --enable-gpl --enable-
 libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame
 --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx
 --enable-libx264 --enable-nonfree --enable-x11grab
   libavutil      52. 90.101 / 52. 90.101
   libavcodec     55. 68.100 / 55. 68.100
   libavformat    55. 44.100 / 55. 44.100
   libavdevice    55. 13.101 / 55. 13.101
   libavfilter     4.  9.100 /  4.  9.100
   libswscale      2.  6.100 /  2.  6.100
   libswresample   0. 19.100 /  0. 19.100
   libpostproc    52.  3.100 / 52.  3.100
 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './INPUT.mov':
   Metadata:
     creation_time   : 2014-06-29 03:18:04
   Duration: 00:00:47.42, start: 0.000000, bitrate: 664 kb/s
     Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv,
 bt709), 854x480, 658 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 48k tbc
 (default)
     Metadata:
       creation_time   : 2014-06-29 03:18:04
       handler_name    : Apple Alias Data Handler
       encoder         : H.264
       timecode        : 00:00:00:00
     Stream #0:1(eng): Data: none (tmcd / 0x64636D74) (default)
     Metadata:
       creation_time   : 2014-06-29 03:18:27
       handler_name    : Apple Alias Data Handler
       timecode        : 00:00:00:00
 [mov @ 0x22155e0] Using AVStream.codec.time_base as a timebase hint to the
 muxer is deprecated. Set AVStream.time_base instead.
 Output #0, mov, to './OUTPUT.mov':
   Metadata:
     timecode        : 01:02:03:04
     reel_name       : ABCD1234
     encoder         : Lavf55.44.100
     Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), yuv420p, 854x480,
 q=2-31, 658 kb/s, 23.98 fps, 24k tbn, 24k tbc (default)
     Metadata:
       creation_time   : 2014-06-29 03:18:04
       handler_name    : Apple Alias Data Handler
       encoder         : H.264
       timecode        : 00:00:00:00
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
 Press [q] to stop, [?] for help
 frame= 1137 fps=0.0 q=-1.0 Lsize=    3824kB time=00:00:47.33 bitrate=
 661.8kbits/s
 video:3811kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: 0.361878%

 }}}

 > Do you think this is a regression (regressions are the main reason why
 tickets are important)?

 Yes, because this is suppose to be a very regular part of film
 postproduction workflows that have utilized it with no trouble in the
 past.

 Thank you!

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3753#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker