[FFmpeg-user] screencast in WinXP

[Pablo Rodríguez]

On 11/17/2014 08:06 PM, Carl Eugen Hoyos wrote:
> Pablo Rodríguez <oinos <at> web.de> writes:
> 
>> but I forgot to copy the complete output
> 
> Please do so if you ask for support on this 
> mailing list.

This is the complete error message:

ffmpeg -f gdigrab -framerate 6 -i desktop -f dshow -i audio="Microphone"
-vcodec libx264 -crf 0 -p reset ultrafast -acodec pcm_s16le output.flv
ffmpeg version N-66289-gb76d613 Copyright (c) 2000-2014 the FFmpeg
developers
  built on Sep 15 2014 22:02:10 with gcc 4.8.3 (GCC)
  configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r
--enable-gnutls --enable-iconv --enable-libass --enable-libbluray
--enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme
--enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libopenjpeg --enable-libopus --enable-librtmp
--enable-libschroedinger --enable-libsoxr --enable-libspeex
--enable-libtheora --enable-libtwolame --enable-libvidstab
--enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis
--enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264
--enable-libx265 --enable-libxavs --enable-libxvid --enable-decklink
--enable-zlib
  libavutil      54.  7.100 / 54.  7.100
  libavcodec     56.  1.100 / 56.  1.100
  libavformat    56.  4.101 / 56.  4.101
  libavdevice    56.  0.100 / 56.  0.100
  libavfilter     5.  1.100 /  5.  1.100
  libswscale      3.  0.100 /  3.  0.100
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  0.100 / 53.  0.100
[gdigrab @ 02ddc020] Capturing whole desktop as 1280x1024x32 at (0,0)
Input #0, gdigrab, from 'desktop':
  Duration: N/A, start: 1416293523.415939, bitrate: 251660 kb/s
    Stream #0:0: Video: bmp, bgra, 1280x1024, 251660 kb/s, 6 tbr, 1000k
tbn, 6 tbc
[dshow @ 02ddf800] Could not find audio device.
audio=Microphone: Input/output error

This is all Greek to me. But I don’t understand why the same machine was
able to detect it before
(https://ffmpeg.org/pipermail/ffmpeg-user/2014-November/024230.html).

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk