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 Linux. ----- Forwarded message from Roger <rogerx.oss@gmail.com> ----- Subject: Hauppauge WinTV-7164 Analog Composite/S-Video Capture Date: Sat, 30 Apr 2022 14:50:31 -0400 From: Roger <rogerx.oss@gmail.com> To: ffmpeg-user@ffmpeg.org Seems I'm plagued by the same bug as described here: https://stackoverflow.com/questions/19113197/ffmpeg-directshow-capture-2-pin... 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 Analog Capture" (NTSC Model 2250) This Hauppauge PCIe device, likely many Hauppuage video capture cards, capture a video stream already combined with an audio stream. The bug and fix posted to stackoverflow is similar. When specifying the following, either with/without ~Audio (pin 1), I do get an audio stream detected, but the audio stream is null/silent: D:\record-ffmpeg>ffplay -f dshow -rtbufsize 500M -video_size 720x480 -framerate 29.97 -audio_pin_name ~Audio -show_video_device_dialog false -i video="Hauppauge WinTV-7164 Analog Capture":audio="Hauppauge WinTV-7164 Analog Capture" D:\record-ffmpeg>ffplay -f dshow -video_size 352x288 -i video="Hauppauge WinTV-7164 Analog Capture":audio="Hauppauge WinTV-7164 Analog Capture" ffplay version 5.0.1-full_build-www.gyan.dev Copyright (c) 2003-2022 the FFmpeg developers built with gcc 11.2.0 (Rev7, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint libavutil 57. 17.100 / 57. 17.100 libavcodec 59. 18.100 / 59. 18.100 libavformat 59. 16.100 / 59. 16.100 libavdevice 59. 4.100 / 59. 4.100 libavfilter 8. 24.100 / 8. 24.100 libswscale 6. 4.100 / 6. 4.100 libswresample 4. 3.100 / 4. 3.100 libpostproc 56. 3.100 / 56. 3.100 [dshow @ 0000020e9bb04f00] Could not find audio only device with name [Hauppauge WinTV-7164 Analog Capture] among source devices of type audio. [dshow @ 0000020e9bb04f00] Searching for audio device within video devices for Hauppauge WinTV-7164 Analog Capture Input #0, dshow, from 'video=Hauppauge WinTV-7164 Analog Capture:audio=Hauppauge WinTV-7164 Analog Capture': Duration: N/A, start: 3738.527811, bitrate: 1536 kb/s Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 352x288, 29.97 fps, 29.97 tbr, 10000k tbn Stream #0:1: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s 3740.13 A-V: -0.010 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0 D:\record-ffmpeg> It's possible the fix was, possibly a hack/workaround, specifically applied only for certain devices such as "AJA Capture Source". Many Hauppauge capture cards should be added as well. Sometimes right after booting into Windows 10, I may get ffplay to play audio only with a blue screen. Subsequent ffplay executions drop audio, with a blue screen, until either Hauppauge's WinTV10 or VirtualDub64 are subsequently executed, likely properly initializing the video capture card. Subsequent ffplay executions show video properly but again without audio, only stating the video/audio stream specifications. Nor is the audio stream recorded to file using ffmpeg. ----- End forwarded message -----