Recherche avancée

Sur d’autres sites (9071)

• avio : Copy URLContext generic options into child URLContexts

  28 février 2015, par Martin Storsjö

  avio : Copy URLContext generic options into child URLContexts
  Since all URLContexts have the same AVOptions, such AVOptions
  
  will be applied on the outermost context only and removed from the
  
  dict, while they probably make sense on all contexts.
  This makes sure that rw_timeout gets propagated to the innermost
  
  URLContext (to make sure it gets passed to the tcp protocol, when
  
  opening a http connection for instance).
  Alternatively, such matching options would be kept in the dict
  
  and only removed after the ffurl_connect call.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/avio.c
  • [DBH] libavformat/aviobuf.c
  • [DBH] libavformat/concat.c
  • [DBH] libavformat/crypto.c
  • [DBH] libavformat/gopher.c
  • [DBH] libavformat/hlsproto.c
  • [DBH] libavformat/http.c
  • [DBH] libavformat/icecast.c
  • [DBH] libavformat/md5proto.c
  • [DBH] libavformat/mmst.c
  • [DBH] libavformat/rtmpcrypt.c
  • [DBH] libavformat/rtmpproto.c
  • [DBH] libavformat/rtpproto.c
  • [DBH] libavformat/rtsp.c
  • [DBH] libavformat/rtspdec.c
  • [DBH] libavformat/sapdec.c
  • [DBH] libavformat/sapenc.c
  • [DBH] libavformat/smoothstreamingenc.c
  • [DBH] libavformat/srtpproto.c
  • [DBH] libavformat/tls.c
  • [DBH] libavformat/url.h

• Node.js Child Process Issue with Args - Quotes Issue ?, FFMPEG issue ?

  7 septembre 2012, par Brad

  I need to be able to execute FFMPEG from my Node.js application. I believe this problem likely has to do with properly specifying command line arguments, and not specific to FFMPEG, but as I have been unable to narrow down the issue, I present my entire problem.

  I can execute the following command from the command prompt successfully :

  C:\Brad\ffmpeg.exe -f dshow -i audio="Microphone (SoundMAX Integrated" testaaa.mp3

  FFMPEG starts as expected, records audio from my audio device, and writes an MP3 file. Now, I try to do the same thing within my Node.js application :

  childProcess = child_process.spawn('C:\\Brad\\ffmpeg.exe', ['-f', 'dshow', '-i', 'audio="Microphone (SoundMAX Integrated"', 'testaaa.mp3']);
  
  childProcess.stderr.on('data', function (data) {
  
      console.log('StdioSource received data from STDERR: ' + data);
  
  });

  From within Node.js, FFMPEG fails ! The error is simply :

  [dshow @ 0000000001eded80] Could not find audio device.
  
  audio="Microphone (SoundMAX Integrated": Input/output error

  Thinking that maybe for some reason this was a weird permissions error, I decided to run FFMPEG with -list_devices true from within my Node application, and sure enough, the device in question is listed :

  [dshow @ 000000000228ecc0] DirectShow video devices
  
  [dshow @ 000000000228ecc0] Could not enumerate video devices.
  
  [dshow @ 000000000228ecc0] DirectShow audio devices
  
  [dshow @ 000000000228ecc0]  "Microphone (SoundMAX Integrated"

  Any thoughts as to why I cannot properly specify the audio input device in the arguments for FFMPEG, or why FFMPEG does not recognize my audio input device when running as a child process to Node.js ?

  Any hints would be most appreciated.

• hls : disallow opening nested files in child demuxers

  15 février 2016, par Anton Khirnov

  hls : disallow opening nested files in child demuxers
  

  • [DBH] libavformat/hls.c