Re: [vdr] Messages from Lirc have to be longer than 21 chars, why?
On 06.03.2011 16:56, Steffen Barszus wrote:
> On Sun, 06 Mar 2011 17:33:39 +0200
> Ville Skyttä wrote:
>
>> On 03/06/2011 04:49 PM, Klaus Schmidinger wrote:
>>
>>> I guess what we need first is a specification of the strings
>>> LIRC provides. Then we can adapt the VDR code accordingly.
>>> I quickly searched the web, but couldn't find that information.
>>>
>>> Anybody?
>>
>> Maybe it has been discussed before, but I wonder why VDR has a LIRC
>> implementation of its own instead of using liblirc_client?
>>
>> http://www.lirc.org/html/technical.html#library
>
> You need a lircrc file for that to use, i think that is just adding
> another layer. Instead of learning the keys, you would need
> to create what is in remote.conf in the .lircrc and have fixed keywords
> in VDR. At least this is my understanding, correct me if i'm wrong.
>
> The format is described there as well.
>
> XBMC seems for instance just to read a line
>
> while (fgets(m_buf, sizeof(m_buf), m_file) != NULL)
> ...
> char scanCode[128];
> char buttonName[128];
> char repeatStr[4];
> char deviceName[128];
> sscanf(m_buf, "%s %s %s %s", &scanCode[0], &repeatStr[0],
> &buttonName[0], &deviceName[0]);
>
> https://github.com/xbmc/xbmc/blob/master/xbmc/input/linux/LIRC.cpp
>
> which seems to work well ...
I've changed the code in VDR's lirc.c this way now:
--- lirc.c 2006/05/28 08:48:13 2.0
+++ lirc.c 2011/03/08 15:35:13
@@ -86,7 +86,8 @@
}
}
-if (ready && ret > 21) {
+if (ready && ret > 0) {
+ buf[ret - 1] = 0;
int count;
char KeyName[LIRC_KEY_BUF];
if (sscanf(buf, "%*x %x %29s", &count, KeyName) != 2) { // '29' in
'%29s' is LIRC_KEY_BUF-1!
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How's the 24 bit OSD VDR coming?
Hi Klaus - et al How's the development on vdr-1.7.17 (?) coming? I wait with baited breath!! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How's the 24 bit OSD VDR coming?
On 08.03.2011 20:08, Simon Baxter wrote: > Hi Klaus - et al > > How's the development on vdr-1.7.17 (?) coming? Almost done. Don't get too excited about the TrueColor OSD, though. What comes with VDR is only the basic OSD platform that allows plugins to use full screen 32 bit ARGB color, with alpha blendable pixmaps and such. It will be up to the skin designers to make good use of these new features ;-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How's the 24 bit OSD VDR coming?
Am 08.03.2011 22:09, schrieb Klaus Schmidinger: > Don't get too excited about the TrueColor OSD, though. > What comes with VDR is only the basic OSD platform that > allows plugins to use full screen 32 bit ARGB color, > with alpha blendable pixmaps and such. Do you have any numbers on OSD speed for, lets say, some prototype output device you may have at hand? An old-style 720x576x8 display has just 400k size, HD RGB32 however has 6Mb. This could limit display update speed notably for animations or video overlays using OSD. Would be nice to know how much is possible. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How's the 24 bit OSD VDR coming?
On Tue, Mar 8, 2011 at 1:31 PM, Udo Richter wrote: >> Don't get too excited about the TrueColor OSD, though. >> What comes with VDR is only the basic OSD platform that >> allows plugins to use full screen 32 bit ARGB color, >> with alpha blendable pixmaps and such. > > Do you have any numbers on OSD speed for, lets say, some prototype > output device you may have at hand? > > An old-style 720x576x8 display has just 400k size, HD RGB32 however has > 6Mb. This could limit display update speed notably for animations or > video overlays using OSD. Would be nice to know how much is possible. With things like VDPAU, I would imagine some very cool things are possible and considering how many people are using VDPAU with VDR now, hopefully we'll get a good pool of skinners coming up with some great options to choose from. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How's the 24 bit OSD VDR coming?
On 08.03.2011 22:31, Udo Richter wrote: > Am 08.03.2011 22:09, schrieb Klaus Schmidinger: >> Don't get too excited about the TrueColor OSD, though. >> What comes with VDR is only the basic OSD platform that >> allows plugins to use full screen 32 bit ARGB color, >> with alpha blendable pixmaps and such. > > Do you have any numbers on OSD speed for, lets say, some prototype > output device you may have at hand? > > An old-style 720x576x8 display has just 400k size, HD RGB32 however has > 6Mb. This could limit display update speed notably for animations or > video overlays using OSD. Would be nice to know how much is possible. Sending the full screen OSD with 32 bit ARGB to the TT-S2 6400 takes roughly 500ms. Most of the time, though, only small portions of the screen are modified and need to be transferred to the hardware (or whatever device actually displays the OSD). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
