Recherche avancée

Sur d’autres sites (4273)

• Encoding a readable movie by QuickTime using FFMPEG

  3 octobre 2014, par itamarb

  I’m trying to encode an image sequence using the following command :

  ffmpeg.exe -i %d.png -f mp4 -vcodec h264 test.mp4

  However, QuickTime failed to open this file or sometimes play a black movie, while this movie plays great in VLC player. Any suggestions how to make it play well in QuickTime ?

  Here is the output :

  ffmpeg.exe -i %d.png -f mp4 -vcodec libx264 13.mp4
  
  ffmpeg version N-49044-g89afa63 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Jan 19 2013 20:36:06 with gcc 4.7.2 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
  
  isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab
  
  le-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libg
  
  sm --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --e
  
  nable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --e
  
  nable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc --en
  
  able-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable
  
  -libxavs --enable-libxvid --enable-zlib --enable-filter=frei0r
  
    libavutil      52. 15.100 / 52. 15.100
  
    libavcodec     54. 89.100 / 54. 89.100
  
    libavformat    54. 61.101 / 54. 61.101
  
    libavdevice    54.  3.102 / 54.  3.102
  
    libavfilter     3. 32.101 /  3. 32.101
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  [image2 @ 0221b940] max_analyze_duration 5000000 reached at 5000000 microseconds
  
  
  
  Input #0, image2, from '%d.png':
  
    Duration: 00:01:19.36, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: png, rgb24, 639x480, 25 fps, 25 tbr, 25 tbn, 25 tbc
  
  [libx264 @ 0221edc0] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE
  
  4.2 AVX
  
  [libx264 @ 0221edc0] profile High 4:4:4 Predictive, level 3.0, 4:4:4 8-bit
  
  [libx264 @ 0221edc0] 264 - core 129 r2230 1cffe9f - H.264/MPEG-4 AVC codec - Cop
  
  yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
  
  lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
  
  e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
  
  ma_qp_offset=4 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 in
  
  terlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b
  
  _bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecu
  
  t=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 '13.mp4':
  
    Metadata:
  
      encoder         : Lavf54.61.101
  
      Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv444p, 639x480, q=-1--1
  
  , 12800 tbn, 25 tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (png -> libx264)
  
  Press [q] to stop, [?] for help
  
  frame=   76 fps=0.0 q=28.0 size=       3kB time=00:00:00.96 bitrate=  22.3kbits/
  
  frame=  156 fps=155 q=28.0 size=       7kB time=00:00:04.16 bitrate=  14.7kbits/
  
  frame=  219 fps=145 q=28.0 size=      12kB time=00:00:06.68 bitrate=  14.1kbits/
  
  frame=  283 fps=141 q=28.0 size=      16kB time=00:00:09.24 bitrate=  14.2kbits/
  
  frame=  352 fps=140 q=28.0 size=      25kB time=00:00:12.00 bitrate=  17.4kbits/

• Revision 734c5ffa2c : Apply constrained partition search range to non-RD mode decision This commit en

  23 avril 2014, par Jingning Han

  Changed Paths :
   Modify /vp9/encoder/vp9_encodeframe.c

  
  
  Apply constrained partition search range to non-RD mode decision

  This commit enables a chessboard pattern for partition search. All
  the black blocks run regular partition search ranging from 8x8 to
  32x32. The rest white blocks take the nearby blocks’ information
  to adaptively decide the effective search range.

  The compression performance for rtc set at speed -5 is down by 1.5%.
  For pedestrian 1080p at speed -5, the runtime goes from 41594 ms to
  39697 ms, i.e., about 5% faster.

  Change-Id : Ia4b96e237abfaada487c743bca08fe1afd298685

• Is "begin" param dead in Youtube's *.c.youtube.com/videoplayback ?

  23 janvier 2013, par Minime

  I tested Youtube video download with begin param using ytdl, and realized that it's not working properly. Below is an URL with begin param. (It won't work on your side because it's session-IP address based.)

  http://r4---sn-o097znee.c.youtube.com/videoplayback?ratebypass=yes&cp=U0hUTVNOT19JTENONF9LSFNIOmtjaWozaFd5Vnhl&newshard=yes&source=youtube&ipbits=8&fexp=916600%2C906072%2C923114%2C914093%2C916626%2C920704%2C912806%2C922403%2C922405%2C929901%2C913605%2C925710%2C929104%2C929110%2C908493%2C920201%2C913302%2C919009%2C911116%2C926403%2C910221%2C901451&id=58dafac107cd7cae&key=yt1&mt=1358307193&gcr=us&ms=au&itag=46&upn=efQT2cDue5M&ip=xxxx&sparams=cp%2Cgcr%2Cid%2Cip%2Cipbits%2Citag%2Cratebypass%2Csource%2Cupn%2Cexpire&expire=1358331742&sver=3&mv=m&signature=C957313FEC2AC174F72CEFE52BF663ABAC8D0E4B.27F8485A36BE654CA25D3CA75A927D443523CA68&begin=12000

  I traced Youtube site by myself to see if there are any recent changes on their black boxed
  API. And I found that begin param is no longer put in videoplayback, but put in user_watch as below.

  http://www.youtube.com/user_watch?video_id=-YFiHW59ASs&ptk=StyleHaul&referrer=None&t=vjVQa1PpcFPiDK6v9s-rWrDn8gNv0QvpjyCIjiAgsm0=&asv=3&fmt=34&cpn=BOOMP-Bzbv1jikj9&el=detailpage&plid=AATTaqGSIR9CQ-MJ&begin=70000

  Its response is

  <?xml version="1.0" encoding="utf-8"?>

  And videoplayback only has range param, which indicate byte range where to pull. However, I couldn't figure out exact mechanism how new begin param works.

  http://r8---sn-p5q7yne6.c.youtube.com/videoplayback?algorithm=throttle-factor&burst=40&cp=U0hUTVNSVl9IT0NONF9LTFpGOlY5MU5RYVYtWHFw&cpn=BOOMP-Bzbv1jikj9&expire=1358378535&factor=1.25&fexp=919361%2C910207%2C916612%2C913112%2C912806%2C922403%2C922405%2C929901%2C913605%2C925710%2C929104%2C929110%2C908493%2C920201%2C913302%2C919009%2C911116%2C910221%2C901451&gcr=us&id=f981621d6e7d012b&ip=xxxx&ipbits=8&itag=34&keepalive=yes&key=yt1&ms=au&mt=1358354777&mv=m&newshard=yes&ratebypass=yes&signature=AA38C7074D8FA9DA44D01D9BB3675C78D05B9794.66D67C5AB111D8FB9EC3C8A141BBB11D9D70545D&source=youtube&sparams=algorithm%2Cburst%2Ccp%2Cfactor%2Cgcr%2Cid%2Cip%2Cipbits%2Citag%2Csource%2Cupn%2Cexpire&sver=3&upn=aLby9GtO0sU&range=3563520-5345279

  Can anyone explain how to pull a video starting from specific position(msec) in new API ?