[mythtv-users] UK-Mendip DVB-T multiplex, post 11 January 2011

[nospam312]

> I'm having weird tuning/failed recording problems with a Nova-T-500
> card that used to work perfectly before a coincidental rebuild/system
> upgrade from Fedora 8/MythTV 0.21-fixes to Fedora 14/MythTV 0.24-fixes.
> I'm wondering if the proliferation of 'auto' in some of those columns
> may be a factor.
>
> A failed recording (with mythfrontend's 'upcoming recordings' showing
> it stuck in the 'tuning' state) goes like this:

I am on a different transmitter and I have recordings getting stuck in
the "t" (lower case t) state also.

I am using single tuner Haupaugge USB sticks.

I was thinking it was related to a recent update on my 0.24fixes - I
was running an early 0.24fixes when it was first released (old CVS
style build number).  After updating I have a newer Git related build
number in my status page.  I was waiting to ensure Mythbuntu update
building from Git was working.  At the same time it did kernel updates
etc so I guess something may have changed that Myth uses.

I think I have had a few days where I have had no problems since I
completely deleted everything from all the channels* / dtv* tables and
did a full scan on all my cards.  I too have several Auto's in fields
I do not recall previously but in this regard I would have to dig out
my previous backups to be 100% sure on this.

The first issue is the recording getting stuck in the "t" state (I
think I saw this on the Upcoming Recordings screen).  The second issue
is if you go and look at the Previous Recordings screen after the "t"
state problem it is classed as recorded meaning Myth does not
reschedule or give any indication there was a problem so it is next to
impossible to know if you have missed a recording as Myth thinks
everything was fine.

Not knowing something has not worked is the main problem for me Myth
should not class the programme as recorded if it hasn't even managed
to tune to the channel - it should marked the recording as failed and
try to reschedule it.

As we both have a very similar problem I think adding a trac ticket is
probably the way to go?