Recherche avancée

Sur d’autres sites (9597)

• FFMPEG hardware acceleration in Windows Scheduled Task [closed]

  25 mars 2022, par cfairer

  I'm setting up an unattended Windows 10 machine that will stream video from an RTSP nest cam feed using FFMPEG and Apache.
As it will be unattended and will lose power for six hours a day, I have created a Scheduled Task to run at boot without a user logged to run ffmpeg.

  


  It all works fine with conventional encoders for task started automatically or manually by Windows Task Scheduler :
ffmpeg.exe -i rtsp ://user:pw@nestcam:554 -vf scale=1280:720 -vcodec libx264 -g 20 -r 10 -b:v 1120000 -crf 31 -map 0 -map -0:a -acodec aac -sc_threshold 0 -f hls -hls_time 2 -segment_time 2 -hls_flags delete_segments -hls_list_size 20 C :\webpages\video\stream.m3u8

  


  It works fine when I use hardware acceleration too, but only outside Task Scheduler (e.g. a command prompt) :
ffmpeg.exe -init_hw_device qsv=hw -filter_hw_device hw -i rtsp ://user:pw@nestcam:554 -vf hwupload=extra_hw_frames=64,format=qsv -c:v h264_qsv -g 20 -r 10 -b:v 1120000 -crf 31 -map 0 -map -0:a -acodec aac -sc_threshold 0 -f hls -hls_time 2 -segment_time 2 -hls_flags delete_segments -hls_list_size 20 C :\webpages\video\stream.m3u8

  


  The hardware accelerated version fails when executed by Windows Task Scheduler, whether started automatically or manually. The relevant output is as follows :
[AVHWDeviceContext @ 00000184ba5cc800] Failed to create Direct3D device
Device creation failed : -1313558101.
Failed to set value 'qsv=hw' for option 'init_hw_device' : Unknown error occurred
Error parsing global options : Unknown error occurred

  


  Why can't the ffmpeg task started by Task Scheduler see the hardware-accelerated hardware ? Any ideas on how to resolve this ?

  


  The hardware-accelerated version reduces the load on the CPU by about 75% (ie 50% down to 13%), so it's a significant benefit.

  


  Thanks

  


• FFMPEG Multiple outputs from BlackMagic input

  24 septembre 2018, par leo_dragons

  I’m currently needing help to achieve multiple outputs from one input.
  Right now, the outputs are set like this :

  ffmpeg -re -f decklink -i "DeckLink Mini Recorder" -y -pix_fmt yuv420p -c:v h264 -preset fast -tune zerolatency -c:a aac -ac 2 -b:a 128k -ar 44100 -async 1 -b:v 2300k -g 5 -probesize 32 -framerate 30 -movflags +faststart -s 1280x720 -bufsize 1000k -maxrate 3072k -shortest -f flv "rtmp://10.0.0.172:1935/Testing/live_720p"
  
  ffmpeg -re -i "rtmp://10.0.0.172:1935/Testing/live_720p" -c:v h264 -preset fast -tune zerolatency -c:a aac -ac 2 -b:a 114k -ar 44100 -async 1 -b:v 900k -g 5 -probesize 32 -framerate 30 -movflags +faststart -s 854x480 -bufsize 400k -maxrate 1000k -shortest -f flv "rtmp://10.0.0.172:1935/Testing/live_480p_hq"
  
  ffmpeg -re -i "rtmp://10.0.0.172:1935/Testing/live_720p" -c:v h264 -preset fast -tune zerolatency -c:a aac -ac 2 -b:a 114k -ar 44100 -async 1 -b:v 550k -g 5 -probesize 32 -framerate 30 -movflags +faststart -s 854x480 -bufsize 400k -maxrate 500k -shortest -f flv "rtmp://10.0.0.172:1935/Testing/live_480p_lq"
  
  ffmpeg -re -i "rtmp://10.0.0.172:1935/Testing/live_720p" -c:v h264 -preset fast -tune zerolatency -c:a aac -ac 2 -b:a 114k -ar 44100 -async 1 -b:v 450k -g 5 -probesize 32 -framerate 30 -movflags +faststart -s 640x360 -bufsize 400k -maxrate 500k -shortest -f flv "rtmp://10.0.0.172:1935/Testing/live_360p" 

  This uses quite a lot of processing power, and also generates unnecessary latency (since I have to stream to WOWZA first, then back to FFMPEG and then back to WOWZA).

  And I want to optimize this.

  I’ve been trying several methods, but I only managed to overflow the decklink buffer. How could I solve this ?

• Real-Time Buffer Too Full (FFMPEG)

  25 janvier 2018, par Nimble

  So I’ve been having this issue with ffmpeg, it has been a journey getting the hardware and command to actually do what I want, but I still have one problem.

  Sometimes when I’m recording I just start dropping frames like crazy, this can be after an hour of recording or even ten hours in... Everything will be working fine and then suddenly I’ll start dropping frames due to "real-time buffer too full or near too full". This happens regardless of how low I put the bitrate, and the buffer size is high as it will allow, eventually I’ll just start dropping frames. Almost seems like it could be like a power saving feature kicking in but it’s too inconsistent it seems. Like I said sometimes I can go 10 hours without having this issue.

  Any ideas ?

  Here is my block of code :

  ffmpeg -guess_layout_max 0 -y -f dshow -video_size 3440x1440 -rtbufsize 2147.48M -pixel_format nv12 -framerate 200 ^
  
  -i video="Video (00 Pro Capture HDMI 4K+)":audio="SPDIF/ADAT (1+2) (RME Fireface UC)" -map 0:0,0:1 -map 0:1 ^
  
  -preset: llhp -codec:v h264_nvenc -pix_fmt nv12 -b:v 250M -maxrate:v 250M -minrate:v 250M -bufsize:v 250M -b:a 320k ^
  
  -ac 2 -r 100 -async 1 -vsync 1 -segment_time 600 -segment_wrap 9 -f segment C:\Users\djcim\Videos\PC\PC%02d.mp4 ^
  
  -guess_layout_max 0 -f dshow -rtbufsize 2000M -i audio="Analog (3+4) (RME Fireface UC)" -map 1:0 -b:a 320k -ac 2 ^
  
  -af "adelay=200|200" -segment_time 600 -segment_wrap 9 -f segment C:\Users\djcim\Videos\PC\Voices\Theirs\TPC%02d.wav ^
  
  -guess_layout_max 0 -f dshow -rtbufsize 2000M -i audio="Analog (5+6) (RME Fireface UC)" -map 2:0 -b:a 320k -ac 2 ^
  
  -af "adelay=825|825" -segment_time 600 -segment_wrap 9 -f segment C:\Users\djcim\Videos\PC\Voices\Mine\MPC%02d.wav

  Here is the error, it repeated around 300 times before locking up ffmpeg forcing my to quit before starting the recording again :

  [dshow @ 0000019a596bdcc0] real-time buffer [Video (00 Pro Capture HDMI 4K+)] [video input] too full or near too full (62% of size: 2147480000 [rtbufsize parameter])! frame dropped!