Recherche avancée

Sur d’autres sites (8391)

• Issue capturing video within device specs from a USB Grabber with ffmpeg & directshow

  11 octobre 2019, par leoncvlt

  I am using a USB Grabber (this one : http://www.logilink.com/Suche/vg0001a) to capture some old VHS footage. I am using ffmpeg with directshow to do so. The device properties are as follows :

  [dshow @ 000001d57618a300] DirectShow video device options (from video devices)
  
  [dshow @ 000001d57618a300]  Pin "Capture" (alternative pin name "0")
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=640x480 fps=5 max s=640x480 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=160x120 fps=5 max s=160x120 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=176x144 fps=5 max s=176x144 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=320x240 fps=5 max s=320x240 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=352x288 fps=5 max s=352x288 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=720x480 fps=5 max s=720x480 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuyv422  min s=720x576 fps=5 max s=720x576 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuv420p  min s=640x480 fps=5 max s=640x480 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuv420p  min s=160x120 fps=5 max s=160x120 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuv420p  min s=176x144 fps=5 max s=176x144 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuv420p  min s=320x240 fps=5 max s=320x240 fps=30
  
  [dshow @ 000001d57618a300]   pixel_format=yuv420p  min s=352x288 fps=5 max s=352x288 fps=30
  
  [dshow @ 000001d57618a300] Crossbar Switching Information for USB2.0 Grabber:
  
  [dshow @ 000001d57618a300]   Crossbar Output pin 0: "Video Decoder" related output pin: 1 current input pin: 0 compatible input pins: 0 1
  
  [dshow @ 000001d57618a300]   Crossbar Output pin 1: "Audio Decoder" related output pin: 0 current input pin: 4 compatible input pins: 3 4
  
  [dshow @ 000001d57618a300]   Crossbar Input pin 0 - "Video Composite" related input pin: 4
  
  [dshow @ 000001d57618a300]   Crossbar Input pin 1 - "S-Video" related input pin: 4
  
  [dshow @ 000001d57618a300]   Crossbar Input pin 2 - "Video Tuner" related input pin: 3
  
  [dshow @ 000001d57618a300]   Crossbar Input pin 3 - "Audio Tuner" related input pin: 2
  
  [dshow @ 000001d57618a300]   Crossbar Input pin 4 - "Audio Line" related input pin: 0

  I ran some tests and can capture and re-encode on the fly just fine at a variety of resolutions at both yuv420p and yuyv422 with the following command :

  ffmpeg -f dshow -pixel_format yuyv422 -video_size 720x480 -framerate 25 -i video="USB2.0 Grabber":audio="Digital Audio Interface (USB Audio Interface)" -c:v libx264 -crf 18 -aspect 4:3 -vf "yadif=1" -pix_fmt yuv420p -c:a aac -b:a 392k capture.mp4

  However, when I set -pixel_format yuyv422 -video_size 720x576 -framerate 25 which is within specs of the device, the process fails with a Too many packets buffered for output stream 0:1.. I tried increasing the buffer size with -rtbufsize and while the process starts, the video is never captured and the frame count is stuck at zero while converting - audio is captured fine.

  I thought it was the encoding not being able to keep up, but streaming the video or capturing the raw video feed with -vcodec copy I encounter the same issues.

  Using VLC to play from a capture device plays the audio only when using 720x576 as the size, while lower resolutions play fine, which make me think the issue is either with the device or me leaving out some specific directshow option.

  Any ideas ?

• ffprobe File not fournd error due long path BUT windows long path enabled

  10 novembre 2020, par nonayme

  I have a python program which run ffprobe on some videos on my win10 computer, and its working fine for most of them. The buggy ones have pretty long path, which seems to be the issue despite a "No Such file or Directory" message from ffprobe, this because :

  


  

  • I checked the path and it exists

  


  • In cmd when I mannualy cd to the directory and start ffprobe -i autocompletion complete with the right name

  


  • Windows Sub-system Linux achieve to run ffprobe from my copy pasted path extracted from my program

  


  


  => the file exist

  


  

  • I made a copy of my file and renamed it with a longer name than the buggy one (ffprobe doesn't work), and also with a really short name (ffprobe works)

  


  


  => path size is the culprit
BUT I have enabled long path on both the registry AND the group policy... any ideas ?

  


• Electron ffmpeg library reloads react application front end on video conversion

  22 août 2022, par David Chavez

  I'm using this ffmpeg library using its save method :

  


  const file = await video.save(_path.join(__dirname, `./my/path.mp4`));

  


  I'm using the .save() method to start video conversion because I also need to use the .addCommand() method.

  


  My problem is that when the promise is created AND when it's resolved, my react front end reloads so the screen turns white for a bit and reloads all of my components.

  


  How can I start video conversion without reloading the front end ?