Re: [vdrpylib-devel] pending patches?

[Dominic M. <do...@su...>]

On Thu, 6 Jan 2005, Rob Shortt wrote:

> Hi, welcome to the list.  Sorry for the late reply.

No worries, I'm still on hols, so I've got time on my hands to hack, if 
only I could decide on one thing to do at a time!

> There is a patch from Vlad here which contains some changes which I may 
> include.  I haven't gone through it all yet because on my vacation 
> (which just ended) I decided to goof off instead of hack.  What issues 
> are you having?

I can't read the EPG in - I'm using DVB-T and the channel ids don't match 
up with what the code expects! Timers are also unreadable, probably due to 
the same issue, rather than digging in and re-solving it I thought I'd ask 
to see if someone else already has.

> It sounds like you should build a server process which is the single 
> point of communication to VDR.  In my other project, Freevo 
> (http://freevo.sf.net), we are working on an EPG library (pyepg) which 
> can use vdrpylib to fill its database.  You may be interested in that 
> sort of thing.  I have also been working on a client-server 
> implimentation of pyepg but that part is specific to Freevo so far.

I always like the idea of leveraging 3rd party code, it seems the
client-server implementation might be the most appropriate idea for my
project (vdr-mediamvp) whereby the database resides in one process and the
rest of the server in another. I suppose the obvious question regarding
that is why couldn't the database be just another vdr module to avoid
holding two sets of the same data (apart from having to write the code
myself of course!)

cheers,

d.