[FFmpeg-trac] #1869(avcodec:new): Create uncompressed v210 in any container

FFmpeg trac at avcodec.org
Mon Oct 29 22:28:50 CET 2012


#1869: Create uncompressed v210 in any container
-----------------------------------+--------------------------------------
             Reporter:  ximmortal  |                     Type:  defect
               Status:  new        |                 Priority:  normal
            Component:  avcodec    |                  Version:  git-master
             Keywords:  v210       |               Blocked By:
             Blocking:             |  Reproduced by developer:  0
Analyzed by developer:  0          |
-----------------------------------+--------------------------------------
 Summary of the bug:
 I am trying to use ffmpeg to contain a raw v210 sequence of images in a
 container.  I've tried mov and avi, but both create a video that seems to
 shift the image around in quadrants.  Hopefully I am just using the wrong
 command line option.  It seems to me that the v210 is more of a pixel
 format than a "codec" which may be why I am getting the unexpected
 results.  When I specify -vcodec v210 on the input, I notice that the
 ffmpeg statistics show only 333 frames processed (of which is really 500).
 I think it is getting to 333 because it is trying to read a frame
 expecting 16-bit per component for 4:2:2 which would be 8294400 bytes per
 frame of a 1920x1080 image, a v210 frame should be 5529600 bytes per frame
 for a 1920x1080 image.

 How to reproduce:
 {{{
 % ffmpeg -s 1920x1080 -vcodec v210 -i
 ../x264-snapshot-20121026-2245/1920x1080_ducks_v210.yuv -vcodec copy
 test.mov
 ffmpeg version N-46081-g5f9cbad Copyright (c) 2000-2012 the FFmpeg
 developers
   built on Oct 27 2012 15:14:01 with gcc 4.6 (Ubuntu/Linaro
 4.6.3-1ubuntu5)
   configuration: --prefix=/home/shane/Development/ffmpeg
   libavutil      52.  1.100 / 52.  1.100
   libavcodec     54. 69.100 / 54. 69.100
   libavformat    54. 35.100 / 54. 35.100
   libavdevice    54.  3.100 / 54.  3.100
   libavfilter     3. 20.106 /  3. 20.106
   libswscale      2.  1.101 /  2.  1.101
   libswresample   0. 16.100 /  0. 16.100
 [rawvideo @ 0x1f08480] Estimating duration from bitrate, this may be
 inaccurate
 Input #0, rawvideo, from '../1920x1080_ducks_v210.yuv':
   Duration: N/A, start: 0.000000, bitrate: N/A
     Stream #0:0: Video: v210, yuv422p10le, 1920x1080, 25 tbr, 25 tbn, 25
 tbc
 File 'test.mov' already exists. Overwrite ? [y/N] y
 Output #0, mov, to 'test.mov':
   Metadata:
     encoder         : Lavf54.35.100
     Stream #0:0: Video: v210 (v210 / 0x30313276), yuv422p10le, 1920x1080,
 q=2-31, 12800 tbn, 25 tbc
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
 Press [q] to stop, [?] for help
 Truncating packet of size 8294400 to 7948801ime=00:00:12.96
 bitrate=1660800.0kbits/s
 frame=  334 fps= 18 q=-1.0 Lsize= 2700003kB time=00:00:13.32
 bitrate=1660542.6kbits/s
 video:2700000kB audio:0kB subtitle:0 global headers:0kB muxing overhead
 0.000123%

 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1869>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list