Recherche avancée

Sur d’autres sites (5510)

• Capturing stream that has multiple frames

  28 mai 2021, par cheese5505

  I'm trying to capture a stream that has multiple "frames" (not sure that's what you would call it but it has multiple 5 second streams inside of it) with FFmpeg and saving to file. When I put it into Quicktime player and play it works fine, however when I put it into FFmpeg and review the final file it seems that the audio and video are out of sync and the video frequently stops. I think this may be because it is stopping to switch to the new 5 second video but i'm not sure. This is the command I am using :

  



  ffmpeg \
    -v 9 \
    -loglevel 99 \
    -y \
    -re \
    -hwaccel auto \
    -threads 4 \
    -user-agent "Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16" \
    -i "url here" \
    -ac 2 \
    -strict -2 \
    -c:a aac \
    test.mov


  



  In the FFmpeg log this frequently happens :

  



  frame=  242 fps=102 q=29.0 size=     252kB time=00:00:06.33 bitrate= 325.9kbits/
frame=  279 fps= 96 q=29.0 size=     252kB time=00:00:07.57 bitrate= 272.8kbits/
frame=  301 fps= 87 q=29.0 size=     252kB time=00:00:08.30 bitrate= 248.7kbits/
frame=  319 fps= 79 q=29.0 size=     252kB time=00:00:08.90 bitrate= 231.9kbits/
frame=  338 fps= 74 q=29.0 size=     252kB time=00:00:09.54 bitrate= 216.5kbits/
frame=  354 fps= 70 q=29.0 size=     252kB time=00:00:10.07 bitrate= 205.0kbits/
skipping 5 segments ahead, expired from playlists
[https @ 0x7f9d81e10380] No trailing CRLF found in HTTP header.
frame=  355 fps= 51 q=29.0 size=     252kB time=00:00:10.11 bitrate= 204.3kbits/
[hls,applehttp @ 0x7f9d83001000] No longer receiving playlist 6
[hls,applehttp @ 0x7f9d83001000] No longer receiving playlist 7
[hls,applehttp @ 0x7f9d83001000] No longer receiving playlist 8
skipping 3 segments ahead, expired from playlists
[https @ 0x7f9d81f006a0] No trailing CRLF found in HTTP header.


  



  Any ideas how I could smooth out the final file would be greatly appreciated.

  


• How to reduce the app size after use of FFMPEG in flutter ?

  10 octobre 2022, par Sugan Pandurengan

  I'm current using ffmpeg_kit_flutter 4.5.1-LTS after that my app bundle size increase by 150mb and final bundle size is 250 mb.

  


  Is there any way to reduce the app bundle size with FFMPEG.

  


• Stop JavaVC playback warning

  5 novembre 2017, par Chaoslab

  Receiving a stream of command line warnings as video plays - deprecated pixel format used, make sure you did set range correctly

  Question :
  How can I stop the warnings from happening or being displayed ?

  Example code below (just frame grabbing, not timed playback).

  import java.io.File;
  
  
  
  import org.bytedeco.javacv.CanvasFrame;
  
  import org.bytedeco.javacv.FFmpegFrameGrabber;
  
  import org.bytedeco.javacv.Frame;
  
  
  
  public class TestPlay implements Runnable {
  
   private static String      video_loc = null;
  
   private static CanvasFrame canvas    = new CanvasFrame("Test JavaCV player");
  
  
  
   public static void main(String[] args) { new Thread(new TestPlay(args[0])).start(); }
  
  
  
   public void run() { play_video(video_loc); }
  
  
  
   public TestPlay(String loc) { video_loc = loc; }
  
  
  
   public static final void play_video(String vid_loc) {
  
    try {
  
     File               file      = new File(vid_loc);
  
     FFmpegFrameGrabber ffmpeg_fg = new FFmpegFrameGrabber(file.getAbsolutePath());
  
     Frame              frm;
  
     ffmpeg_fg.setAudioChannels(0);
  
     ffmpeg_fg.start();
  
     for(;;)
  
      if((frm = ffmpeg_fg.grab()) != null) canvas.showImage(frm);
  
      else {
  
       ffmpeg_fg.setTimestamp(0);
  
       break;
  
      }
  
     ffmpeg_fg.stop();
  
    } catch(Exception ex) { ex("play_video vid_loc:" + vid_loc, ex); }
  
   }
  
  
  
   public static final void ex(String txt, Exception ex)   {
  
    System.out.println("EXCEPTION: " + txt + " stack..."); ex.printStackTrace(System.out); }
  
  }

  Looking into these possible solutions...

  • Set the correct pixel format before decoding.
  • Turning off FFMpeg warning logging.

  Will update with a fix when found.