VFW Capture support
Hello, First attempt for VFW capture support in Windows. For testing purposes only! Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap It prints lots of (somewhat useless) debug messages. Image is upside down =). I just have to find the right PIX_FMT and width/height... I'm way too tired to look at that now. Note: Run this FFmpeg from Windows' command prompts (cmd or command)! *Not MSys!*. This patch includes the patch I sent to ffmpeg-devel for interactive support for Windows. You must kill it with 'q' or Ctrl+C, or else the capture device won't be released, and you'll have to reboot Windows to get it back. MSys doesn't capture 'q' nor Ctrl+C, so it's doomed to make you loose control of the device. Ramiro Polla
ramiro at lisha.ufsc.br wrote:
Hello,
First attempt for VFW capture support in Windows. For testing purposes only!
Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap
I forgot to mention, when you run it, you must specify the width/height, and must also specify no audio stream (or provide an audio stream). Such as: ffmpeg -y -an -s "320x240" outfile.mpg Ramiro Polla
Hi,
Hello,
First attempt for VFW capture support in Windows. For testing purposes only!
Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap
It prints lots of (somewhat useless) debug messages. Image is upside down =). I just have to find the right PIX_FMT and width/height... I'm way too tired to look at that now.
Note: Run this FFmpeg from Windows' command prompts (cmd or command)! *Not MSys!*. This patch includes the patch I sent to ffmpeg-devel for interactive support for Windows. You must kill it with 'q' or Ctrl+C, or else the capture device won't be released, and you'll have to reboot Windows to get it back. MSys doesn't capture 'q' nor Ctrl+C, so it's doomed to make you loose control of the device.
Tried under Cygwin, I got this: $ ./ffmpeg -t 2 -y -an -s "320x240" outfile.mpg FFmpeg version SVN-r6907, Copyright (c) 2000-2006 Fabrice Bellard, et al. configuration: --enable-mp3lame --enable-a52 --disable-static --enable-shared --enable-pthreads --enable-swscaler --enable-avisynth --enable-gpl --extra-cflags=-march=pentium4 --enable-vfw-cap libavutil version: 49.0.2 libavcodec version: 51.24.0 libavformat version: 51.6.0 built on Nov 5 2006 23:14:45, gcc: 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) vfw_read_header called capCreateCaptureWindow 1048992 and then hanged, nor 'q' nor Ctrl+C worked. My VfW default device is my hybrid analog-digital TV card, a bad beast that only Graphedit or Windows Media Center seem able to understand (VirtualDub and others have failed on it), so the "hang" is expected. Do you know how could I get the list of video devices in Windows, in a format valid for option -vd? (I also have firewire and a DV camcorder, and I could try to capture from it instead) Regards, V?ctor P.S: there were some trailing CRs in patch
ramiro at lisha.ufsc.br wrote in news:2148.201.72.105.43.1162697376.squirrel at mail.lisha.ufsc.br:
Hello,
First attempt for VFW capture support in Windows. For testing purposes only!
Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap
hmm, i got a compile error on mingw... gcc -L/d/mplayer-testclips/ffmpeg/libavformat -L/d/mplayer- testclips/ffmpeg/libavcodec -L/d/mplayer-testclips/ffmpeg/libavutil -Wl,-- warn-common -Wl,-rpath-link,/d/mplayer-testclips/ffmpeg/libavcodec -Wl,- rpath-link,/d/mplayer-testclips/ffmpeg/libavformat -Wl,-rpath- link,/d/mplayer-testclips/ffmpeg/libavutil -g -o ffmpeg_g.exe ffmpeg.o cmdutils.o -lavformat -lavcodec -lavutil -lm -lz -lvfw32 d:/mplayer-testclips/ffmpeg/libavformat/libavformat.a(vfw_cap.o)(.text+ 0x2ca): In function `vfw_read_header': d:/mplayer-testclips/ffmpeg/libavformat/vfw_cap.c:99: undefined reference to `capCreateCaptureWindow' make: *** [ffmpeg_g.exe] Error 1 -compn
<ramiro <at> lisha.ufsc.br> writes:
Hello,
First attempt for VFW capture support in Windows. For testing purposes only!
Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap
It prints lots of (somewhat useless) debug messages. Image is upside down =). I just have to find the right PIX_FMT and width/height... I'm way too tired to look at that now.
Note: Run this FFmpeg from Windows' command prompts (cmd or command)! *Not MSys!*. This patch includes the patch I sent to ffmpeg-devel for interactive support for Windows. You must kill it with 'q' or Ctrl+C, or else the capture device won't be released, and you'll have to reboot Windows to get it back. MSys doesn't capture 'q' nor Ctrl+C, so it's doomed to make you loose control of the device.
Ramiro Polla Attachment (vfw_cap.4.patch): application/octet-stream, 12 KiB
_______________________________________________ ffmpeg-user mailing list ffmpeg-user <at> mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Hello Ramiro, Sorry for the naive questions - however, could you please send some instructions on how to apply the patch to the ffmpeg source tree that I downloaded today with SVN. I was getting errors when I applied the patch like this in the ffmpeg directory: patch -p1 < vfw-cap.4.patch Also, do you have a newer version of the patch? thanks, Sandeep
Hello, Sandeep Neema wrote:
<ramiro <at> lisha.ufsc.br> writes:
Hello,
First attempt for VFW capture support in Windows. For testing purposes only!
Enable it with: ./configure --enable-memalign-hack --enable-vfw-cap
It prints lots of (somewhat useless) debug messages. Image is upside down =). I just have to find the right PIX_FMT and width/height... I'm way too tired to look at that now.
Note: Run this FFmpeg from Windows' command prompts (cmd or command)! *Not MSys!*. This patch includes the patch I sent to ffmpeg-devel for interactive support for Windows. You must kill it with 'q' or Ctrl+C, or else the capture device won't be released, and you'll have to reboot Windows to get it back. MSys doesn't capture 'q' nor Ctrl+C, so it's doomed to make you loose control of the device.
Ramiro Polla Attachment (vfw_cap.4.patch): application/octet-stream, 12 KiB
_______________________________________________ ffmpeg-user mailing list ffmpeg-user <at> mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Hello Ramiro, Sorry for the naive questions - however, could you please send some instructions on how to apply the patch to the ffmpeg source tree that I downloaded today with SVN. I was getting errors when I applied the patch like this in the ffmpeg directory: patch -p1 < vfw-cap.4.patch Also, do you have a newer version of the patch?
Yes. I just sent a new e-mail to the list. It does not need --enable-vfw-cap anymore. It patches ok with current SVN. http://article.gmane.org/gmane.comp.video.ffmpeg.user/6822 Ramiro Polla
Dear Ramiro, Could you tell me how to use this in appl.? what function sequences to call? do you have some example? Thanks alot. Regards, Ginanjar Nur Rahmat
Ginanjar Nur Rahmat wrote:
Dear Ramiro,
Could you tell me how to use this in appl.? what function sequences to call? do you have some example?
Attached patch is the latest version for vfwcap. configure and make FFmpeg normally with MinGW. Then run: ffmpeg -r 25 -f vfwcap -i 0 -y output.avi Ramiro Polla
On 10/22/07, Ramiro Polla <ramiro at lisha.ufsc.br> wrote:
Ginanjar Nur Rahmat wrote:
Dear Ramiro,
Could you tell me how to use this in appl.? what function sequences to call? do you have some example?
Attached patch is the latest version for vfwcap.
configure and make FFmpeg normally with MinGW. Then run:
ffmpeg -r 25 -f vfwcap -i 0 -y output.avi
[...] Sorry to ask a basic question, but if this is used I noticed the input filename is 0. How would I point this to the real file to convert?
Jonathon Elwood wrote:
On 10/22/07, Ramiro Polla <ramiro at lisha.ufsc.br> wrote:
Ginanjar Nur Rahmat wrote:
Dear Ramiro,
Could you tell me how to use this in appl.? what function sequences to call? do you have some example? Attached patch is the latest version for vfwcap.
configure and make FFmpeg normally with MinGW. Then run:
ffmpeg -r 25 -f vfwcap -i 0 -y output.avi [...] Sorry to ask a basic question, but if this is used I noticed the input filename is 0. How would I point this to the real file to convert?
In linux this would be /dev/video0, but Windows doesn't think everything should be a file, so it doesn't create device files for the video devices. Instead, this number is passed as is to the VFW capture API, with 0 being the default device. Ramiro Polla
Ramiro Polla a ?crit :
Jonathon Elwood wrote:
On 10/22/07, Ramiro Polla <ramiro at lisha.ufsc.br> wrote:
Ginanjar Nur Rahmat wrote:
Dear Ramiro,
Could you tell me how to use this in appl.? what function sequences to call? do you have some example? Attached patch is the latest version for vfwcap.
configure and make FFmpeg normally with MinGW. Then run:
ffmpeg -r 25 -f vfwcap -i 0 -y output.avi [...] Sorry to ask a basic question, but if this is used I noticed the input filename is 0. How would I point this to the real file to convert?
In linux this would be /dev/video0, but Windows doesn't think everything should be a file, so it doesn't create device files for the video devices. Instead, this number is passed as is to the VFW capture API, with 0 being the default device.
Ramiro Polla
Is there a way to know whether a particular hardware can be captured in VFW? Or a list of such hardwares? -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
Michel Bardiaux wrote:
Is there a way to know whether a particular hardware can be captured in VFW? Or a list of such hardwares?
Winxp should have a wvfwrapper by default. So all hardware with a ds driver should work. MvH Benjamin Larsson
participants (9)
-
angustia＠arrozcru.no-ip.org -
banan＠ludd.ltu.se -
jaelwood＠gmail.com -
mbardiaux＠mediaxim.be -
neemask＠gmail.com -
ramiro＠lisha.ufsc.br -
rgnurrahmat＠yahoo.com -
tempn＠twmi.rr.com -
wzrlpy＠arsystel.com