I have it working - see below :) > > 3) Occasionally flipping channels results in the sound being messed up: by > > flipping back and forth I can often rectify this. In fullscreen mode, > > flipping channels sometimes results in a black-screen with the correct > > sound: again, flipping back and forth fixes this. > > I occasionally see the video black screen problem also. Somehow the video > sync is lost and the driver stops sending video data? (I'm speculating > here) > > As for sound being messed up, do you mean sound / channel mismatch? I have a problem where now and again, changing to a channel results in whitish noise rather than proper sound. Changing back to another channel a few times fixes it, until I change channel again. Am I the only one experiencing this? > > 5) Capturing of video seems impossible: I seem to be able to capture audio > > fine, but trying to capture video never works. I get the same errors as > > reported by Dave Antliff who has exactly the same card as me (same > > make/model, same chipset, same tuner-type). > > > > I've tried on 2.4.19-pre10 running on RH 7.3, ASUS A7S333 motherboard, ATI > Rage Pro 4MB (old!), FlyVideo2000, latest saa7134 snapshot (June 4), mp1e > 1.9.1 with v4l2 patch (enable O_RDWR), and I get a hard kernel lock due to > a NULL pointer dereference (same thing as reported by Dave). > > I think saa7134 is horribly broken wrt. mp1e support. Don't know where the > problem is... (Gerd?) > > Has anyone gotten mp1e to work with a v4l2 based driver/card other than > saa7134? It'd be interesting to compare notes. Yes, I've got it working! The new saa7134 driver from bytesex.org (20020605) works like a charm. Btw, if you're using mp1e, don't forget the -p option (uses esd by default - might not work for you). So, the only problem I have left is the noise one - anybody else experience this? Maybe I have a duff card? (Might try it in windows just to see, only last time I did that it blue-screened). Dave.
