Recherche avancée

Sur d’autres sites (9132)

• hwcontext_vaapi : Return all formats for constraints without config

  18 juin 2016, par Mark Thompson

  hwcontext_vaapi : Return all formats for constraints without config
  No longer make a dummy device configuration to query.  Instead, just
  
  return everything we recognise from the whole format list.  Also
  
  change the device setup code to query that list only, rather than
  
  intersecting it with the constraint output.
  This makes hwupload more usable on mesa/gallium where the video
  
  processor only declares support for RGB formats, making it unable to
  
  deal with YUV formats before this patch.  It might introduce some
  
  different trickier failures in the internal upload/download code
  
  because the set of allowed formats there has changed, though I didn’t
  
  find any obvious regressions with i965.
  

  • [DBH] libavutil/hwcontext_vaapi.c

• Two USB cams to two rtsp-simple-servers simultaneously

  20 juin 2022, par Imm

  Like in title, I have 2 USB cams and I need to create two RTSP streams. I'm using FFmpeg and rtsp-simple-server and it's working with one cam with this configuration (rtsp-simple-server.yml) :

  


  paths:
  cam:
    runOnInit: ffmpeg -f dshow -video_device_number 0 -i video="UVC Camera" -c:v libx264 -preset ultrafast -tune zerolatency -b:v 600k -f rtsp rtsp://192.168.5.203:8554/cam
    runOnInitRestart: yes


  


  but I can't figure it out with second cam. I tried to make second instance of rtsp-simple-server in separete console and it doesn't work. I set it up like this (and few other ways with different port etc.) :

  


  paths:
  cam:
    runOnInit: ffmpeg -f dshow -video_device_number 1 -i video="UVC Camera" -c:v libx264 -preset ultrafast -tune zerolatency -b:v 600k -f rtsp rtsp://192.168.5.203:8555/cam2
    runOnInitRestart: yes


  


  I get this error as result : Only one use of each socket address (protocol / network address / port) is allowed. and I still think there is better way to solve this with proper configuration.

  


  I hoping for your help !

  


• vp9 : use superframe split BSF

  17 novembre 2017, par wm4

  vp9 : use superframe split BSF
  webm usually has invisible superframes merged with normal frames.
  
  (vpxenc muxes them in this form, which is evidence enough that this is
  
  the standard webm packet format. It's rather unclear whether ffmpeg is
  
  even allowed to remux them with split packets.)
  The vp9 decoder needs them to be in separate packets for multithreading
  
  to work. Add the BSF to the decoder, so the conversion happens
  
  automatically.
  This contains the important part of fa1749dd34c55fb9, which
  
  was apparently skipped in commit d417e95af76. This restores Libav API
  
  compatibility.
  

  • [DH] libavcodec/version.h
  • [DH] libavcodec/vp9.c