Hi Luke, Es schrieb Luke Rosenthal: > > Hi, > > I can't seem to get nvrec-20030316 snapshot working with saa7134-0.2.6 > (0.2.7 hangs on unload for me too). Running RH 7.3, 2.4.20 with v4l2 > patches applied. This is what happens: > Nvrec-20030316 is doing the job here too. Did not see the trouble with unloading the modules on saa7134-0.2.7 and on the 0.2.8-snapshot from 20030521, it was resolved by the 4 lines from Tom Zoerner (a md9717 is here thanks!). Also have sound on the recordings taking care, that IGain is somewhat up with kmix. (For testing I use "v4lctl -c /dev/video0 volume mute off" and audacity.) > [root@gw root]# divx4rec -v /dev/video0 -o test2.mpg When I put your command it works here (attached), even I use regulary .avi and .mov format and set the -D and -s option and also -norm PAL and -input Television, what should not be required. Don't think the .mpg trick will work to use the outcome directly for a vcd :) > Starting nvrec.c, version CVS-current (nvrec-CVS-current). > nvcore_parse_file(617): Error opening "/etc/nvrec.conf" > nvcore_parse_file(617): Error opening "/root/.nvrec.conf" > v4l1_core_init(323): Size: 384x288 from /dev/video0 > v4l1_core_init(393): Set window: Invalid argument Some of the conditions are not fullfilled. Set -D to get maybe some more out. Using tvtime to set a channel is very comfortable and using a 600 MHz cpu should do it. Even saa7134-0.2.6 was reported working, there are some good reasons to come up. > main(70): nvrec: initialising capture device: Invalid argument > > I think those dimensions (384x288) are reasonable, but no variation of > sizes (using the well known VCD/SVCD sizes etc) seems to yield any other > result. Here's the output from dmesg: > [snip] > > v4l1-compat: VIDIOCSWIN / VIDIOC_S_FMT #2: -22 > > That last line is triggered every time I try and fire up divx4rec. > This error you get in the ioctl translation from the old v4l to the new v4l2. "case VIDIOCSWIN: /* set window and/or capture dimensions */" You should easily find it in the kraxelpatch-2.4.20-20030410, which I use don't having this error with 0.2.7 and snapshot 0.2.8-20030521 with the 4 lines from Tom copied in. (update the driver) > streamer and ffmpeg can record from the card no problems (although I can't > seem to get ffmpeg and vcdimager to agree on a format, hence the use of > nvrec). I've searched high and low for the text of these errors and > can't seem to find any info, although I have a sneaky suspicion I'm > missing something obvious. Any ideas or pointers in the right direction? > Or can someone suggest a way to get ffmpeg to record in a format that > vcdimager will be happy with or is it a known incompatability? > Tested some time ago ffmpeg in conjunction with zapping. A/V is out of sync for that what you are looking for. > I've tried the nvrec-20030217 snapshot, also saa7134-0.2.7 too, same result. > So that is what I have. Don't know if it can help you ... Greetings Hermann --
