[mythtv-users] 1080i content and xv
Chris Ribe
chrisribe at gmail.com
Fri Jan 13 00:56:23 UTC 2006
I've found a solution that will work for the time being.
Using mplayer with the command "mplayer -fs -vf scale=1600:900 filename.ts"
gets me exactly the results I am looking for. Alternatively, substituing
"crop=1600:1080" for "scale"1600:900" will get me unscaled, but cropped on
the sides, playback.
I've yet to figure out how to get this working inside of myth, but at least
I know I'll be able to watch the Pat's game in HD on Saturday.
Thanks again to all who have helped me.
On 1/12/06, Chris Ribe <chrisribe at gmail.com> wrote:
>
> Well, I probably will end up throwing money at the problem, but I won't
> like doing it. The video card is old, yes, but not that old. I bought it
> new in 2003!
>
> On 1/11/06, Steve Adeff <adeffs at gmail.com> wrote:
> >
> > On Wednesday 11 January 2006 22:46, Chris Ribe wrote:
> > > Minor success!
> > >
> > > If I make the window wider than my desktop, the video plays back
> > normally.
> > > Of course, it has also crashed x once and hard frozen the computer
> > another
> > > time. Perhaps the -panscan option will help me out.
> > >
> > > On 1/11/06, Chris Ribe <chrisribe at gmail.com> wrote:
> > > > The output from the cable box is an MPEG-TS stream over firewire.
> > > > Playback works fine for 720p channels. The clip I am testing with
> > was
> > > > captured off of PBS.
> > > >
> > > > I've tried playing the clip back at half size with VLC, and the
> > results
> > > > were the same. I'm having trouble figuring out how to do any
> > scaling
> > > > with mplayer.
> > > >
> > > > The GPU is an old nVidia GeForce2 card w/ 32MB of ram. I don't know
> > much
> > > > more than that.
> > > >
> > > >
> > > > Here is the current state of my xorg.conf (I switched to the xv
> > driver
> > > > earlier this evening, disregard the monitor section as that is not
> > > > actually my monitor):
> > > >
> > > > # Xorg configuration created by system-config-display
> > > >
> > > > Section "ServerLayout"
> > > > Identifier "single head configuration"
> > > > Screen 0 "Screen0" 0 0
> > > > InputDevice "Mouse0" "CorePointer"
> > > > InputDevice "Keyboard0" "CoreKeyboard"
> > > > EndSection
> > > >
> > > > Section "Files"
> > > >
> > > > # RgbPath is the location of the RGB database. Note, this is the
> > name of
> > > > the
> > > > # file minus the extension (like ".txt" or ".db"). There is
> > normally
> > > > # no need to change the default.
> > > > # Multiple FontPath entries are allowed (they are concatenated
> > together)
> > > > # By default, Red Hat 6.0 and later now use a font server
> > independent of
> > > > # the X server to render fonts.
> > > > RgbPath "/usr/X11R6/lib/X11/rgb"
> > > > ModulePath "/usr/X11R6/lib/modules/extensions/nvidia"
> > > > ModulePath "/usr/X11R6/lib/modules/extensions"
> > > > ModulePath "/usr/X11R6/lib/modules"
> > > > FontPath "unix/:7100"
> > > > EndSection
> > > >
> > > > Section "Module"
> > > > Load "dbe"
> > > > Load "extmod"
> > > > Load "fbdevhw"
> > > > ## Load "glx"
> > > > Load "record"
> > > > Load "freetype"
> > > > Load "type1"
> > > > Load "dri"
> > > > EndSection
> > > >
> > > > Section "InputDevice"
> > > >
> > > > # Specify which keyboard LEDs can be user-controlled (eg, with
> > xset(1))
> > > > # Option "Xleds" "1 2 3"
> > > > # To disable the XKEYBOARD extension, uncomment XkbDisable.
> > > > # Option "XkbDisable"
> > > > # To customise the XKB settings to suit your keyboard, modify the
> > > > # lines below (which are the defaults). For example, for a non-U.S.
> > > > # keyboard, you will probably want to use:
> > > > # Option "XkbModel" "pc102"
> > > > # If you have a US Microsoft Natural keyboard, you can use:
> > > > # Option "XkbModel" "microsoft"
> > > > #
> > > > # Then to change the language, change the Layout setting.
> > > > # For example, a german layout can be obtained with:
> > > > # Option "XkbLayout" "de"
> > > > # or:
> > > > # Option "XkbLayout" "de"
> > > > # Option "XkbVariant" "nodeadkeys"
> > > > #
> > > > # If you'd like to switch the positions of your capslock and
> > > > # control keys, use:
> > > > # Option "XkbOptions" "ctrl:swapcaps"
> > > > # Or if you just want both to be control, use:
> > > > # Option "XkbOptions" "ctrl:nocaps"
> > > > #
> > > > Identifier "Keyboard0"
> > > > Driver "kbd"
> > > > Option "XkbModel" "pc105"
> > > > Option "XkbLayout" "us"
> > > > EndSection
> > > >
> > > > Section "InputDevice"
> > > > Identifier "Mouse0"
> > > > Driver "mouse"
> > > > Option "Protocol" "IMPS/2"
> > > > Option "Device" "/dev/input/mice"
> > > > Option "ZAxisMapping" "4 5"
> > > > Option "Emulate3Buttons" "yes"
> > > > EndSection
> > > >
> > > > Section "Monitor"
> > > > Identifier "Monitor0"
> > > > VendorName "Monitor Vendor"
> > > > ModelName "Dell 1905FP (Analog)"
> > > > DisplaySize 370 270
> > > > HorizSync 30.0 - 81.0
> > > > VertRefresh 56.0 - 76.0
> > > > Option "dpms"
> > > > EndSection
> > > >
> > > > Section "Device"
> > > > Identifier "Videocard0"
> > > > Driver "nv"
> > > > VendorName "Videocard vendor"
> > > > BoardName "NVIDIA GeForce 2 MX (generic)"
> > > > EndSection
> > > >
> > > > Section "Screen"
> > > > Identifier "Screen0"
> > > > Device "Videocard0"
> > > > Monitor "Monitor0"
> > > > DefaultDepth 24
> > > > SubSection "Display"
> > > > Viewport 0 0
> > > > Depth 16
> > > > Modes "800x600" "640x480"
> > > > EndSubSection
> > > > SubSection "Display"
> > > > Viewport 0 0
> > > > Depth 24
> > > > Modes "1600x1200" "1400x1050" "1280x960"
> > "1280x800"
> > > > "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
> > > > EndSubSection
> > > > EndSection
> > > >
> > > > Section "DRI"
> > > > Group 0
> > > > Mode 0666
> > > > EndSection
> > > >
> > > > On 1/11/06, Steve Adeff <adeffs at gmail.com> wrote:
> > > > > On Wednesday 11 January 2006 21:11, Chris Ribe wrote:
> > > > > > Neither of them worked, unfortunately.
> > > > > >
> > > > > > Using the nv driver resulted in a slightly different version of
> > the
> > > > >
> > > > > same
> > > > >
> > > > > > problem.
> > > > > >
> > > > > > Perhaps it is a peculiarity in the transport stream from the
> > cable
> > > > >
> > > > > box,
> > > > >
> > > > > > perhaps a newer video card would help. I guess I'll just keep
> > > > >
> > > > > plugging
> > > > >
> > > > > > away and see if I can figure something out. Thanks for your
> > help.
> > > > > >
> > > > > > On 1/11/06, Brian Wood < beww at beww.org> wrote:
> > > > > > > On Jan 11, 2006, at 6:35 PM, Chris Ribe wrote:
> > > > > > > > Sorry, I need a little hand holding here.
> > > > > > > >
> > > > > > > > I assume I can unload the nVidia driver by issuing
> > > > > > > >
> > > > > > > > #modprobe -r /lib/modules/2.6.14-
> > 1.1656_FC4smp/updates/drivers/
> > > > > > > > video/nvidia/nvidia-1_0-7676.ko
> > > > > > >
> > > > > > > Or just "rmmod nvidia", "lsmod" will tell you if it's still
> > there
> > > > > > > or
> > > > > > >
> > > > > > > not.
> > > > > > >
> > > > > > > > but loading the nv driver, I'm not so sure about.
> > > > > > > >
> > > > > > > > Can I just replace the
> > > > > > > >
> > > > > > > > Driver "nvidia" line in xorg.conf with, Driver "xv" and
> > restart
> > > > > > > > x?
> > > > > > >
> > > > > > > Yes, normally, but I have heard tell of nVidia setups where it
> >
> > > > > > > still loads nVidia even if you do that. The actual X server is
> > an
> > > > > > > executable usually linked to "X" (note the cap) someplace like
> > > > > > > /usr/ X11R6/bin (seems like everybody puts it in a different
> > place.
> > > > > > >
> > > > > > > That should be "nv" not "xv", I'm assuming that was a typo.
> > "xv" is
> > > > > > > something completely different.
> > > > > > >
> > > > > > > My guess is that if commenting out "load glx" does not work
> > then
> > > > > > > loading "nv" instead of nvidia will not work either, but you
> > never
> > > > >
> > > > > know.
> > > > >
> > > > > which GPU card?
> > > > > whats your xorg.conf have for loading the nvidia driver?
> > > > > does the issue occur when you playback 1080i content at 1/2 size?
> > > > >
> > > > > --
> > > > > Steve
> >
> > I've seen this before, I think it was on an oooooold nvidia card as
> > well. xv
> > couldn't handle resizing the video smaller for whatever reason (I was
> > way too
> > newbie in linux to have figured it out) and would tear the video. I
> > would try
> > a new card with more memory perhaps?
> >
> > --
> > Steve
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060112/efd5312c/attachment-0001.htm
More information about the mythtv-users
mailing list