Petri Helin <[EMAIL PROTECTED]> writes:
> gimli wrote:
>> Screen resolution is 1920x1080 for HDTV.
>> When is switch from an SDTV channel to an HDTV channel
>> the OSD is way to small. Looks there is no scalling to
>> the larger resolution.
>>
>
> You might want to give the cvs a go now. There sh
gimli wrote:
> Screen resolution is 1920x1080 for HDTV.
> When is switch from an SDTV channel to an HDTV channel
> the OSD is way to small. Looks there is no scalling to
> the larger resolution.
>
You might want to give the cvs a go now. There should be a proper fix in
place and no more revertin
gimli wrote:
> Screen resolution is 1920x1080 for HDTV.
> When is switch from an SDTV channel to an HDTV channel
> the OSD is way to small. Looks there is no scalling to
> the larger resolution.
>
Yes, that's an unfortunate side effect. You could try reverting several
other files also, namely se
Screen resolution is 1920x1080 for HDTV.
When is switch from an SDTV channel to an HDTV channel
the OSD is way to small. Looks there is no scalling to
the larger resolution.
cu
Edgar (gimli) Hucek
Petri Helin schrieb:
> gimli wrote:
>> Reverting xine_input_vdr.c breaks the OSD scaling.
>>
>> cu
gimli wrote:
> Reverting xine_input_vdr.c breaks the OSD scaling.
>
> cu
>
> Edgar (gimli) Hucek
>
Could you elaborate a bit? What settings do you have, what is the
resolution of the video when it happens, what are the exact symptoms you
are experiencing and so on... I myself have not yet exp
Reverting xine_input_vdr.c breaks the OSD scaling.
cu
Edgar (gimli) Hucek
Petri Helin schrieb:
> [EMAIL PROTECTED] wrote:
>> Petri Helin <[EMAIL PROTECTED]> writes:
>>
>>> For a temporary solution you could revert file xine_input_vdr.c to
>>> version 1.127:
>>>
>>> cvs update -C -r 1.127 xine_i
[EMAIL PROTECTED] writes:
> Don't know, I haven't tried :)
> Going to try right now
Seems ok now.
Thanks again.
--
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Petri Helin <[EMAIL PROTECTED]> writes:
> It will affect in a sense since xine_input_vdr.c is used when building
> xineplug_inp_xvdr.so (the xine VDR input plugin) which in turn is used
> whether you use vdr-sxfe or xine-ui. So, the important thing is to
> replace the xine plugin after recompil
[EMAIL PROTECTED] wrote:
> Pertti Kosunen <[EMAIL PROTECTED]> writes:
>
>> [EMAIL PROTECTED] wrote:
>>> but vdr-sxfe wasn't recompiled. it seems there's no dependency to
>>> xine_input_vdr.c
>> You may have to run "make clean-plugins".
>
> what I meant is that it does not seem vdr-sxfe depends on
Pertti Kosunen <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> but vdr-sxfe wasn't recompiled. it seems there's no dependency to
>> xine_input_vdr.c
>
> You may have to run "make clean-plugins".
what I meant is that it does not seem vdr-sxfe depends on
xine_input_vdr.c
And the modificat
"Simon Baxter" <[EMAIL PROTECTED]> writes:
> If you could share your modified plugin - that'd be great
freevo-vdr.tar.bz2
Description: Binary data
If I recall correctly it was based on freevo-vdr-0.5.
I copy the 2 files in
/usr/local/stow/freevo-1.x/lib/python2.5/site-packages/freevo/plugins/
[EMAIL PROTECTED] wrote:
> but vdr-sxfe wasn't recompiled. it seems there's no dependency to
> xine_input_vdr.c
You may have to run "make clean-plugins".
(
cd /usr/src/vdr-1.6.0-1/
make clean-plugins
make plugins
cd /usr/src/vdr-1.6.0-1/PLUGINS/src/xineliboutput-1.0.0
make install
cp /usr/src/v
Petri Helin <[EMAIL PROTECTED]> writes:
>>> cvs update -C -r 1.127 xine_input_vdr.c
>>>
>>> It has been reported to cure the kind of behaviour you have been
>>> experiencing.
>>
>> btw, vdr-sxfe is also affected.
>>
>
> Reverting xine_input_vdr.c, recompiling (make plugins) and reinstalling
>
[EMAIL PROTECTED] wrote:
> Petri Helin <[EMAIL PROTECTED]> writes:
>
>> For a temporary solution you could revert file xine_input_vdr.c to
>> version 1.127:
>>
>> cvs update -C -r 1.127 xine_input_vdr.c
>>
>> It has been reported to cure the kind of behaviour you have been
>> experiencing.
>
>
Petri Helin <[EMAIL PROTECTED]> writes:
> For a temporary solution you could revert file xine_input_vdr.c to
> version 1.127:
>
> cvs update -C -r 1.127 xine_input_vdr.c
>
> It has been reported to cure the kind of behaviour you have been
> experiencing.
btw, vdr-sxfe is also affected.
--
__
> I'm using freevo-1.x from svn.
> I'm using debian and ubuntu. I'm installing kaa and freevo in
> /usr/local/stow and using stow to make it available through the
> standard paths.
> (cd /usr/src/kaa; python setup.py install --prefix
> /usr/local/stow/kaa; cd /usr/local/stow; stow kaa; ldconfig; cd
"Simon Baxter" <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] wrote:
>>> Hi,
>>>
>>> I'm using vdr-1.6 and xineliboutput from cvs.
>>> I'm using it with freevo and vdr is controlled through
>>> xine-ui/vdr-sxfe by stdin.
>>> For instance I send "hitk Up" to vdr-sxfe or "EventUp" to xine-ui.
>
>
Petri Helin <[EMAIL PROTECTED]> writes:
> For a temporary solution you could revert file xine_input_vdr.c to
> version 1.127:
>
> cvs update -C -r 1.127 xine_input_vdr.c
>
> It has been reported to cure the kind of behaviour you have been
> experiencing.
I'll do that.
Cheers.
--
> [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> I'm using vdr-1.6 and xineliboutput from cvs.
>> I'm using it with freevo and vdr is controlled through
>> xine-ui/vdr-sxfe by stdin.
>> For instance I send "hitk Up" to vdr-sxfe or "EventUp" to xine-ui.
Can you tell me more on how this works? Are you runni
[EMAIL PROTECTED] wrote:
> Hi,
>
> I'm using vdr-1.6 and xineliboutput from cvs.
> I'm using it with freevo and vdr is controlled through
> xine-ui/vdr-sxfe by stdin.
> For instance I send "hitk Up" to vdr-sxfe or "EventUp" to xine-ui.
> Every so often when i change between channels xine-ui/vdr-sx
20 matches
Mail list logo
