Recherche avancée

Sur d’autres sites (9830)

• avformat/mpegts : skip non-PMT tids earlier

  9 mai 2018, par Aman Gupta

  avformat/mpegts : skip non-PMT tids earlier
  This mimics the logic flow in all the other callbacks
  
  (pat_cb, sdt_cb, m4sl_cb), and avoids calling skip_identical()
  
  for non PMT_TID packets.
  Since skip_identical modifies internal state like
  
  MpegTSSectionFilter.last_ver, this change prevents unnecessary
  
  reprocessing on some streams which contain multiple tables in
  
  the PMT pid. This can be observed with streams from certain US
  
  cable providers, which include both tid=0x2 and another unspecified
  
  tid=0xc0.
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  

  • [DH] libavformat/mpegts.c

• Youtube-DL file download live progress

  7 février 2015, par roshkattu

  I am using the YoutubeDL library in a project. My environment is based on WINDOWS with XAMPP as the webserver boundle (apache,php,mysql,etc). I am using the youtube-dl.exe file to download the video and then use ffmpeg.exe to convert the video to an MP3 audio file.

  At the moment, I have an issue related to programming : I want to show live a progressbar while the video is downloaded with the youtube-dl.exe file. This exe creates a log file, that is updated while the video is downloaded. So my approach on this was to create a PHP file, that opens, parses the log file and get’s the progress percent, and sends it as a json encoded value to an AJAX function that is called every 100MS. Indeed, if the video is too large, there will be a very high ammount of data while polling the PHP file to get the progress state. And sometimes, the browser either crashes or freezes because of this ajax polling.

  My question is : is there any better approach to do this with PHP/AJAX ? Rathar than poll the file every 100MS, or 50MS ?

• android chromecast mp4 by ffmpeg - shorter files play, some longer ones buffer but dont play

  20 octobre 2014, par Robert Rowntree

  Using Android SDK for CC, CCL, and ’styled receiver’ CC app.

  Video Files created by a heroku/ffmpeg bin that will play on any other client i tried (VLC ubuntu... ) and that will even play in chrome on a tab that’s being cast to chromecast will NOT PLAY natively on chromecast apps. They will appear as normal load in the UI of the app. CCL logs will show them buffering OK , but they never enter a play state from the buffering state. Debugging the receiver shows nothing unusual ( network tab, or Console ). They just buffer and dont play.

  If a slightly shorter version of the same , 2 ffmpeg input files is prepared and hosted, it seems to play fine in shorter versions under about 14 seconds long but will not play if a 16 second version is created.

  I used a number of chromecast apps including Allcast to test this. always got same result.

  2 dropbox mp4 links created with the ffmpeg cli here are below. A 14 second version of the output mp4 file plays fine on several Chromecast/android apps and a 16 second version fails.

  file len 14s

  file len 16s Wont play in CC apps

  ffprobe output on the files at :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_14s.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.29.105
  
    Duration: 00:00:14.07, start: 0.046440, bitrate: 311 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 199 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
  
      Metadata:
  
        handler_name    : SoundHandler

  and the file 2 seconds longer that wont play

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_16s.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.29.105
  
    Duration: 00:00:16.06, start: 0.046440, bitrate: 286 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 174 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
  
      Metadata:
  
        handler_name    : SoundHandler

  Used ’qtfaststart’ and checked for MOOV ATOM issues and dont think that’s relevant.

  I think i can limit recordings in my app to 14 seconds and avoid problems that way, but I would like to understand what is up with the chromecast GETS on MP4’s generated by ffmpeg.