Recherche avancée

Sur d’autres sites (9666)

• ffmpeg determine correct codec to use

  6 janvier 2015, par nha

  I am trying to use .y4m files that I feed into Chrome for playing.
  This is the only format that I can use.

  I have a set of .y4m files that are working for my use case, taken from here.
  For example let’s say that I use the file mobile_qcif_7.5fps.y4m.

  I also have a .mp4 file (specifically the sample small.mp4 file from techslides ). I know how to convert small.mp4 to small.y4m with the following command :

  ffmpeg -y -i small.mp4 small.y4m

  I would like the resulting file to be accepted by Chrome, just like the other file.
  What options should I use (and how to find them) ?

  Additional information

  ffprobe gives :

  $ ffprobe small.y4m 
  
  avprobe version 0.8.13-6:0.8.13-0ubuntu0.13.10.1, Copyright (c) 2007-2014 the Libav developers
  
    built on Jul 15 2014 13:48:35 with gcc 4.8.1
  
  [yuv4mpegpipe @ 0x23160c0] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, yuv4mpegpipe, from 'small.y4m':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0.0: Video: rawvideo, yuv420p, 560x320, 30 fps, 30 tbr, 30 tbn, 30 tbc
  
  
  
  
  
  $ ffprobe mobile_qcif_7.5fps.y4m
  
  avprobe version 0.8.13-6:0.8.13-0ubuntu0.13.10.1, Copyright (c) 2007-2014 the Libav developers
  
    built on Jul 15 2014 13:48:35 with gcc 4.8.1
  
  [yuv4mpegpipe @ 0x1e080c0] max_analyze_duration reached
  
  [yuv4mpegpipe @ 0x1e080c0] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, yuv4mpegpipe, from 'mobile_qcif_7.5fps.y4m':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0.0: Video: rawvideo, yuv420p, 176x144, PAR 128:117 DAR 1408:1053, 7.50 fps, 7.50 tbr, 7.50 tbn, 7.50 tbc

  OS : I am using ffmpeg in Ubuntu 13.10 from the default repository : I ran sudo apt-get install ffmpeg libavcodec-extra-53

  Complete console output

  $ ffmpeg -y -i small.mp4 small.y4m
  
  ffmpeg version 0.8.13-6:0.8.13-0ubuntu0.13.10.1, Copyright (c) 2000-2014 the Libav developers
  
    built on Jul 15 2014 13:48:35 with gcc 4.8.1
  
  *** THIS PROGRAM IS DEPRECATED ***
  
  This program is only provided for compatibility and will be removed in a future release. Please use avconv instead.
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'small.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42isomavc1
  
      creation_time   : 2010-03-20 21:29:11
  
      encoder         : HandBrake 0.9.4 2009112300
  
    Duration: 00:00:05.56, start: 0.000000, bitrate: 551 kb/s
  
      Stream #0.0(und): Video: h264 (Constrained Baseline), yuv420p, 560x320, 465 kb/s, 30 fps, 30 tbr, 90k tbn, 60 tbc
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
      Stream #0.1(eng): Audio: aac, 48000 Hz, mono, s16, 83 kb/s
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
  [buffer @ 0x7274e0] w:560 h:320 pixfmt:yuv420p
  
  Output #0, yuv4mpegpipe, to 'small.y4m':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42isomavc1
  
      creation_time   : 2010-03-20 21:29:11
  
      encoder         : Lavf53.21.1
  
      Stream #0.0(und): Video: rawvideo, yuv420p, 560x320, q=2-31, 200 kb/s, 90k tbn, 30 tbc
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
  Stream mapping:
  
    Stream #0.0 -> #0.0
  
  Press ctrl-c to stop encoding
  
  frame=  166 fps=  0 q=0.0 Lsize=   43576kB time=5.53 bitrate=64513.5kbits/s    
  
  video:0kB audio:0kB global headers:0kB muxing overhead inf%

  Head of the files

  Not sure if this is relevant, but the text content of both files begin like that :

  mobile_qcif_7.5fps.y4m
  
  YUV4MPEG2 W176 H144 F15:2 Ip A128:117
  
  FRAME
  
  
  
  small.y4m (invalid)
  
  YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420mpeg2 XYSCSS=420MPEG2
  
  FRAME

  Additional experiment

  Taking the sample mobile_qcif_7.5fps.y4m, turning it into a .mp4 file and then back into a .y4m produces an invalid file (at least for Chrome).

  Answer to comments in the answer of @SirDarius

  Following the suggestion of @SirDarius ; I tried the following commands.
  They failed to produce a valid file.

  # [COMMAND]   # [RESULT] [HEADER]
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -pix_fmt yuv444p -y small_yuv444p.y4m   # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C444 XYSCSS=444
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -pix_fmt yuv422p -y small_yuv422p.y4m   # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C422 XYSCSS=422
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -pix_fmt yuv420p -y small_yuv420p.y4m   # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420mpeg2 XYSCSS=420MPEG2
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -pix_fmt yuv411p -y small_yuv411p.y4m   # KO   YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C411 XYSCSS=411
  
  
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p9 -y small_yuv420p9.y4m   # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420p9 XYSCSS=420P9
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p12 -y small_yuv420p12.y4m # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420p12 XYSCSS=420P12
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p14 -y small_yuv420p14.y4m # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420p14 XYSCSS=420P14
  
  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -strict -1 -pix_fmt yuv420p16 -y small_yuv420p16.y4m # KO YUV4MPEG2 W560 H320 F15:2 Ip A0:0 C420p16 XYSCSS=420P16

  When trying other formats (like yuv420p12be, which was in the output of -pix_fmts), I had the following output (hence my previous trials) :

  $  ffmpeg -i small.mp4 -vf fps=7.5 -an -c:v rawvideo -f yuv4mpegpipe -pix_fmt yuv420p12be -y small_yuv420p12be.y4m 
  
  ffmpeg version N-68884-g3ebd76a Copyright (c) 2000-2015 the FFmpeg developers
  
    built on Jan  6 2015 11:03:21 with gcc 4.8 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  
    configuration: 
  
    libavutil      54. 16.100 / 54. 16.100
  
    libavcodec     56. 19.100 / 56. 19.100
  
    libavformat    56. 18.100 / 56. 18.100
  
    libavdevice    56.  3.100 / 56.  3.100
  
    libavfilter     5.  6.100 /  5.  6.100
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x21d0220] overread end of atom 'colr' by 1 bytes
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'small.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42isomavc1
  
      creation_time   : 2010-03-20 21:29:11
  
      encoder         : HandBrake 0.9.4 2009112300
  
    Duration: 00:00:05.57, start: 0.000000, bitrate: 551 kb/s
  
      Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(tv, bt709), 560x320, 465 kb/s, 30 fps, 30 tbr, 90k tbn, 60 tbc (default)
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
        encoder         : JVT/AVC Coding
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 83 kb/s (default)
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
  [yuv4mpegpipe @ 0x21d8180] ERROR: yuv4mpeg can only handle yuv444p, yuv422p, yuv420p, yuv411p and gray8 pixel formats. And using 'strict -1' also yuv444p9, yuv422p9, yuv420p9, yuv444p10, yuv422p10, yuv420p10, yuv444p12, yuv422p12, yuv420p12, yuv444p14, yuv422p14, yuv420p14, yuv444p16, yuv422p16, yuv420p16 and gray16 pixel formats. Use -pix_fmt to select one.
  
  Output #0, yuv4mpegpipe, to 'small_yuv420p12be.y4m':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42isomavc1
  
      encoder         : Lavf56.18.100
  
      Stream #0:0(und): Video: rawvideo ([12][11]3Y / 0x59330B0C), yuv420p12be, 560x320, q=2-31, 200 kb/s, 7.50 fps, 7.50 tbn, 7.50 tbc (default)
  
      Metadata:
  
        creation_time   : 2010-03-20 21:29:11
  
        encoder         : Lavc56.19.100 rawvideo
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
  
  Could not write header for output file #0 (incorrect codec parameters ?): Input/output error

  After that, I also tried to edit with an hexadecimal editor (bless) the small_yuv420p.y4m file. I replace C420mpeg2 by C420, and the file was accepted by Chrome.
  What does the number in 420p[number] correspond to ? It is not explained there.
  Is there any way to make ffmpeg output this kind of header files ?

  @SirDarius, thank you again for your help.

  The question

  (in case you forgot after this text blob)

  How can I convert the small.mp4 into a small.y4m file that has the same properties as the mobile_qcif_7.5fps.y4m file ?

• How to make that video module can generate readable files for the module JW Player ?

  4 janvier 2015, par Dvex

  I use Drupal 7.x with Video Module, Video Pressets for FFMPEG and JW Player.
  I install FFMPEG with this Guide : https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu in Ubuntu 14.04

  I’m using jQuery 1.8

  I downloaded the files that the JW Player module requires and renamed some files, as the guide tells me.

  I set the video module so you can use FFMPEG and established the necessary pressets (FLV, MP4 and WebM) for any browser (web and mobile).

  I changed the default settings of these pressets. I put check the option : Force one-pass Encoding. Because if not me error message :

  PHPVideoToolkit error: Execute error. It was not possible to encode "/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4" as FFmpeg returned an error. Note, however the error was encountered on the second pass of the encoding process and the first pass appear to go fine. The error is with the video codec of the input file. FFmpeg reports the error to be "Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height".
  
  
  
  /usr/bin/ffmpeg -i '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4' -strict experimental -vcodec 'h264' -acodec 'aac' -vprofile 'baseline' -ac '2' -pass '1' -passlogfile '/tmp/1420389438-54a96c3eda9fc-multipass'  -y /tmp/1420389438-54a96c3eda8c1.mp4
  
  ffmpeg version 1.2.6-7:1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    53.  5.103 / 53.  5.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      creation_time   : 2013-09-12 17:30:22
  
    Duration: 00:00:39.32, start: 0.000000, bitrate: 3190 kb/s
  
      Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 720x480 [SAR 40:33 DAR 20:11], 2991 kb/s, 29.97 fps, 29.97 tbr, 29970 tbn, 59.94 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  [libx264 @ 0x164dec0] using SAR=40/33
  
  [libx264 @ 0x164dec0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x164dec0] profile Constrained Baseline, level 3.0
  
  [libx264 @ 0x164dec0] 264 - core 142 r2389 956c8d8 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=1:0:0 analyse=0x1:0 me=dia subme=2 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to '/tmp/1420389438-54a96c3eda8c1.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      encoder         : Lavf54.63.104
  
      Stream #0:0(eng): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 720x480 [SAR 40:33 DAR 20:11], q=-1--1, pass 1, 11988 tbn, 29.97 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, fltp, 128 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libx264)
  
    Stream #0:1 -> #0:1 (aac -> aac)
  
  Press [q] to stop, [?] for help
  
  frame=   88 fps=0.0 q=29.0 size=     483kB time=00:00:02.96 bitrate=1335.6kbits/s dup=1 drop=0    
  
  frame=  190 fps=189 q=29.0 size=    1916kB time=00:00:06.33 bitrate=2477.6kbits/s dup=1 drop=0    
  
  frame=  289 fps=192 q=29.0 size=    3001kB time=00:00:09.64 bitrate=2549.5kbits/s dup=1 drop=0    
  
  frame=  395 fps=196 q=29.0 size=    3732kB time=00:00:13.31 bitrate=2296.7kbits/s dup=1 drop=0    
  
  frame=  495 fps=197 q=29.0 size=    4481kB time=00:00:16.66 bitrate=2203.1kbits/s dup=1 drop=0    
  
  frame=  591 fps=196 q=29.0 size=    5152kB time=00:00:19.98 bitrate=2111.4kbits/s dup=1 drop=0    
  
  frame=  690 fps=196 q=29.0 size=    6329kB time=00:00:23.01 bitrate=2252.4kbits/s dup=1 drop=0    
  
  frame=  790 fps=197 q=29.0 size=    7184kB time=00:00:26.32 bitrate=2235.6kbits/s dup=1 drop=0    
  
  frame=  890 fps=197 q=29.0 size=    8532kB time=00:00:29.73 bitrate=2350.3kbits/s dup=1 drop=0    
  
  frame= 1000 fps=199 q=29.0 size=    9398kB time=00:00:33.42 bitrate=2303.0kbits/s dup=1 drop=0    
  
  frame= 1106 fps=200 q=29.0 size=   10423kB time=00:00:37.01 bitrate=2306.8kbits/s dup=1 drop=0    
  
  frame= 1178 fps=199 q=-1.0 Lsize=   11404kB time=00:00:39.31 bitrate=2376.1kbits/s dup=1 drop=0
  
  video:10752kB audio:618kB subtitle:0 global headers:0kB muxing overhead 0.302603%
  
  [libx264 @ 0x164dec0] frame I:87    Avg QP:24.23  size: 21823
  
  [libx264 @ 0x164dec0] frame P:1091  Avg QP:25.90  size:  8351
  
  [libx264 @ 0x164dec0] mb I  I16..4: 50.9%  0.0% 49.1%
  
  [libx264 @ 0x164dec0] mb P  I16..4: 14.8%  0.0%  0.0%  P16..4: 51.3%  0.0%  0.0%  0.0%  0.0%    skip:33.9%
  
  [libx264 @ 0x164dec0] coded y,uvDC,uvAC intra: 43.9% 38.7% 10.2% inter: 23.0% 14.4% 0.8%
  
  [libx264 @ 0x164dec0] i16 v,h,dc,p: 31% 39% 19% 11%
  
  [libx264 @ 0x164dec0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 44% 14%  5%  4%  4%  4%  4%  4%
  
  [libx264 @ 0x164dec0] i8c dc,h,v,p: 57% 22% 17%  4%
  
  [libx264 @ 0x164dec0] kb/s:2240.77
  
  /usr/bin/ffmpeg -i '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4' -strict experimental -vcodec 'h264' -acodec 'aac' -vprofile 'baseline' -ac '2' -pass '2' -passlogfile '/tmp/1420389438-54a96c3eda9fc-multipass'  -y /tmp/1420389438-54a96c3eda8c1.mp4
  
  ffmpeg version 1.2.6-7:1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    53.  5.103 / 53.  5.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/www/html/sites/default/files/private/videos/original/reel para web en loop_2.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      creation_time   : 2013-09-12 17:30:22
  
    Duration: 00:00:39.32, start: 0.000000, bitrate: 3190 kb/s
  
      Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 720x480 [SAR 40:33 DAR 20:11], 2991 kb/s, 29.97 fps, 29.97 tbr, 29970 tbn, 59.94 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  [libx264 @ 0x161eec0] using SAR=40/33
  
  [libx264 @ 0x161eec0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x161eec0] constant rate-factor is incompatible with 2pass.
  
  Output #0, mp4, to '/tmp/1420389438-54a96c3eda8c1.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      Stream #0:0(eng): Video: h264, yuv420p, 720x480 [SAR 40:33 DAR 20:11], q=-1--1, pass 2, 90k tbn, 29.97 tbc
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
      Stream #0:1(eng): Audio: none, 48000 Hz, stereo, fltp, 128 kb/s
  
      Metadata:
  
        creation_time   : 2013-09-12 17:30:22
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libx264)
  
    Stream #0:1 -> #0:1 (aac -> aac)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  When I save a node and add its corresponding video, the module generates the 3 files with their respective formats. But when thrown at the JW Player module, only plays FLV in every browser.
  But not the MP4 or WebM.

  I checked the log and status report and all I get in order.

  So I assume that the MP4 and WebM formats generated are not what the JW Player waiting.

  Does anyone have the solution to this problem ? I tried to recompile FFMPEG with more codecs but it does not solve the problem.

  This is my FFMPEG Configuration :

  ffmpeg version 1.2.6-1~trusty1 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --arch=amd64 --disable-stripping --enable-avresample --enable-pthreads --enable-runtime-cpudetect --extra-version='7:1.2.6-1~trusty1' --libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --enable-bzlib --enable-libdc1394 --enable-libfreetype --enable-frei0r --enable-gnutls --enable-libgsm --enable-libmp3lame --enable-librtmp --enable-libopencv --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvpx --enable-zlib --enable-gpl --enable-postproc --enable-libcdio --enable-x11grab --enable-libx264 --shlibdir=/usr/lib/x86_64-linux-gnu --enable-shared --disable-static

• Dreamcast SD Adapter and DreamShell

  31 décembre 2014, par Multimedia Mike — Sega Dreamcast

  Nope ! I’m never going to let go of the Sega Dreamcast hacking. When I was playing around with Dreamcast hacking early last year, I became aware that there is such a thing as an SD card adapter for the DC that plugs into the port normally reserved for the odd DC link cable. Of course I wanted to see what I could do with it.

  The primary software that leverages the DC SD adapter is called DreamShell. Working with this adapter and the software requires some skill and guesswork. Searching for these topics tends to turn up results from various forums where people are trying to cargo-cult their way to solutions. I have a strange feeling that this post might become the unofficial English-language documentation on the matter.

  Use Cases
  What can you do with this thing ? Undoubtedly, the primary use is for backing up (ripping) the contents of GD-ROMs (the custom optical format used for the DC) and playing those backed up (ripped) copies. Presumably, users of this device leverage the latter use case more than the former, i.e., download ripped games, load them on the SD card, and launch them using DreamShell.

  However, there are other uses such as multimedia playback, system exploration, BIOS reprogramming, high-level programming, and probably a few other things I haven’t figured out yet.

  Delivery
  I put in an order via the dc-sd.com website and in about 2 short months, the item arrived from China. This marked my third lifetime delivery from China and curiously, all 3 of the shipments have pertained to the Sega Dreamcast.

  
  

  

  Click for larger image

  
  

  I thought it was very interesting that this adapter came in such complete packaging. The text is all in Chinese, though the back states “Windows 98 / ME / 2000 / XP, Mac OS 9.1, LINUX2.4”. That’s what tipped me off that they must have just cannibalized some old USB SD card readers and packaging in order to create these. Closer inspection of the internals through the translucent pink case confirms this.

  Usage
  According to its change log, DreamShell has been around for a long time with version 1.0.0 released in February of 2004. The current version is 4.0.0 RC3. There are several downloads available :

  1. DreamShell 4.0 RC 3 CDI Image
  2. DreamShell 4.0 RC 3 + Boot Loader
  3. DreamShell 4.0 RC 3 + Core CDI image

  Option #2 worked for me. It contains a CDI disc image and the DreamShell files in a directory named DS/.

  Burn the CDI to a CD-R in the normal way you would burn a bootable Dreamcast disc from a CDI image. This is open-ended and left as an exercise to the reader, since there are many procedures depending on platform. On Linux, I used a small script I found once called burncdi-dc.sh.

  Then, copy the contents of the DS/ folder to an SD card. As for filesystem, FAT16 and FAT32 are both known to work. The files in DS/ should land in the root of the SD card ; the folder DS/ should not be in the root.

  Plug the SD card into the DC SD adapter and plug the adapter in the link cable port on the back of the Dreamcast. Then, boot the disc. If it works, you will see this minor corruption of the usual Sega licensing screen :

  
  
  

  Then, there will be a brief white-on-black text screen that explains the booting process :
  

  
  
  

  Then, there will be the main DreamShell logo :

  
  
  

  Finally, you will land on the DreamShell main desktop :

  
  
  

  Skepticism
  At first, I was supremely skeptical of the idea that this SD adapter could perform speedily enough to play games reasonably. This was predicated on the observation that my DC coder’s cable that I used to use for homebrew development could not transfer faster than 115200 bits/second, amounting to about 11 kbytes/sec. I assumed that this was a fundamental limitation of the link port.

  In fact, I ripped a few of my Dreamcast discs over a decade ago and still have those rips lying around. So I copied the ISO image of Resident Evil : Code Veronica — the game I personally played most on the DC — to the SD card (anywhere works) and used the “ISO loader” icon seen on the desktop above to launch the game.

  It works :

  
  
  

  The opening FMV plays at full speed. Everything loads as fast as I remember. I was quite surprised.

  Digression : My assumptions about serial speeds have often been mistaken. 10 years ago, I heard stories about how we would soon be able to watch streaming video on our cell phones. I scoffed because I thought the 56K limitation of dialup modems was some sort of fundamental speed-of-light type of limitation for telephony bandwidth, wired or wireless.

  The desktop menu also includes a ‘speedtest’ tool that profiles the write and read performance of your preferred storage medium. For my fastest SD card (a PNY 2 GB card) :

  
  
  

  This is probably more representative of the true adapter bandwidth as reading and writing is a good deal faster through more modern interfaces on PC and Mac with this same card.

  Look at the other options on the speedtest console. Hard drive ? Apparently, it’s possible, but it requires a good deal more hardware hacking than just purchasing this SD adapter.

  Ripping
  As you can see from the Resident Evil screenshot, playing games works quite nicely. How about ripping ? I’m pleased to say that DreamShell has a beautiful ripping interface :

  
  
  

  Enter a name for the disc (or read the disc label), select the storage medium, and let it, well, rip. It indicates which track it’s working on and the Sega logo acts as a progress bar, shading blue as the track rip progresses.

  I’m finally, efficiently, archiving that collection of Sega Dreamcast demo discs ; I’m hoping they’ll eventually find a home at the Internet Archive. How is overall ripping performance ? Usually about 38-40 minutes to rip a full 900-1000 MB. That certainly beats the 27-28 hours that were required when I performed the ripping at 11 kbytes/sec via the DC coders cable.

  All is well until I get a sector reading error :

  
  
  

  That’s when it can come in handy to have 3 DC consoles (see ?! not crazy !).

  Other Uses
  There’s a file explorer. You can browse the filesystem of the SD card, visual memory unit, or the CD portion of the GD-ROM (would be more useful if it accessed the GD area). There are FFmpeg files included. So I threw a random Cinepak file and random MPEG-1 file at it to see what happens. MPEG-1 didn’t do anything, but this Cinepak file from some Sierra game played handily :

  
  
  

  If you must enter strings, it helps to have a Dreamcast keyboard (which I do). Failing that, here’s a glimpse of the onscreen keyboard that DreamShell equips :

  
  
  

  Learning to use it is a game in itself.

  There is an option of installing DreamShell in the BIOS. I did not attempt this. I don’t know if it’s possible (not like there’s a lot of documentation)– perhaps a custom BIOS modchip is needed. But here’s what the screen looks like :

  
  
  

  There is also a plain console to interact with (better have a physical keyboard). There are numerous file manipulation commands and custom system interaction commands. I see one interesting command called ‘addr’ that looks useful for dumping memory regions to a file.

  A Lua language interpreter is also built in. I would love to play with this if I could ascertain whether DreamShell provided Dreamcast-specific APIs.

  Tips And Troubleshooting
  I have 3 Dreamcast consoles, affectionately named Terran, Protoss, and Zerg after the StarCraft II stickers with which they are adorned. Some seem to work better than others. Protoss seemed to be able to boot the DreamShell disc more reliably than the others. However, I was alarmed when it couldn’t boot one morning when it was churning the previous day.

  I think the problem is that it was just cold. That seemed to be the issue. I put in a normal GD-ROM and let it warm up on that disc for awhile and then DreamShell booted fine. So that’s my piece of cargo-culting troubleshooting advice.