Recherche avancée

Sur d’autres sites (7277)

• FFmpeg settings to convert MTS into MPG for YouTube

  17 juin 2013, par JJD

  I would like to discuss the optimal parameters for FFmpeg to convert an MTS video file with the following profile for the upload onto YouTube. YouTube published their suggested resolutions and bitrates settings.

  // Input video profile
  
  Stream #0:0[0x1011]: Video: h264 (High) (HDMV / 0x564D4448), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc
  
  Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, s16, 256 kb/s

  Since YouTube has length restrictions to the videos I also want to cut the original file into pieces.

  Here is my current configuration to convert a video. I am running Ubuntu 10.10. with FFmpeg version git-2011-12-31-81980bf.

  ffmpeg -ss 00:15:00 -i input.mts -t 00:30:00 -vcodec libx264 -deinterlace -s hd720 -ab 128k -threads 0 output.mp4

  I also want to reencode the video since I do not want to upload the large files of the original recording.

• FFmpeg settings to convert MTS into MPG for YouTube

  17 juin 2013, par JJD

  I would like to discuss the optimal parameters for FFmpeg to convert an MTS video file with the following profile for the upload onto YouTube. YouTube published their suggested resolutions and bitrates settings.

  // Input video profile
  
  Stream #0:0[0x1011]: Video: h264 (High) (HDMV / 0x564D4448), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc
  
  Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, s16, 256 kb/s

  Since YouTube has length restrictions to the videos I also want to cut the original file into pieces.

  Here is my current configuration to convert a video. I am running Ubuntu 10.10. with FFmpeg version git-2011-12-31-81980bf.

  ffmpeg -ss 00:15:00 -i input.mts -t 00:30:00 -vcodec libx264 -deinterlace -s hd720 -ab 128k -threads 0 output.mp4

  I also want to reencode the video since I do not want to upload the large files of the original recording.

• YouTube's HD Video Streaming Server Technology ?

  30 septembre 2013, par bgentry

  Lately I've been researching different methods for streaming MP4s to the browser. Flash Media Server is an obvious choice here (using Cloudfront), and most solutions I've seen use the RTMP protocol.

  However, I spent some time on YouTube with Firebug and Chrome debugger figuring out how their streaming worked and I discovered some interesting differences between some of their videos and quality rates.

  My two sample videos are A and B. A is available up to 480p and B is available up to 1080p. For both videos, all rates up to 480p are served in an FLV container with H.264 video and AAC audio, over HTTP. What's interesting here is that if you have not yet downloaded (cached) the entire video, and you try to skip forward to an uncached part of the video, a new request will be made with a 'begin' parameter equal to the target offset in milliseconds. Example from Video A at 480p :

  http://v11.lscache8.c.youtube.com/videoplayback?ip=0.0.0.0&sparams=id%2Cexpire%2Cip%2Cipbits%2Citag%2Calgorithm%2Cburst%2Cfactor%2Coc%3AU0dWTldQVF9FSkNNNl9PSlhJ&fexp=904806%2C902906%2C903711&algorithm=throttle-factor&itag=35&ipbits=0&burst=40&sver=3&expire=1279756800&key=yt1&signature=D2D704D63C242CF187CAA5B5D5BAFB8DFACAC5FF.39180C01559C976717B651A7EB1D0C6249231EB7&factor=1.25&id=8568eb3135971f6f&begin=111863
  
  
  
  Response Headers:
  
  Cache-Control:public,max-age=23472
  
  Connection:close
  
  Content-Length:14320637
  
  Content-Type:video/x-flv
  
  Date:Wed, 21 Jul 2010 17:23:48 GMT
  
  Expires:Wed, 21 Jul 2010 23:55:00 GMT
  
  Last-Modified:Wed, 19 May 2010 12:31:41 GMT
  
  Server:gvs 1.0
  
  X-Content-Type-Options:nosniff

  The file returned by this URL is a fully valid FLV containing only the portion of the video after the requested offset.

  I did the same kind of test on the higher resolution versions of Video B. At 720p and 1080p, YouTube will return a video in an MP4 container, also with H.264 video and AAC audio. What's impressive to me is that their server takes the same type of offset for an MP4 video (via the 'begin' parameter) and returns a valid, streamable MP4 (moov atom at the front of the file with correct offsets) that also only includes the requested portion of the video.

  So, how does YouTube do this ? How do they generate the FLV or MP4 container on the fly with the correct headers and only the desired segment of the requested video ? I know this can be accomplished using FFMPEG to seek to the desired start point and the qt-faststart script to reposition the moov atom to the front of the stream, but it seems like this would be too slow to handle on-demand for millions of YouTube viewers.

  Ideas ?

  Thanks in advance !

  Footnote : I am not allowed to include more than 1 link at this point, so here is Video A's URL : http:// www.youtube .com/watch ?v=hWjrMTWXH28 "Video available up to 480p"