Recherche avancée

Sur d’autres sites (11336)

• Unable to find a suitable output format for 'pipe :' - pipe: : Invalid argument

  14 août 2017, par Adam Gerard

  I’m working on a project to potentially simplify some of the process to send video to something like Facebook Live.

  Right now I’m using this example with a FB Live API RTMP endpoint (neither of these are production or real development commands - by using this example I think I can figure out the limitations of what I’m doing in others) :

  -i - -map 0 -c:v libx264 -c:a aac -muxrate 1000k -bufsize 2000k -g 50 -f tee "rtmp://rtmp-api.facebook.com:80/rtmp/10104590177564330?ds=1&s_e=4&s_l=1&a=ATgko8JiGpXC0WGf"

  Here’s the original example :

  $ ffmpeg -i input -map 0 -c:v libx264 -c:a aac -bufsize 2000k -g 50 -f tee \ "[f=flv:onfail=ignore]rtmp://facebook|[f=flv:onfail=ignore]r‌​tmp://youtube|local_‌​file.mkv"

  However, despite using that example I’m getting :

  [NULL @ 0xffd840] Unable to find a suitable output format for 'pipe:'<br />
pipe:: Invalid argument

  I understand that sometimes this error arises due to spacing issues or incorrect syntax. I’ve looked around to try to resolve this problem and using many combinations does not change the result.

  Thanks !

  Edit - Log added :

   configuration: --cc=emcc --prefix=/Users/bgrinstead/Sites/videoconverter.js/build/ffmpeg/../dist --extra-cflags='-I/Users/bgrinstead/Sites/videoconverter.js/build/ffmpeg/../dist/include -v' --enable-cross-compile --target-os=none --arch=x86_32 --cpu=generic --disable-ffplay --disable-ffprobe --disable-ffserver --disable-asm --disable-doc --disable-devices --disable-pthreads --disable-w32threads --disable-network --disable-hwaccels --disable-parsers --disable-bsfs --disable-debug --disable-protocols --disable-indevs --disable-outdevs --enable-protocol=file --enable-libvpx --enable-gpl --extra-libs='/Users/bgrinstead/Sites/videoconverter.js/build/ffmpeg/../dist/lib/libx264.a /Users/bgrinstead/Sites/videoconverter.js/build/ffmpeg/../dist/lib/libvpx.a'

  It specifically fails here :

  .../
  
  libavutil      52. 66.100 / 52. 66.100

• Video conversion with ffmpeg to target Android and iOS mobile devices

  17 novembre 2017, par Lee Brindley

  I’m building a react native app for both Android and IOS, the back-end API is written with NodeJS.

  Users may upload video from their phones, once uploaded the user and their friends will be able to view the video - so the videos need to be stored in a format which is playable on both Android & IOS.

  My question relates to the conversion of video, uploaded by the user. I developed a similar app a couple of years ago ; I used the repo node-fluent-ffmpeg which provides a nice API to interact with FFmpeg.

  In the previous project (which was a web app), I converted the uploaded videos into two files, one .mp4 and one .webm - if a user uploaded an mp4, then I would skip the mp4 step, likewise if they uploaded a .webm.

  This was kind of slow. Now I’ve come across the same requirement years later, after some research I think I was wrong to convert the videos to the last project.

  I’ve read that I can simply use FFmpeg to change the container format of the videos, which is a much faster process than converting them from scratch.

  The video conversion code I used last time went something along the lines of :

  var convertVideo = function (source, format, output, success, failure, progress) {
  
  
  
      var converter = ffmpeg(source);
  
  
  
      var audioCodec = "libvorbis";
  
  
  
      if (format.indexOf("mp4") != -1) {
  
          audioCodec = "aac";
  
      }
  
  
  
      converter.format(format)
  
          .withVideoBitrate(1024)
  
          .withAudioCodec(audioCodec)
  
          .on('end', success)
  
          .on('progress', progress)
  
          .on('error', failure);
  
  
  
      converter.save(output);
  
  };

  Usage :

  Convert to mp4 :

  convertVideo("PATH_TO_VIDEO", "mp4", "foo.mp4", () => {console.log("success");});

  Convert to webm :

  convertVideo("PATH_TO_VIDEO", "webm", "foo.webm", () => {console.log("success");});

  Can anyone point out a code smell here regarding the performance of this operation ? Is this code doing a lot more than it should achieve cross-platform compatibility between IOS and Android ?

  Might be worth mentioning that support for older OS versions is not such a big deal in this project.

• FFmpeg ogg - Invalid data found when processing input

  28 juillet 2017, par Earinor

  I am trying to change the framerate of a Video of mine. Below there is the example Input and the Output. I Built ffmpeg myself and I’m pretty sure I miss the right decoder/demuxer but I have no Idea what I need. I thought —enable-libtheora would be enough to enable, muxers, demuxers, encoder and decoder, but apperently there is somehting missing. Does anybody have an idea about this ?

  I have inserted path-to-ffmpeg to make this shorter, the Path itself is okay, so no worries about that.

     *path-to-ffmpeg*\ffmpeg>ffmpeg -i Video.ogg -filter "minterpolate='fps=60'" out.ogg
  
  ffmpeg version 3.3.git Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 6.3.0 (x86_64-posix-seh-rev2, Built by MinGW-W64 project)
  
    configuration: --disable-encoders --disable-decoder=hevc --disable-decoder=raw
  
  video --disable-decoder=ac3 --disable-decoder=flac --disable-decoder=ffwavesynth
  
   --disable-decoder=libcelt --disable-decoder=libgsm --disable-decoder=libilbc --
  
  disable-decoder=libopus --disable-decoder=dvbsub --disable-decoder=dvdsub --disa
  
  ble-hwaccels --disable-parsers --disable-bsfs --disable-protocols --disable-inde
  
  vs --disable-outdevs --disable-devices --disable-filters --disable-muxers --disa
  
  ble-demuxers --enable-muxer=ogg --enable-zlib --enable-libtheora --enable-libvor
  
  bis --enable-shared --enable-encoder=libtheora --enable-encoder=libvorbis --enab
  
  le-demuxer=image2 --enable-filter=framerate --enable-protocol=file --enable-filt
  
  er=minterpolate --enable-filter=scale
  
    libavutil      55. 61.100 / 55. 61.100
  
    libavcodec     57. 93.100 / 57. 93.100
  
    libavformat    57. 72.101 / 57. 72.101
  
    libavdevice    57.  7.100 / 57.  7.100
  
    libavfilter     6. 85.100 /  6. 85.100
  
    libswscale      4.  7.101 /  4.  7.101
  
    libswresample   2.  8.100 /  2.  8.100
  
  Video.ogg: Invalid data found when processing input