[mythtv] Mythtv/DVB enhancements

Paul Woodward paul_woodward at fastnet.co.uk
Wed Feb 11 05:35:21 EST 2004


> The first one is the simplest I've seen this bug since 0.13 and it
> occurs on the simple recording menu off the epg. Basicly if the
> description text is too long it forces all of the useful buttons off the
> bottom of the visible screen (Things like Record once etc.).  My inital
> attempt to fix this was to truncate the description text to a safe
> ammount.  It occurs to me this is a bit of a botch fix?, if so any
> suggestions on a better fix and which area of the code I should ramp up
> first on? As an ammendment to this one I also notice that html &
> characters are sneeking into the descriptions which I assume are
> unconverted chars anyone know where this is supposed to be done?

This had irritated me too. I end up using mythweb for most of my scheduling because of it.

> 
> Secondly since I have a marginal DVB-T connection I notice I get
> "no-dataed" quite a lot from the DVB driver. Saddly this causes the
> mythback to lockup (loop of death) and for the frontend to die in a xvmv
> assert. So I kind of figured it might be nice to harden that code to
> cope with missing data.  So how about a "lost transmission" error
> displayed on the mythfrontend instead?.  This appears to be quite a in
> depth fix so I'd appreciate any hints.. <Chuckle>
Yes, I strongly agree with this, in the event of a poor signal mythfrontend will often lock up. In order to recover the situation, I have to kill the back and frontend, edit the default channel to which the card will tune in the database (otherwise it will lock again if I try to watch TV) and the start it all back up again. That doesn't gain any WAF points.

I would much prefer if it simply stopped trying to display the corrupted stream and allowed you to change channels.

> 
> Thirdly an enhancement to DVB, I understand that the DVB drivers allow
> for multiple streams to be read from the same frequency (ahh the joys of
> multiplexing). I guess it would be good enhancement for mythtv to be
> able to cope with this one. Bit of a mythtv expert change but I'd be
> interesting in hearing how it could be implemented?

Someone mentioned in an email yesterday that Kenneth might already have a preliminary patch for this.



More information about the mythtv-dev mailing list