Recherche avancée

Sur d’autres sites (9253)

• ffmepg why error :Failed to write core dump

  9 juillet 2021, par dmouse

  I wang to implement a feature that allows me to save RTSP stram as a file,
use javacv implement a demo,but there's an error.
i debug the demo , execute 'recorder.record(frame) ;' error, "ulimit -c unlimited" is useless,the program still reports an error.
review of the source code did note find the problem principle.pleace give me a hand.

  


  import org.bytedeco.javacpp.avcodec;
import org.bytedeco.javacv.FFmpegFrameGrabber;
import org.bytedeco.javacv.FFmpegFrameRecorder;
import org.bytedeco.javacv.Frame;

import java.io.File;
import java.io.IOException;

/**
 * @ClassName video
 * @Description TODO
 * @Author mouse
 * @Date 2021/7/9 11:13
 * @Version 1.0
 **/
public class Video {
    public static void main(String[] args) {
        String streamUrl = "rtsp://admin:12345678.@192.168.20.180:554/h265/ch1/main/av_stream";
        String filePath = "./video/hello.mp3";
        File outFile = new File(filePath);
        FFmpegFrameGrabber grabber = new FFmpegFrameGrabber(streamUrl);
        if (!outFile.getParentFile().exists()) {
            outFile.getParentFile().mkdirs();
        }
        FFmpegFrameRecorder recorder = new FFmpegFrameRecorder(filePath,1080,1440, 1);
        recorder.setVideoCodec(avcodec.AV_CODEC_ID_H265);
        recorder.setFormat("flv");
        recorder.setVideoBitrate(4000);
        try {
            grabber.start();
            recorder.start();
            Frame frame = grabber.grabFrame();
            while (frame!=null){
                recorder.record(frame);
                frame = grabber.grabFrame();
            }
            recorder.record(frame);
            recorder.stop();
            grabber.stop();

        } catch (FFmpegFrameGrabber.Exception e) {
            e.printStackTrace();
        } catch (IOException e) {
            e.printStackTrace();
        } finally {
            try {
                if (recorder != null) {
                    recorder.stop();
                }
                if (grabber != null) {
                    grabber.stop();
                }
            } catch (FFmpegFrameRecorder.Exception | FFmpegFrameGrabber.Exception e) {
                e.printStackTrace();
            }
        }
    }
}



  


  log error

  


  #
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000131fef233, pid=50498, tid=0x0000000000001003
#
# JRE version: Java(TM) SE Runtime Environment (8.0_281-b09) (build 1.8.0_281-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.281-b09 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  [libavformat.57.dylib+0xbf233]  av_write_frame+0x993
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


  


  pom :

  


          <dependency>&#xA;            <groupid>org.bytedeco</groupid>&#xA;            <artifactid>javacv</artifactid>&#xA;            <version>1.4.3</version>&#xA;        </dependency>&#xA;        <dependency>&#xA;            <groupid>org.bytedeco.javacpp-presets</groupid>&#xA;            <artifactid>ffmpeg-platform</artifactid>&#xA;            <version>4.0.2-1.4.3</version>&#xA;        </dependency>&#xA;

  


  My os : macOS Bgi Sur 11.4 ;
  
JDK : 1.8.0_281
  
execute 'recorder.record(frame) ;' error,
"ulimit -c unlimited" is useless,the program still reports an error .

  


• Can't get FFMPEG buildpack working in Heroku Node.js server (using Fluent-FFMPEG)

  30 juillet 2021, par Rayhan Memon

  I'm using a library called 'fluent-ffmpeg' on my Nodejs server that makes it easier to use an audio/video editing tool called FFmpeg, which is downloaded locally on my computer.

  


  When running on my computer, I point fluent-ffmpeg to the local executable files of FFmpeg and FFprobe on my computer, like so :

  


  import ffmpeg from "fluent-ffmpeg";

// When running locally, set FFmpeg and FFprobe path to the local executable files
ffmpeg.setFfmpegPath("C:/Program Files/FFMPEG/ffmpeg.exe");
ffmpeg.setFfprobePath("C:/Program Files/FFMPEG/ffprobe.exe");


  


  When deploying to Heroku, I must use an FFmpeg 'buildpack'.

  


  I've tried two :

  


  

  1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest

  


  2. https://github.com/HasibulKabir/heroku-buildpack-ffmpeg-ffprobe

  


  


  Neither have worked for me. Whenever I use an FFmpeg command, I get the following error in my heroku logs :

  


  2021-07-24T15:22:52.970990+00:00 app[web.1]:   code: 'ENOENT',
2021-07-24T15:22:52.970990+00:00 app[web.1]:   syscall: 'spawn C:/Program Files/FFMPEG/',
2021-07-24T15:22:52.970990+00:00 app[web.1]:   path: 'C:/Program Files/FFMPEG/',
2021-07-24T15:22:52.970991+00:00 app[web.1]:   spawnargs: [
2021-07-24T15:22:52.970991+00:00 app[web.1]:     '-show_streams',
2021-07-24T15:22:52.970991+00:00 app[web.1]:     '-show_format',
2021-07-24T15:22:52.970992+00:00 app[web.1]:     'temp/cf3b5f1ae270df824921364573a4366b'
2021-07-24T15:22:52.970992+00:00 app[web.1]:   ]
2021-07-24T15:22:52.970992+00:00 app[web.1]: }


  


  How can I go about using fluent-ffmpeg in my Nodejs server when deploying to Heroku ?

  


  Thank you for the help in advance !

  


• RNFFMpeg.executeAsync : Unable to create gif of a video with space(s) in it's source path

  7 juillet 2021, par STBox

  Unable to make gif of a video which has space(s) in it's source directory. All the other video which don't have space(s), their gif is making fine. I had a video whose folder name had space and it was not making gif for it. I copied the same video to a folder without space in it's name, and it made gif for it successfully. Even if I replace the the space with source path with anything like %20 etc, then it says

  


  


  No such file or directory

  


  


  Code snippet

  


  


  


  RNFFmpeg.executeAsync(
          `-i ${source} -ss ${start} -t ${gifDuration}  -vf "fps=5,scale=160:-1:flags=lanczos,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" -loop 0 ${destination}`, (completedExecution) => {
            if (completedExecution.returnCode === 0) {
              resolve({ path: destination });
            } else {
              resolve({ error: "invalid Gif" });  // always this part executes for videos with space in their source path
            }
          }
        );

  


  


  



  Expected behavior

  


  Regardless a video has or has not a space in it's path, it should make gif correctly and

  


  


  completedExecution.returnCode

  


  


  should be 0

  


  Current behavior
Currently, for all the videos having space in their source path, completedExecution.returnCode is always 1

  


  Logs of the same video without space in folder name

  


  


  [Wed Jul 07 2021 12:23:56.377] LOG file :///storage/emulated/0/AirDroid/VID-20210620-WA0024.mp4 [Wed Jul

  


  


  


  07 2021 12:23:56.511] LOG [Parsed_palettegen_3 @ 0x7d62eb5ec0] 255(+1) colors generated out of 249823 colors ; ratio=0.001021 [Wed Jul 07 2021 12:23:56.672] LOG video:48kB audio:0kB subtitle:0kB other streams:0kB

  


  


  


  global headers:0kB muxing overhead : [Wed Jul 07 2021 12:23:56.673] LOG

  


  


  


  0.041083% [Wed Jul 07 2021 12:23:56.722] LOG "path" : "/data/user/0/com.tbox.pantry/cache/1625642625930.gif"

  


  


  Logs of the same video with space in folder name

  


  


  [Wed Jul 07 2021 12:20:45.577] LOG

  


  


  


  file :///storage/emulated/0/FMWhatsApp/Media/FMWhatsApp

  


  


  


  Video/VID-20210620-WA0024.mp4 [Wed Jul 07 2021 12:20:45.998] LOG

  


  


  


  file :///storage/emulated/0/FMWhatsApp/Media/FMWhatsApp : No such file

  


  


  


  or directory [Wed Jul 07 2021 12:20:45.998] LOG Conversion failed !

  


  


  


  [Wed Jul 07 2021 12:20:45.999] LOG "error" : "invalid Gif"

  


  


  Environment

  


  "react" : "16.13.1",
"react-native" : "^0.63.3",
"react-native-ffmpeg" : "0.5.1",
Android 11