Recherche avancée

Sur d’autres sites (3397)

• Fixing "RTP : dropping old packet received too late" in FFMPEG

  25 juin 2014, par user985030

  I have been using FFMPEG 0.6 for years with no problems and recently ported much of my code to 2.2 ; however, there is still a problem that I cannot resolve after fixing many of the deprecated functions. I am generating simulated video and then using RTSP to unicast this generated stream. The problem is that when I change the height and width of my video data, I basically recreate a new stream to send the subscribed client. The algorithm I used to do this in 0.6 worked like a charm, never had any problems. Now that I have upgraded, I get "RTP : dropping old packet received too late" as soon as I change my frame size. I think I have been dropping packets all along, but the new code is causing connection issues for me. The packets being dropped in the past were negligible and I really didn’t care if I missed them as long as the stream eventually corrected itself. Is there a flag that I can set to not drop these packets ? Or at least recover more quickly ? I believe that this has something to do with receiving packets out of order. There is a section of code that does a diff in FFMPEG in the rtpdec.c file in the function rtp_parts_one_packet. The only reference I found similar to my issue is here :

  http://en.it-usenet.org/thread/16949/6708/#post6707. Any tips would be greatly appreciated. In the meantime, I am just going to patch the FFMPEG code to not do the following check :

  if (diff < 0) {
  
  
  
  /* Packet older than the previously emitted one, drop */
  
  
  
  av_log(s->st ? s->st->codec : NULL,        AV_LOG_WARNING,
  
  
  
  "RTP: dropping old packet received too late\n");
  
  
  
  return -1;
  
  
  
  }

  By commenting out the above code, I am able to run my streaming application like I used to, but I have a feeling that I am not doing something correctly but I am not sure what it is. Thanks for any advice !

• FFmpeg error with ffmpeg.FS("readfile", "output.mp4"). trying to get ffmpeg to work in the react app

  21 juin 2024, par Paul Tham

   const stackVideos = useCallback(
    async (video1) => {
      try {
        console.log("Fetching video2 from storage...");
        const video2Ref = ref(storage, "video2.mp4");
        const video2Url = await getDownloadURL(video2Ref);
        const video2Blob = await (await fetch(video2Url)).blob();

        console.log("Writing video1 to FFmpeg FS...");
        await ffmpeg.FS("writeFile", "video1.mp4", await fetchFile(video1));

        console.log("Writing video2 to FFmpeg FS...");
        await ffmpeg.FS("writeFile", "video2.mp4", await fetchFile(video2Blob));

        console.log("Files in FFmpeg FS after write:");
        const files = await ffmpeg.FS("readdir", "/");
        console.log(files);

        const { start, end } = inputs[0];
        const startSeconds = new Date(`1970-01-01T${start}Z`).getTime() / 1000;
        const endSeconds = new Date(`1970-01-01T${end}Z`).getTime() / 1000;
        const duration = endSeconds - startSeconds;

        console.log("Running FFmpeg command...");
        await ffmpeg.run(
          "-i",
          "video1.mp4",
          "-ss",
          startSeconds.toString(),
          "-t",
          duration.toString(),
          "-i",
          "video2.mp4",
          "-filter_complex",
          "[0:v]scale=1080:-1[v1];[1:v]scale=-1:1920/2[v2scaled];[v2scaled]crop=1080:1920/2[v2cropped];[v1][v2cropped]vstack=inputs=2,scale=1080:1920[vid]",
          "-map",
          "[vid]",
          "-map",
          "0:a",
          "-c:v",
          "libx264",
          "-crf",
          "23",
          "-preset",
          "veryfast",
          "-shortest",
          "output1.mp4"
        );

        console.log("Files in FFmpeg FS after run:");
        const filesAfterRun = await ffmpeg.FS("readdir", "/");
        console.log(filesAfterRun);

        console.log("Reading output1.mp4 from FFmpeg FS...");
        const data = await ffmpeg.FS("readfile", "output1.mp4");
        console.log("after the FS readfile");
        const url = URL.createObjectURL(
          new Blob([data.buffer], { type: "video/mp4" })
        );
        setStackedVideo(url);
        setOutputFileReady(true); // Mark output file as ready
      } catch (err) {
        console.error("FFmpeg error output:", err);
        setError(`FFmpeg run error: ${err.message}`);
        setIsProcessing(false);
      }
    },
    [inputs]
  );


  


  My error seems to be stemming from this line :

  


   const data = await ffmpeg.FS("readfile", "output1.mp4");


  


  Seeing the ffmpeg.wasm documentation i thought the functions for some of the functions had changed, but when I changed it, it seemed like they did not recognise the new functions. Sometimes this will also give me some other errors like worker.js which I dont understand enough to debug this myself.

  


  words word words words words words word words words wordswords word words words wordswords word words words wordswords word words words wordswords word words words wordswords word words words words

  


• .NET Wrapper ffmpeg convert to mp4 set size to 1920 x 1080

  1er août 2020, par Robert

  I in my application written in .NET Core I use ffmpeg to convert movie from 3gp to mp4.

  


  var conversionOptions = new ConversionOptions
{
   MaxVideoDuration = TimeSpan.FromSeconds(60),
   VideoAspectRatio = VideoAspectRatio.R16_9,
   VideoSize = VideoSize.Hd1080,
   AudioSampleRate = AudioSampleRate.Hz44100,
   //  CustomWidth = 200
};
                    
await ffmpeg.ConvertAsync(inputFile, outputFileMp4, conversionOptions);


  


  Convertion works fine, but my source movie is from mobile phone. Its frame size is 1920 x 1080 but the movie is higher than wider.
After conversion with above code the frame is the same but the movie is cuted and it is wider than taller.
I wanted to have original size