On 3/15/07, Tom Weichmann <[EMAIL PROTECTED]> wrote:
> On Wednesday 14 March 2007 02:02, Duncan Webb wrote:
> > On Wed, 14 March, 2007 3:53 am, Tom Weichmann wrote:
> > > On Tuesday 13 March 2007 13:22, Duncan Webb wrote:
> > >> On Tue, 13 March, 2007 3:09 am, Tom Weichmann wrote:
> > >>> On Monday 12 March 2007 02:01, Duncan Webb wrote:
> > >>>> On Mon, 12 March, 2007 5:46 am, Tom Weichmann wrote:
> > >>>>> After an upgrade from SuSE 10.0 to 10.2, I have got some
> > >>>>> wierdness with mplayer.
> > >>>>>
> > >>>>> If I just do a 'mplayer /dev/video0'
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> I get pretty good video., but if I use freevo, it changes the 4:3
> > >>>>>  signal to something that looks like 16:0 and skips a lot.  Once
> > >>>>> I
> > >>>>> close sown freeo and do a 'mplayer /dev/video0' again, the ourput
> > >>>>> looks like the freevo output, 16:9ish and choppy.  Anyone have
> > >>>>> any ideas what might be causing this?
> > >>>>
> > >>>> Use http://freevo.sourceforge.net/cgi-bin/doc/TroubleShooting to
> > >>>> get the mplayer command line and post this.
> > >>>>
> > >>>> Duncan
> > >>>
> > >>> Thanks Duncan, I should have thought of that before:
> > >>
> > >> np
> > >>
> > >>> /usr/bin/mplayer -vo xv,sdl,x11,  -ao sdl -autosync
> > >>> 100 -nolirc -nojoystick -autoq 100 -screenw 800 -screenh
> > >>> 600 -fs -slave -cache 8192 /dev/video0, poll=-1
> > >>>
> > >>>
> > >>>
> > >>> This should be the default, as I have not changed anything.
> > >>
> > >> This looks ok. I would expect to see a -slave option, but this is the
> > >> tv module so may be not. As you're using X what is the default mode,
> > >> 800x600
> > >> too? It's best to have the two matching.
> > >>
> > >> I would change the MPLAYER_VO_DEV (display in freevo.conf) to either xv
> > >> or sdl, (x11 is a very poor driver)
> > >>
> > >> Duncan
> > >
> > > OK, I have a new theory about this.  When reading your reply you
> > > mentioned something about this being the TV module and it made me realize
> > > that I didn't describe this well enough.  Yes, this is the TV module and
> > > this only occurs when either recording or or watching video directly from
> > > the TV card.  This does not occur when I am watching video that I did not
> > > record myself.  Also once I have tried watching TV in Freevo it seems to
> > > lock in this weird setting.  If I try mplayer /dev/video0, before using
> > > freevo, everything is OK, then I try freevo and get weird output from the
> > > TV then I quit and try
> > > mplayer /dev/video0 again and the same weirdness is there as when I tried
> > > in freevo.  The only way I can get back to normal output is to reboot or
> > > to 'rmmod ivtv' and then 'modprobe ivtv' again.
> > >
> > >
> > > So here is my new theory.  I think that I may have some messed up
> > > IVTV_OPTIONS.  I set these in my local_conf.py when I was using IVTV 0.4
> > > with SuSE 10.0 not I am using IVTV 1.x with SuSE 10.2 and a new mobo and
> > > processor.  Would these options have changed?  I used ivtvctl -a before
> > > to get these values, but this has changed with this new driver version.
> > > How do
> > > I get the settings that I need?
> > >
> > >
> > > Here are my ivtv options:
> > >
> > >
> > > TV_IVTV_OPTIONS = {
> > > 'input'         : 0,
> > > 'resolution'    : '720x480',
> > > 'aspect'        : 2,
> > > 'audio_bitmask' : 233,
> > > 'bframes'       : 3,
> > > 'bitrate_mode'  : 0,
> > > 'bitrate'       : 6000000,
> > > 'bitrate_peak'  : 9000000,
> > > 'dnr_mode'      : 0,
> > > 'dnr_spatial'   : 0,
> > > 'dnr_temporal'  : 8,
> > > 'dnr_type'      : 0,
> > > 'framerate'     : 0,
> > > 'framespergop'  : 15,
> > > 'gop_closure'   : 1,
> > > 'pulldown'      : 0,
> > > 'stream_type'   : 0,
> > > }
> >
> > What happens when you comment out the TV_IVTV_OPTIONS settings? Is
> > everything fine?
> >
> > What settings do you want to change from the defaults?
> >
> > I assume that SuSE 10.0 uses kernel 2.6.15 or lower, is this correct?
> >
> > There is a debug mode for Freevo's ivtv interface which is run by typing:
> > freevo execute /path/to/ivtv.py
> > it may show you something but it may need tweaking first.
> >
> > Duncan
> >
>
>
> Duncan,
>
> I tried commenting out the TV_IVTV_OPTIONS and still got the same results.  I
> also copied the mplayer line that Freevo uses and DO NOT have the same
> problem when I use it at the command line.  I also tried using xine to watch
> TV through freevo - same problem.
>
> I tried talking to the IVTV guys on IRC and they think that this is a Freevo
> problem.
>
> The only other thing that I can think of to look at are the following lines
> from my local_conf.py:
>
> -------------------------------------------------------------------------------
> TV_VIEW_SIZE = (640, 480)
> TV_REC_SIZE = (320, 240)   # Default for slower computers
>
> # Input formats for viewing and recording. The format affect viewing
> # and recording performance. It is specific to your hardware, so read
> # the MPlayer docs and experiment with mplayer to see which one fits
> # your computer best.
> TV_VIEW_OUTFMT = 'yuy2'   # Better quality, slower on pure FB/X11
> TV_REC_OUTFMT  = 'yuy2'
>
> -------------------------------------------------------------------------------
>
>
> Any idea if these could mess things up?
>
> Thanks for your help,
>
> Tom Weichmann
>
>
>
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Freevo-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/freevo-users
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Freevo-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>


I have been wrestling with the same problem now for a few weeks.  I
have a PVR-150 card.  I'm running Freevo 1.7 and ivtv 0.10.1 with
kernel 2.6.19.

I don't have any problems with my aspect ratio, but it looks like the
frames or fields are getting played out of order.  When things move
they look very jerky.  This doesn't happen before I start freevo.
Afterwards the video is "stuck" that way.  I tried to see which
settings freevo is changing, but the only one I could find, I found in
the code and changed it (it was the 0x3000 setting for NTSC which is
0x1000 by default) it didn't fix the issue.

I really hope there is a solution to this problem.

Thanks for all of your help!

Shawn Dowler
-- 
"Mit der Dummheit kämpfen Götter selbst vergebens."
                                                 -- Friedrich Schiller

-->  http://walkingtowel.org  <--

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to