Recherche avancée

Sur d’autres sites (9768)

• Black overlay appears when merging a transparent video to another video

  13 juin 2012, par RakeshS

  This is what I have done so far :

  Command to create a transparent PNG image :

  convert -size 640x480 -background transparent -fill blue \
  
  -gravity South label:ROCK image1-0.png

  Command to create a transparent video :

  ffmpeg -loop 1 -f image2 -i image1-0.png -r 20 -vframes 100 \
  
  -vcodec png -pix_fmt bgra mov-1.mov

  (as per this post) - I expect this video to be a transparent video.

  Command to overlay a video with another :

  ffmpeg -i final-video.mov -sameq -ar 44100 \
  
  -vf "movie=mov-1.mov [logo];[in][logo] overlay=0:0 [out]" \
  
  -strict experimental final-video.mov

  Above commands works perfect and I have not faced any problem, but I don't get what I expect which is kinda watermarking effect, I want mov-1.mov to be transparent with final-video.mov.

  Questions :

  1. Is there any way to verify if the generated video is transparent ? other than merging ?
  2. Not sure why the above mov-1.mov is not transparent when it is merged with final-video.mov, any info to solve this problem would be great.

  Please help.

• Put vast or vpaid overlay on live stream rtmp url output

  8 février 2020, par yolov3

  how to merge vast/vpaid overlay on live stream rtmp url output using ffmpeg ?
  it means get rtmp or m3u8 output stream link with merged vast/paid generated on stream time & can’t be change it.

• Node.js Live Streaming : Avoid buffering

  27 octobre 2012, par Shirish Kamath

  I've written a small nodeJS server that outputs system audio captured by ffmpeg on Windows (using DirectShow) to the browser as a streaming MP3 file. The audio needs to be as live as possible, with minimum/no buffering, and a "skipping" effect in the audio is perfectly acceptable.

  When I play the audio in Chrome using the HTML5 audio tag, there's a delay of about 8-10 secs over a low-latency LAN connection. I suspected this to be a client-side buffer, and used a Flash MP3 player on the client-side, which brought down the delay to 2-3 secs.

  Now, the buffering seems to taking place on the server-side. The documentation for NodeJS's response.write mentions that the data is written kernel buffers. How do I go about avoiding any buffering altogether or at least getting around it, so that the client always gets the latest audio data ? Strategies for handling 'drain' events to always push live data ?

  On the request object, I've used setNoDelay(true) to avoid the use of Nagle's algorithm. Following is a snippet of how data is written when the spawned ffmpeg process emits data.

  var clients = []; //List of client connections currently being served
  
  ffmpeg.stdout.on('data', function(data) {
  
      for(var i = 0; i < clients.length; i++){
  
          clients[i].res.write(data);
  
      }
  
  });