Recherche avancée

Sur d’autres sites (5412)

• I can't use immediately converted video with FFmpeg (Android)

  26 juin 2019, par Jose Q

  I’m using this lib to turn a video with a watermark into a corner : https://github.com/WritingMinds/ffmpeg-android-java

  To detect when the video conversion is ready I’m using this :

  try {
  
          ffmpeg.execute(command, new ExecuteBinaryResponseHandler() {
  
              @Override
  
              public void onFailure(String s) {
  
              }
  
  
  
              @Override
  
              public void onSuccess(String s) {
  
              }
  
  
  
              @Override
  
              public void onProgress(String s) {
  
              }
  
  
  
              @Override
  
              public void onStart() {
  
              }
  
  
  
              @Override
  
              public void onFinish() {
  
  
  
                  //outpath is: /storage/emulated/0/drawable/share1561561063811.mp4
  
                  Uri u = Uri.parse(outpath);
  
  
  
              }
  
          });
  
      } catch (FFmpegCommandAlreadyRunningException e) {
  
          // do nothing for now
  
      }

  Well, everything goes perfect so far, I can find the video through the file manager, but what I can’t do is use it immediately after onFinish() in my app.

  I can’t play the video or upload it. I’ve tried using outpath directly and also tried this method that works for other videos and I get null. :

  private String getRealPathFromURI(Uri contentUri) {
  
      String[] proj = { MediaStore.Images.Media.DATA };
  
      CursorLoader loader = new CursorLoader(this, contentUri, proj, null, null, null);
  
      Cursor cursor = loader.loadInBackground();
  
      int column_index = cursor.getColumnIndexOrThrow(MediaStore.Video.Media.DATA);
  
      cursor.moveToFirst();
  
      String result = cursor.getString(column_index);
  
      cursor.close();
  
      return result;
  
  }

• Video Processing in background using ffmpeg

  20 juin 2019, par Mehran

  The problem comes when during the video processing user closes the application himself from the task manager then its processing stops.

  I am working on video file processing in android using FFMpeg, which is working perfectly but when I do close the application during processing from task manager then video processing has stopped working even I added all the work in work manager.

  @Override
  
  public Result doWork() {
  
      shellCommand = new ShellCommand();
  
      ffmpegBinary = new String[] {
  
          FileUtils.getFFmpeg(context).getAbsolutePath()
  
      };
  
      command = concatenate(ffmpegBinary, command);
  
      CommandResult commandResult = getCommandResult(command);
  
      if (command`enter code here`Result.success) {
  
          onSuccess(videoPath);
  
      } else {
  
          onFailure(videoPath);
  
      }
  
  }
  
  //getCommandResult
  
  private CommandResult getCommandResult(String[] command) {
  
      try {
  
          process = shellCommand.run(command, null);
  
  
  
          if (process == null) {
  
              return CommandResult.getDummyFailureResponse();
  
          }
  
          checkAndUpdateProcess();
  
          return CommandResult.getOutputFromProcess(process);
  
      } catch(Exception e) {} finally {
  
          Util.destroyProcess(process);
  
      }`enter code here`
  
      return CommandResult.getDummyFailureResponse();
  
  }

  As far as I can tell, when the application closes from the background then the parent process destroys it and is destroying all of its sub-process too, FFMpeg is using the android process to execute the command and check the video file status during video processing.

• Gracefully closing FFMPEG child processes from node

  10 juin 2019, par Gordon

  I am trying to record numerous audio feeds using ffmpeg. Node downloads a config file with the stream URLS (HLS M3U8 playlists), parses it and starts the appropriate number of ffmpeg instances. When I go to shut them down, nothing happens and I have to kill them with task manager, resulting in corrupt files. When I am debugging and hit control-c within a minute or two of starting the program, it works without issue. When I need to record more than 5-10 minutes that I have problems.

  I found this related question from 2013, and adapted it to fit my multiple stream situation.

  The recorder processes are started with the following code (inside the http request callback) :

  config.audio_config.forEach((channel,i)=>{
  
  self.liveChannels++;
  
  
  
  console.log(`   ${channel.number}`);
  
  self.Channels[i] = spawn('ffmpeg', ['-i', `${channel.base_url + channel.stream_ios}`,  '-c:v', 'none', '-c:a', 'copy', `Output\\${config.folder}\\${channel.number}.m4a`]);
  
  self.Channels[i].stdin.setEncoding('utf8');
  
  self.Channels[i].chNum = channel.number;
  
  
  
  self.Channels[i].on('exit',(code,sig)=>{
  
  console.log(`   Channel ${channel.number} recorder closed.`);
  
  self.liveChannels--;
  
  if(self.liveChannels === 0){
  
      process.exit();
  
  }
  
  });
  
  });
  
  console.log('Press Ctl-C to start Shutdown');

  My shutdown function (triggered by SIGINT to main process) is :

  function shutdown() {
  
      self.Channels.forEach((chan)=>{
  
          chan.stdin.write('q');
  
          chan.stdin.end(); //I have tried both with and without this line and chan.stdin.end('q')
  
      });
  
  
  
  }

  UPDATE :
  Switching to an AAC container file (simply changed the extension on the output) removed the need for a graceful FFMPEG exit. I still would like to know why sending ’q’ to stdin only kills the FFMPEG process for the first 10 minutes.