Recherche avancée

Sur d’autres sites (12292)

• Add 2 watermark with scale2ref 40 percent width of video and timeout using FFmpeg

  3 septembre 2020, par Arun Maurya

  Add 2 watermark with scale2ref 40 percent width of video and timeout using FFmpeg

  


  timeout for the top right corner (first 8 sec) then the bottom right corner till the end time.

  


  ffmpeg -i 1597739850_368007908.mp4 -i artistsharleen.png -i artistsharleen.png -filter_complex "[1][0scale2ref=w='iw*40/100':h='ow/mdar'[wm][vid];[vid][wm]overlay=10:40:enable='between(t,0,8)'"[v1];[v1][2]scale2ref=w='iw*40/100':h='ow/mdar'[a][b];[b][a]overlay=main_w-overlay_w-10:main_h-overlay_h-10:enable='gt(t,8)[v2]" -map "[v2]" -map 0:a 17780739871599156232.mp4

  


  I'm able to place 2 watermarks with keyframe

  


  ffmpeg -i video.mp4 -i image2.png -i image2.png -filter_complex "[0][1]overlay=10:10:enable='between(t,0,8)'[v1];[v1][2]overlay=main_w-overlay_w-10:main_h-overlay_h-10:enable='gt(t,8)'[v2]" -map "[v2]" -map 0:a output.mp4

  


  but my images are not getting scaled as per video resolution, that's why i want to integrate scale2ref in this command

  


  Hope someone also faces this problem, can help me.

  


• HTML5 Progressive Streaming — no follow-up range requests

  20 septembre 2023, par user2333829

  I'm working on an embedded device that is recording video on the fly. I'd like to stream that to an HTML5 video element, using our own custom server. I have this almost working and would like some help.

  



  So far as I can tell, I've got libav / ffmpeg doing their job right. I encoded an mp4 in RAM with the moov atom at the start of the file. I've written this file to disk and it plays everywhere it should.

  



  The problem, I think, lies with how I'm responding to HTTP range requests. When I try to do a live stream, I get an initial range request from the browser / player (currently tried Chrome, Firefox, and VLC) for bytes:0-. I responded with some initial bytes. The browser / player actually plays this fine, but never asks again. So the live stream doesn't work, just the first 3 seconds or whatever.

  



  I've looked at the RFC spec of partial content, and my understanding is I'm doing what I should be... Clearly I'm not though. Here is an example of a request / response with Chrome as the requester :

  



  ---

  



  
get /live.mp4 HTTP/1.1
host: localhost:1235
connection: keep-alive
accept-encoding: identity;q=1, *;q=0
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
accept: */*
dnt: 1
accept-language: en-GB,en-US;q=0.9,en;q=0.8
range: bytes=0-


  



  
HTTP/1.1 206 Partial Content
Accept-Ranges: bytes
Content-Type: video/mp4
Content-Length: 182400
Content-Range: bytes 0-182399/*


  



  ---

  



  Again, with that request / response pair, Chrome plays the first 182400 bytes but never makes a second request. I thought having the '*' in Content-Range would make this happen...

  


• Using FFMPEG to send headers

  4 février 2017, par max

  Following is the ffprobe command i used :

  ffprobe -headers "X-CloudFront-Secret: mysecret" -v error -show_format -show_streams -print_format json "myurl"

  However, I get the response access denied from the server. It seems that the header is not passed in correctly.

  To make sure that the header and the secret key I used is correct, i tried it with "curl" and it works.

  curl --header "X-CloudFront-Secret: mysecret" -i "myurl"

  Did I passed the headers in ffprobe command correctly ?
  What is the correct way to pass the header in ffprobe ?