Red Hat Bugzilla – Bug 76062
Xvideo v4l bridge does not scale out properly
Last modified: 2007-04-18 12:47:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
Description of problem:
Xvideo v4l bridge does not scale out properly: when using for instance xawtv
with -xv flag, rescaling window should alsways give a rescaled image, be the
image smaller than video output (726x625 or sthg like that. this works), or
bigger than the video output (this doesn't work: when trying to maximize window
in 1024x768 for instance, only the center of the screen has the video, and there
is a black border outside).
It doesn't work as well on RedHat 8.0.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.needs a video card (any bt878 will be ok), and properly configured XFree86,
with v4l loaded, and any resolution > to 800x600
2.start xawtv -xv -scale (or xawtv alone, since it's the defaults)
3.maximize window / do fullscreen
Actual Results: video appears only in the center, big black frame around.
Expected Results: fullscreen or maximized image.
This has been reported as working with other distributions and other X servers.
Enabling VidMod extension use in video programs solves the problem, when that
extension can be used by the program.
Problem has been seen using Mach64, Rage 128 and Radeon chips.
More information can be seen on these threads of kwintv/qtvision development
mailing list where the problem has been discussed:
I do not have this hardware in order to test...
Does this problem occur for you, or anyone else in Red Hat Linux 8.0 as well?
As seen on the mailing list, this problem occurs for me on RH 7.3 and for
Michael Kedl who is using RH 8.0. He was the guy who tested it with commercial X
Since I do not have access to the hardware this problem is occuring on,
I strongly suggest reporting this problem on the email@example.com
mailing list and also the firstname.lastname@example.org mailing list to
accelerate the issue by letting many more developers be aware of the
I do not see any evidence presented in any of those emails that this
is a Red Hat Linux specific problem.
Without the hardware, or a known patch that adds support or fixes
a bug, there is not really a lot that I can do until upstream developers
whom are made aware of the problem can comment on it and/or fix it.
Please keep this report updated with any information you come across.
Sounds like it is related to bug #74684 and not reproducible here.
Please upgrade to Fedora Core 2 or later, and if this issue turns
out to still be reproduceable, please file a bug report in the
X.Org bugzilla located at http://bugs.freedesktop.org in the
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes
that become available for consideration in future updates.