>>> >> >> No problem. I don't keep well tested the the important member of the >> family won't let me keep my toy :). >> The patch fixed the new tvtime and mplayer issue. Now the old quirk is >> back and a new MPlayer issue has cropped up. The tvtime issues is with >> the freevo channels not matching the tvtime channels and an odd >> interactions that are occuring. The new mlpayer issue is with v4l: >> ================================================================= >> WARNING: YOU ARE USING V4L DEMUXER WITH V4L2 DRIVERS!!! >> As the V4L1 compatibility layer is broken, this may not work. >> If you encounter any problems, use driver=v4l2 instead. >> Bugreports on driver=v4l with v4l2 drivers will be ignored. >> ================================================================= >> tv.c: norm_from_string(NTSC): Bogus norm parameter, setting default. >> Unknown norm! >> Error: Cannot set norm! >> FPS not specified in the header or invalid, use the -fps option. >> No stream found. >> >> I change to v4l2 it goes away. It may be tiem to change # TV_DRIVER = >> 'v4l' default to v4l2. A doc note for the mplayer pause it does not >> seem to work with non-ivtv cards beyond pausing the video frame. It >> then resumes to the current point in play. > > Sounds reasonable most of the drivers will now support v4l2 io controls. > > What are the other messages caused by simply the driver being v4l? > > Duncan None other than the above and Mplayer not working.
Evan ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
