[vdr] Wrong OSD values in setup.conf (was: Re: vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5)

Andreas Mair andreas at vdr-developer.org
Thu Jun 11 07:25:37 CEST 2009


Hi,

as you can see your values are "0" too. I suggest you set (VDR
stopped!) OSDHeightP and OSDWidthP to "0.5" (=50%) and FontFixSizeP,
FontOsdSizeP, FontSmlSizeP to "0.03" to get an OSD. After that you can
fine-tune the OSD settings.

Regards,
Andreas

2009/6/10 Goga777 <goga777 at bk.ru>:
>> check your setup.conf. Mine has invalid sizes:
>> FontFix = Courier:Bold
>> FontFixSize = 0
>> FontFixSizeP = 0,000000
>> FontOsd = VDRSymbols Sans:Bold
>> FontOsdSize = 0
>> FontOsdSizeP = 0,000000
>> FontSml = VDRSymbols Sans:Book
>> FontSmlSize = 0
>> FontSmlSizeP = 0,000000
>> OSDHeight = 0
>> OSDHeightP = 0,000000
>> OSDLanguage = de_DE
>> OSDLeft = 0
>> OSDLeftP = 0,000000
>> OSDTop = 0
>> OSDTopP = 0,000000
>> OSDWidth = 0
>> OSDWidthP = 0,000000
>
> my setup.conf
>
> FontFix = Courier:Bold
> FontFixSize = 0
> FontFixSizeP = 0.000000
> FontOsd = Sans Serif:Bold
> FontOsdSize = 0
> FontOsdSizeP = 0.000000
> FontSml = Sans Serif
> FontSmlSize = 0
> FontSmlSizeP = 0.000000
> InitialChannel = 0
> OSDHeight = 0
> OSDHeightP = 0.000000
> OSDLanguage = en_US
> OSDLeft = 0
> OSDLeftP = 0.000000
> OSDMessageTime = 2
> OSDSkin = sttng
> OSDTheme = default
> OSDTop = 0
> OSDTopP = 0.000000
> OSDWidth = 0
> OSDWidthP = 0.000000
>
>> As you can see they are are all "0". I don't know how that could
>> happen, but I already had that on two VDR instances. Both upgraded
>> from VDR 1.6.0.
>> After setting them once in VDR 1.7 they are fine.
>>
>> What skin do you use?
>> My own EnigmaNG skin (CVS release) takes care of invalid values ;)
>
> I didn't install additional skins, I'm using default skin  ST:TNG
>
> Goga
>
>
>> 2009/6/9 Reinhard Nissl <rnissl at gmx.de>:
>> > Hi,
>> >
>> > Goga777 schrieb:
>> >
>> >> how can I fix my problem with ERROR: cOsd::SetAreas returned 5
>> >
>> > This number matches the enum value oeWrongAlignment. In VDR's
>> > code excerpt you can see the condition for this error:
>> >
>> >  if (Areas[i].x1 > Areas[i].x2 || Areas[i].y1 > Areas[i].y2 ||
>> > Areas[i].x1 < 0 || Areas[i].y1 < 0)
>> >     return oeWrongAlignment;
>> >
>> >> Jun  9 21:25:39 arvdr vdr: [12294] vdr-xine: new OSD(0, -108) requested with coordinates out of range
>> >> Jun  9 21:25:39 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5
>> >
>> > I've no idea why a vanilla VDR-1.7.7 should produce such an
>> > incorrect OSD setup.
>> >
>> > Bye.
>> > --
>> > Dipl.-Inform. (FH) Reinhard Nissl
>> > mailto:rnissl at gmx.de
>> >
>> > _______________________________________________
>> > vdr mailing list
>> > vdr at linuxtv.org
>> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>> >
>>
>>
>>
>
>
> --
> Удачи,
> Игорь
>
> _______________________________________________
> vdr mailing list
> vdr at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>



-- 
http://andreas.vdr-developer.org --- VDRAdmin-AM & EnigmaNG & VDRSymbols
VDR user #303



More information about the vdr mailing list