Recherche avancée

Sur d’autres sites (14963)

• Slow start time in FFmpeg conversion - Seeking advice on optimization and identifying unnecessary flags [closed]

  30 novembre 2023, par Mohamed Dhouib

  I'm currently facing an issue with the startup time of FFmpeg conversion from RTSP stream to DASH stream in my application.
The conversion process takes longer to initiate than expected (sometimes even 15 seconds), impacting overall performance.
I've provided the relevant FFmpeg used options flags below :

  


      "-g 48",
    "-map 0:v:0",
    "-pix_fmt yuv420p",
    "-f dash",
    "-window_size 5",
    "-use_template 1",
    "-g 48",
    "-sc_threshold 0",
    "-vf scale=1920:1080",
    "-c:a aac",
    "-ar 48000",
    "-ac 2",
    "-strict experimental",
    "-max_muxing_queue_size 1024",
    "-c:v libx264",
    "-use_timeline 0"
    `-preset medium`,
    `-b:v 500k`,
    `-s 1280x720`,
    `-r 30`


  


  I'm looking for guidance on optimizing the FFmpeg configuration by adding new flags or identifying any unnecessary flags that might contribute to the slow start time.
The goal is to reduce the time it takes for FFmpeg to start the conversion process.
I appreciate any insights or recommendations on how to improve the startup time of FFmpeg conversion in my application.

  


  Relevant Dependencies :

  


  "@ffmpeg-installer/ffmpeg" : "^1.1.0",
"fluent-ffmpeg" : "^2.1.2",

  


  I am expecting the first stream chunk to be created in the first 3 seconds or so but it takes a lot more than that ( about 10 seconds )

  


• FFmpeg ignores some HTTP options when using the PUT method

  6 mars 2020, par mehdi.r

  I am using FFmpeg to create a CMAF stream and I upload it to an AWS resource (AWS MediaStore) using the PUT method of FFMpeg.
  I need to pass the Content-Type header when uploading manifests & segments.
  I have 3 type of files :

  application/x-mpegURL : m3u8 manifest

  application/dash+xml : mpd manifest

  video/mp4 : video segments

  Currently, all the types are set to Binary - octet-stream in the AWS resource (AWS MediaStore).
  As I will upload a huge number of files, I can’t use AWS Lambda functions to set the correct content type after a file as been uploaded.

  FFmpeg upload logs

  [https @ 0x555fe7a7d1c0] Opening 'https://XXXX.YYYY.amazonaws.com/chunk-stream0-00001.mp4' for writing
  
  [https @ 0x555fe7a7d0c0] request: PUT /chunk-stream0-00001.mp4 HTTP/1.1
  
  Transfer-Encoding: chunked
  
  User-Agent: Lavf/58.28.100
  
  Accept: */*
  
  Connection: keep-alive
  
  Host: XXXXX.YYYY.amazonaws.com
  
  Icy-MetaData: 1

  My tries

  I tried static builds & master branch of FFMpeg.
  I tried different ways to pass the content type, without success :

  -mime_type 1 -headers "Content-type: video/mp4\r\n"

  -mime_type "video/mp4,application/dash+xml,application/x-mpegURL"

  -content_type application/dash+xml

  -multiple_requests 1  -headers "a:b" -icy 0

  Upload command :

  ./ffmpeg -re -i ~/videos/BigBuckBunny.mp4 -loglevel debug \
  
    -map 0 -map 0 -map 0 -c:a aac -c:v libx264 -tune zerolatency \
  
    -b:v:0 2000k -s:v:0 1280x720 -profile:v:0 high -b:v:1 1500k -s:v:1 640x340  -profile:v:1 main -b:v:2 500k -s:v:2 320x170  -profile:v:2 baseline -bf 1 \
  
   -keyint_min 24 -g 24 -sc_threshold 0 -b_strategy 0 -ar:a:1 22050 -use_timeline 1 -use_template 1 -window_size 5 \
  
   -adaptation_sets "id=0,streams=v id=1,streams=a" -hls_playlist 1 -seg_duration 3 -streaming 1 \
  
   -strict experimental -lhls 1 -remove_at_exit 0 -master_m3u8_publish_rate 3 \
  
   -f dash -method PUT -http_persistent 1  https://example.com/manifest.mpd

  Any help would be highly appreciated.

  Reference :
  https://www.ffmpeg.org/ffmpeg-protocols.html#http

• FFmpeg segment desktop capture and send over http

  18 décembre 2014, par static

  I’m trying to capture the desktop video and segment it in order to send it over http to my node.js server, where I want to encode it to multiple bit-rates in order to serve it to clients for live streaming.
  The video has to be received in segments in order to create the manifest for live streaming, because i’m trying to use DASH, and to play the video on the client side using dash.js.

  The problem is that i can’t seem to be able to segment the video properly when i’m sending it to the server.

  This is the ffmpeg command that i’ve tried :

  ffmpeg -rtbufsize 1500M -f dshow -r 10 -i video="UScreenCapture"
  
  -vcodec libvpx -crf 10 -quality good -cpu-used 3 -b:v 1000k -qmin 10 -qmax 42  -
  
  threads 2 -vf scale=-1:480 -bufsize 1500 -flags -global_header -map 0 -f stream_
  
  segment -segment_time 2 -segment_format webm -  http://localhost:3000/stream/22

  I’ve managed to send it over http without segmenting the video, but on the server side i need to receive segments that have a duration of 2 seconds so that i can create the manifest.

  Also processing the video on the server side is also going to be done using ffmpeg(fluent ffmpeg module).
  I’m open to any suggestions.