> BUG: The device specific URLS provided by ffmpeg dshow "-list_devices" for
> this
> Hauppauge provided some extremely length device URLs that were apparently not
> recognized by the dshow video= and audio= options.
Examples please? :)
___
ffmpeg-user
Small correction on this, as users might obtain a not playable video/container
files from my prior incomplete instructions.
Use .avi container instead of .yuv!
c:\ ffmpeg -f dshow -crossbar_audio_input_pin_number 5
-crossbar_video_input_pin_number 2 -i video="Hauppauge WinTV-7164 Analog
Captu
Figured it out finally.
The Hauppauge 2250 (SAA7164 chip), has two tuners, each with dvb/analog
TV/composite/svideo inputs. The exact inputs need to be specied, else without
specifying, using ffmpeg on simply "Hauppauge WinTV-7164 Analog Capture" will
produce random results with inputs, inclu
I've found, after searching Google, the following on Linux pulls the entire
video+audio stream successfully:
$ cat /dev/video0 | ffplay -
or,
$ ffmpeg -i file:/dev/video0
Now to see if doing so within Windows does the same, likely omitting the "-f
dshow", similar to omitting the "-f v4l2" on
Seems I'm plagued by the same bug as described here:
https://stackoverflow.com/questions/19113197/ffmpeg-directshow-capture-2-pins
Hauppauge WinTV-7164 Analog Composite/S-Video Capture
Using this device trying to capture composite/s-video from VCR/VHS media.
dshow device: "Hauppauge WinTV-7164 A
