Your message dated Sat, 26 Jul 2014 14:00:56 -0400
with message-id
<CAJ0cceaFDo1RQQezk_s=4t6-qxsixeyuwb62bo5ai2dnyqt...@mail.gmail.com>
and subject line Seems to work
has caused the Debian Bug report #663891,
regarding ffmpeg: little bug with redirection
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
663891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663891
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ffmpeg
Version: 4:0.5.4-1
Severity: minor
ffmpeg -f alsa -ac 2 -i hw:0,0 -f video4linux2 -i /dev/video0 pipe: | cat >
test2.avi
$ ffmpeg -f alsa -ac 2 -i hw:0,0 -f video4linux2 -i /dev/video0 pipe: | cat
> test2.avi
FFmpeg version SVN-r0.5.4-4:0.5.4-1, Copyright (c) 2000-2009 Fabrice Bellard,
et al.
configuration: --extra-version=4:0.5.4-1 --prefix=/usr --enable-avfilter
--enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libdirac
--enable-libgsm --enable-libopenjpeg --enable-libschroedinger --enable-libspeex
--enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib
--disable-stripping --disable-vhook --enable-runtime-cpudetect --enable-gpl
--enable-postproc --enable-swscale --enable-x11grab --enable-libfaad
--enable-libdc1394 --enable-shared --disable-static
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 1 / 52.20. 1
libavformat 52.31. 0 / 52.31. 0
libavdevice 52. 1. 0 / 52. 1. 0
libavfilter 0. 4. 0 / 0. 4. 0
libswscale 0. 7. 1 / 0. 7. 1
libpostproc 51. 2. 0 / 51. 2. 0
built on Mar 26 2011 22:50:57, gcc: 4.4.5
Input #0, alsa, from 'hw:0,0':
Duration: N/A, start: 20636.988357, bitrate: N/A
Stream #0.0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
[video4linux2 @ 0x93da3a0]Wrong size (0x0)
/dev/video0: Error while opening file
it should however work
it works wiht a file:
ffmpeg -f alsa -ac 2 -i hw:0,0 -f avi pipe: | cat > test2.avi
someday a fix would be helpful.
Thank for ffmpeg !
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ffmpeg depends on:
ii libavcodec52 4:0.5.2-6 ffmpeg codec library
ii libavdevice52 4:0.5.2-6 ffmpeg device handling library
ii libavfilter0 4:0.5.2-6 ffmpeg video filtering library
ii libavformat52 4:0.5.2-6 ffmpeg file format library
ii libavutil49 4:0.5.2-6 ffmpeg utility library
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libpostproc51 4:0.5.2-6 ffmpeg video postprocessing librar
ii libsdl1.2debian 1.2.14-6.1 Simple DirectMedia Layer
ii libswscale0 4:0.5.2-6 ffmpeg video scaling library
ffmpeg recommends no packages.
ffmpeg suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 6:9.14-1
I have verified that the following command works for me:
$ avconv -f video4linux2 -i /dev/video0 -f vob pipe: | cat > /tmp/foo.vob
avconv version 9.14-6:9.14-0ubuntu0.14.04.1, Copyright (c) 2000-2014
the Libav developers
built on Jul 15 2014 13:57:40 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
[video4linux2 @ 0x1756f60] Estimating duration from bitrate, this may
be inaccurate
Input #0, video4linux2, from '/dev/video0':
Duration: N/A, start: 46077.065726, bitrate: 147456 kb/s
Stream #0.0: Video: rawvideo, yuyv422, 640x480, 147456 kb/s, 1000k
tbn, 30 tbc
[vob @ 0x17577c0] VBV buffer size not set, muxing may fail
Output #0, vob, to 'pipe:':
Metadata:
encoder : Lavf54.20.4
Stream #0.0: Video: mpeg2video, yuv420p, 640x480, q=2-31, 200
kb/s, 90k tbn, 25 tbc
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo -> mpeg2video)
Press ctrl-c to stop encoding
I'm therefore considering this issue as fixed and close this bugreport
based on this. Feel free to followup if you have additional questions.
--
regards,
Reinhard
--- End Message ---
