Schedule Restore Screwed Up

Black Hole

May contain traces of nut
Came in from a weekend out to find my HDR4 displaying "wizard" :sigh:.

Yada yada... reboot.. auto-restore.

But now my schedule entries which should have been 704 BBC Radio 4 have been given weird entries on 735 BBC Gloucestershire and BBC FOUR.

What? Why? How?

I'll try a manual restore, but I don't expect it to do any good... it didn't.

Something is going wrong with the search heuristics. My guess is that it looks for matching titles in the EPG, but is finding the wrong thing.
 
Last edited:
More misery.

The BBC FOUR entries seem to be a hangover from the weird random programmes my machine has been recording, so I deleted them from the schedule.

The Archers and Inside Science should be recorded from Radio 4 but were set for Radio Gloucester, so I guessed maybe it was finding that broadcast first and figured that if I remove Radio Gloucester from my tuning set and restore again, they would revert. But they didn't. All that happened was the BBC FOUR recordings got reinstated, and the entries which were restoring to Radio Gloucester are no longer there at all.

What????
 
Might it have retuned using the wrong transmitter?

The fix-up is in the static {rsv restore} method in webif/lib/rsv.class. It relies on restoring the hSvc of the service by the service name or by the LCN. I couldn't see any fuzzy matching.
 
Transmitter seems OK (Mendip), including the local mux, but could this HD regionalisation thing have mucked up the service IDs? Come to think of it, the retune hasn't picked up any DVB-T2 mux (but I'm watching the snooker on BBC TWO HD right now, different HDR).
 
I wondered whether this is a casualty of the regionalisation (which seems to have happened on Mendip overnight), so I did another retune (and tunefix removed BBC Gloucestershire), but a schedule restore is still only giving me BBC FOUR, and anything that was being allocated to Glos is missing entirely.

So far as I can see, schedule entries which should be restored to R4 are now allocated to BBC Radio Glos, and schedules for R4 Extra are allocated to BBC FOUR.

I'll disable tunefix before I try again (prob tomorrow).
 
Regionalisation only affected the HD services on PSB3. No-one knows why anything is happening unless you post:
a) your tunefix.conf file and
b) your current /var/lib/humaxtv/channel.db file
 
I've cracked it. The wizard must have kicked in some days before I was home and noticed it, and I was trying to restore from a backup post-wizard. The schedule items were in the backup (which at first glance looked OK), but actually they were missing their intended service name. Restoring a backup from before the wizard has solved the problem.

Code:
Listing scheduled events from auto-2023-Apr-30-02:08...
Backup version 2  The Archers ( - Sun Apr 30 19:00:00 BST 2023 - 19:15)
  The Hartlepool Spy ( - Wed May 03 05:00:00 BST 2023 - 06:00)
  The Curious Cases of Rutherford... ( - Tue Feb 14 11:00:00 GMT 2023 - 11:30)
  More or Less ( - Fri Mar 03 16:30:00 GMT 2023 - 17:00)
  The Infinite Monkey Cage ( - Thu Mar 30 16:00:00 BST 2023 - 16:30)
  Casino Royale (Omnibus) ( - Sun Apr 16 02:30:00 BST 2023 - 03:40)
  BBC Inside Science ( - Thu Apr 27 16:30:00 BST 2023 - 17:00)
Favourites 1 '0'
Favourites 2 '0'
Favourites 3 '0'
Favourites 4 '0'
Favourites 5 '0'

That said, I have no DVB-T2 muxes tuned (even after a vanilla auto-retune) so I wonder whether I have a fault on that unit.
 
:mystified: :dunno:

I tried a manual tune of UHF35, and that worked fine. I then retried an auto-retune... which has pulled everything in* including Mendip Local UHF30!

* COM7/UHF55 is still missing, but I think that's defunct now isn't it?

Maybe I had a pigeon roosting on my aerial yesterday.
 
Huh? Where have you been? It's been nearly a year.
Thought so, but wasn't absolutely sure (I've slept since then).

Well, one or two more hiccups:
  1. I was happily fiddling about with BBC ONE WestHD on, when I did a reboot to reinstate the recording schedule. After the reboot, there was no signal. Signal detection showed poor reception on 30, 33, 36 and nothing on 35. What's more, all the Mynydd Machen muxes were missing from the list.

  2. Then I fired up the hidden service menu tuner test. For 586MHz (UHF35) Tuner 1 showed nothing while Tuner 2 gave 46% and quality variable 80-100%. So then I tried tying up Tuner 1 by recording another service, but still got nothing on LCN101. So I went back to the tuner test except Tuner 1 had come back to life. (Incidentally: Signal Detection is unavailable while a recording is in progress, but the hidden menu tuner test remains available and so far as I can see the recording is not interrupted* – who knew! I'm not even sure how that works...)

  3. Although I thought I had removed the tunefix package, when I inspected the installed package list it's still there, so I presume that is why my Mynydd Machen muxes disappeared. I'll try again...

  4. Another auto-retune, and again no DVB-T2 services picked up (Mynydd Machen or Mendip). I checked for a manual tune, and although at first sight there was nothing on UHF29 or UHF35, after extended monitoring a glimmer did register.

  5. Repeating these trials with HDR1 (same aerial lead) gave similar results. I am therefore forced to conclude HDR4 is not at fault and my installation leaves something to be desired.
* The recording had a lightning strike complaining of loss of signal, but played perfectly well.

On a different tack: years ago I found importing channel.db as a means of copying tuning between machines sometimes worked but mostly didn't. With what we know now, is there a reason for that?
 
Last edited:
For 546MHz (UHF35)
That's either Ch 30 or 586MHz.
Signal Detection is unavailable while a recording is in progress, but the hidden menu tuner test remains available and so far as I can see the recording is not interrupted* – who knew! I'm not even sure how that works...)
I knew. It crashed the machine when I tried it, so I didn't try it again.
I am therefore forced to conclude HDR4 is not at fault and my installation leaves something to be desired.
I think that sounds most likely.
On a different tack: years ago I found importing channel.db as a means of copying tuning between machines sometimes worked but mostly didn't. With what we know now, is there a reason for that?
No. It should always work, assuming you are on the same transmitter channels of course.
Even if you're not sometimes things work. When I inherited boxes from the North West region, some muxes worked on Mendip, for video/audio anyway.
 
You probably need to do it with the Humax software shutdown though /etc/init.d/S90settop shut and then reboot afterwards. I've never tried doing it without. You may or may not get unexpected results if you don't.
 
You probably need to do it with the Humax software shutdown though /etc/init.d/S90settop shut and then reboot afterwards. I've never tried doing it without. You may or may not get unexpected results if you don't.
I wonder how the "Copy DB to Flash" operation handles this!
 
Well obviously that's internal to the Humax software, so it knows. It's doing things behind its back that is the problem.
 
Back
Top