Hello,
I have a miro DC10 and liked to use it for recording video. I remember
it definitely working with lavrec as I converted at least two VHS tapes
to DVD with it (using composite input).
Unfortunately, things changed. lavrec suddenly was missing from the
latest mjpegtools in Ubuntu, so I switched to arch. Here, lavrec is
available again. Still, it doesn't want to record.
Driver for the capture card (zr36067) is loaded. I already knew from
last time that the "card=x"-parameter is needed. /dev/video0 is
available. I can access it with several tools and see the video:
xawtv -device /dev/video0
tvtime -d /dev/video0
mplayer tv:///dev/video0
vlc v4l2:///dev/video0
symlinking to /dev/video makes all of these work on /dev/video, too. So
I guess, lavrev should work even when defaulting to /dev/video. I also
tried setting environment variable LAV_VIDEO_DEV. As setting it to a
clearly nonexisting path (/dev/videoblabla) makes lavrec notice it (No
such file or directory), I guess that lavrec sees my card correctly.
vlc can record from there. streamer did, too.
Still I wanted to use lavrec as it seems better suited for this hardware
and supports hardware compression (MJPEG). Also, audio was missing when
recording with the other tools although that seems a rather minor issue
and easy to fix.
Lavrec exists with an error message:
**ERROR: [lavrec] Error setting channel: Inappropriate ioctl for device
**ERROR: [lavrec] Something went wrong while setting up the card
I'm also kind of puzzled as I get the
INFO: [lavrec] Auto detecting input and norm ...
right before the error message - even when supplying input and norm via
parameter (-i p). I used -v 1000 for this one so I guess I won't get any
more verbose information.
Linux Kernel version: 3.8.3-2-ARCH #1 SMP PREEMPT Sun Mar 17 13:04:22
CET 2013 x86_64 GNU/Linux
Module version: modinfo zr36067
filename:
/lib/modules/3.8.3-2-ARCH/kernel/drivers/media/pci/zoran/zr36067.ko.gz
version: 0.10.1
lavrec version: lavtools version 2.0.0: lavrec
I also started with "error mapping audio buffer" but found out to try it
with -U instead.
The ioctl-Message reminds me of an error I got when trying v4l2-compliance:
Required ioctls:
fail: v4l2-compliance.cpp(286): (vcap.version >> 16) < 3
test VIDIOC_QUERYCAP: FAIL
but I don't know whether those two are connected.
I feel like I'm only a small tweak in the v4l-controls, a single
parameter for lavrec or tiny detail when loading the driver away from
the solution. Still, I don't know what to try anymore and hope that
someone on this list has some ideas.
Regards,
Markus
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
