On Sat, Apr 18, 2009 at 10:37 AM, Udo Richter wrote:
>>> This is mostly what the VDR skin interface already provides: A
>>> semantically structured description of the interface. Most skins
>>> translate this into a bitmapped OSD view, but they don't have to. The
>>> skincurses plugin for example u
Petri Helin wrote:
>> [6753] [input_vdr] TCP: Buffer too small (8192 ; incoming frame 1734679773
>> bytes)
>> Not multiplexed? 0xf6
>> Not multiplexed? 0xbd
>> Speicherzugriffsfehler
> There were some buffer related changes done in the cvs on 5th of March,
> so you could try with a version a bit
On 18.04.2009 15:36, Luca Olivetti wrote:
> On Sat, 18 Apr 2009 13:28:24 +0200
> Udo Richter wrote:
>
>> This is mostly what the VDR skin interface already provides: A
>> semantically structured description of the interface. Most skins
>> translate this into a bitmapped OSD view, but they don't ha
Hi!
I've set up a GIT mirror of the xineliboutput CVS repository:
git://projects.vdr-developer.org/xineliboutput.git
http://projects.vdr-developer.org/git/?p=xineliboutput.git;a=summary
It was originally intended to be used for developing the FRC patches
(http://projects.vdr-developer.or
On 17.04.2009 11:34, Fce.Valeins wrote:
> Hi,
>
> With the new version of VDR (1.7.4 or 1.7.5), iptv 0.2.6 and xine 0.9.0
> I can view H264 stream for my French DSL box (Livebox).
> But when I try to record stream H264 I have file when 0 size and these
> errors :
>
> Apr 16 18:44:33 solo vdr: [
Morfsta wrote:
> On Mon, Apr 13, 2009 at 11:47 PM, Thomas Günther wrote:
> >
> > Here is a patch for the vompserver plug-in and VDR >= 1.7.3:
> >
> > http://toms-cafe.de/vdr/download/vompserver-0.3.0-1.7.3.diff
>
> Thanks for making the patch, before I go back down the route of
> fiddling with VD
On Sat, 18 Apr 2009 13:28:24 +0200
Udo Richter wrote:
>
> This is mostly what the VDR skin interface already provides: A
> semantically structured description of the interface. Most skins
> translate this into a bitmapped OSD view, but they don't have to. The
> skincurses plugin for example u
On 17.04.2009 23:49, Timothy D. Lenz wrote:
> In the startup scripts I've been using for some time, it does a check for
> /tmp/VDRBOOT_COMPLETE
> to confirm vdr started correctly. It doesn't seem to have a problem if the
> file is not found, but somewhere along the line vdr
> stoped creating this
On 14.04.2009 01:42, Torgeir Veimo wrote:
> This would of course require information from vdr in a slightly
> different form; ie. semantically instead of pixels. I'd suggest trying
> to get the OSD information as HTML from VDR, then allowing the frontend
> to render it in any way it deems suitable,
