Hi Wolfgang, On Fri, 2003-01-03 at 03:18, Wolfgang Goeller wrote: > I think this is the price for the integrated tuner: > lavrec must gain control over the tuner when it wants to > record and any "watch-application" can also only work if it's > in control of the tuner. > The other cards get the signal and thus you can easily see, > what they get - it does not disturb the cards. The only > thing you can't do with dc10 and the like cards: Starting > or closing say xawtv during recording. > That's also easy to see why: When say xawtv starts it want's > to setup the card - and that's bad, since the card is recording. > If say xawtv closes it want's to close the data stream. > Both is poison for the recording-process.
What you're describing here is not a 'feature' or 'bug' in the card, but rather of the old videodev kernel interface in combination with video4linux1. It just stores per-card information, so if you have one card with two applications running at the same time (which was officially not possible), then the driver can't tell which of the two applications is doing what. The way in which the (old) zoran driver handled 2 opens-at-the-same-time in the past was an ugly hack (but hey, it worked, somewhat). >From kernels 2.4.19 and further, the kernel has been shipping with a new file_ops-based videodev kernel interface, which gives the option to store per-session information (i.e., xawtv and lavrec can have their own session-data in the driver), and you probably see that this will make it possible to close xawtv while lavrec is recording (because the session data says that xawtv just uses overlay, so the driver just shut down overlay and nothing else - lavrec will continue recording until it is shut down). If you have a 2.4.19 kernel and a DC10+/Buz/LML, just try out the new drivers (CVS branch ZORAN_VIDEODEV_2) and play with it in whatever way - it should just work (tm). Anyway, it is definately *not* a feature or bug of the card, but just of one of the kernel protocols, and that has been fixed some time ago. When someone (Leon?) finds time to adapt the marvel driver to this new file_ops-based videodev interface, you'll see the same thing under the marvel cards, and recording and watching TV should (from then on) also be possible simultaneously. Concerning the tuner - the only thing that apps do is send a request to the driver - they don't lock the tuner or anything to their specific session - to change frequency, and it then either does that, or it doesn't (and returns an error). If two apps do this at the same time, the frequency will just change quickly to the frequency requested by app1 and then flash over to the frequency requested by app2. Ronald -- Ronald Bultje <[EMAIL PROTECTED]> Linux Video/Multimedia developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
