Sewing Bee has not tracked for next week

hairy_mutley

hairy_mutley

Active Member
I am assuming that this isn't machine (HDR-Fox-T2) or CF specific...
The Great British Sewing Bee (Wed 21:00 BBC1) recorded as first in series last night, but has not linked to next week's episode (it is just sitting in the schedule list as a series with no next episode).
The seriesCRID looks OK to me (but that doesn't mean much).
Just thought that I would mention it so that people could re-schedule if necessary.
 
Last edited:
2020-04-23_15.21.23.jpg
It re-scheduled next week's episode on my HDR-Fox T2 OK which was series recorded before the first transmission yesterday
 
hairy_mutley said:
I am assuming that this isn't machine (HDR-Fox-T2) or CF specific...
The Great British Sewing Bee (Wed 21:00 BBC1) recorded as first in series last night, but has not linked to next week's episode (it is just sitting in the schedule list as a series with no next episode).
The seriesCRID looks OK to me (but that doesn't mean much).
Just thought that I would mention it so that people could re-schedule if necessary.
Click to expand...
mine has tracked. what is going on?
 
In that case, very odd.
Before I posted I had put it to standby and powered up again (the disk did stop, so not a delinquent standby).
Now, I have just powered it off and on again. But it stays the same
Capture.PNG
If necessary, I will just unschedule and reschedule it.

Just as an experiment...
I have tried scheduling it on my second HDR, no problem.
Using the CF, I can view the schedule's Series CRID; on the first HDR it is SCRID:/m/9XIX/01, on the second it is SCRID:/m/9XIX
Not sure if that difference is relevant?
 
I have just noticed that Ezra's starts "The", mine does not.
The one that I have just scheduled on the second HDR also starts "The".
 
hairy_mutley said:
If necessary, I will just unschedule and reschedule it.
Click to expand...
Try 'Refresh Events' on the schedule Opt+ menu before rescheduling (it can take a while before the refresh works)
What is the series crid when you click on the program name in schedule display? it should be /M/9XIX/01
hairy_mutley said:
I have just noticed that Ezra's starts "The", mine does not.
Click to expand...
The name is not significant - it is all based on sCRID
 
mihaid said:
could it possibly be that you just recorded the episode rather than the series? that 01 at the end looks odd
Click to expand...
I cannot remember, but, unless by mistake, I would only have done it if the series option wasn't available at the time.
But, doesn't the final icon confirm it as a series recording. Also, it recorded into the directory "Great British Sewing Bee"; which I wouldn't have created or swept to.
So, I think the evidence is in favour of a series recording.
I can only wonder if I set it to record early (e.g. the Wednesday before) and the EPG information was different at that time.

MymsMan said:
Try 'Refresh Events' on the schedule Opt+ menu before rescheduling (it can take a while before the refresh works)
Click to expand...
done with no change so far, but how do I know when I have waited long enough :o_O:
MymsMan said:
What is the series crid when you click on the program name in schedule display? it should be /M/9XIX/01
Click to expand...
Next week's episode in the EPG it is fp.bbc.co.uk/m/9XIX
In the schedule (as I said in post #4); HRD1 says /m/9XIX/01, HDR 2 says /m/9XIX

MymsMan said:
The name is not significant - it is all based on sCRID
Click to expand...
but does that not suggest that something changed between me & Ezra scheduling the recording.
 
hairy_mutley said:
done with no change so far, but how do I know when I have waited long enough
Click to expand...
It seems to vary and not be updated whilst recording but within a minute otherwise
hairy_mutley said:
In the schedule (as I said in post #4); HRD1 says /m/9XIX/01, HDR 2 says /m/9XIX
Click to expand...
But that wasn't the question, What is it when clicked on in the Schedule view not in the EPG?
The schedule view show what it is looking for and will always be upper cased
1587662842063.png
 
I did schedule it the previous Wednesday (possibly through RS)
/mod/tmp/nugget.log has the following snippet.
Code: 
[nugget]: Wed Apr 15 12:42:05 2020: Persistent log starting, v1.0
[nugget]: Wed Apr 15 12:42:05 2020: schedule save starting.
[nugget]: Wed Apr 15 12:42:06 2020: schedule save complete.
[nugget]: Wed Apr 15 12:42:06 2020: Re-loading schedule database (41).
[nugget]: Wed Apr 15 12:42:06 2020: Closing database.
[nugget]: Wed Apr 15 12:42:06 2020: Schedule load failed.
[nugget]: Wed Apr 15 12:42:06 2020: NULL database handle.
[nugget]: Wed Apr 15 12:42:06 2020: Schedule failed to reload, deferring.
[nugget]: Wed Apr 15 12:42:06 2020: Deferred thread starting for '41:+9' (attempt 1)
[nugget]: Wed Apr 15 12:42:09 2020: Re-loading schedule database (41).
[nugget]: Wed Apr 15 12:42:09 2020: schedule reload complete (41).
[nugget]: Wed Apr 15 12:42:09 2020: slots(41, +9)
[nugget]: Wed Apr 15 12:42:09 2020: Processing slot +9 (9)
[nugget]: Wed Apr 15 12:42:09 2020:   Great British Sewing Bee
[nugget]: Wed Apr 15 12:42:09 2020:    @ 1587585600 (Wed Apr 15 12:42:09 2020)
[nugget]: Wed Apr 15 12:42:09 2020:   CRID: 2/[FP.BBC.CO.UK/m/9XIX/01]
[nugget]: Wed Apr 15 12:42:09 2020:   Recorded:
[nugget]: Wed Apr 15 12:42:09 2020:   Last Event: 0
[nugget]: Wed Apr 15 12:42:09 2020:   Events: 1FP.BBC.CO.UK/m/9XIW|
[nugget]: Wed Apr 15 12:42:09 2020:  [0] 196650,1587585600,1587589200,11458
[nugget]: Wed Apr 15 12:42:09 2020:       Wed Apr 15 12:42:09 2020 +60m
[nugget]: Wed Apr 15 12:42:09 2020:  Wake 1587584700 - Wed Apr 15 12:42:09 2020
[nugget]: Wed Apr 15 12:42:09 2020: Ready 1587584670 - Wed Apr 15 12:42:09 2020
[nugget]: Wed Apr 15 12:42:09 2020: Adding timer(1587584670)
[nugget]: Wed Apr 15 12:42:09 2020:     - Wed Apr 15 12:42:09 2020
[nugget]: Wed Apr 15 12:42:09 2020: Deferred thread exiting.
[nugget]: Wed Apr 15 15:31:18 2020: schedule save starting.
[nugget]: Wed Apr 15 15:31:18 2020: schedule save complete.

/mod/tmp/rs.log has this
Code: 
anacron Wed Apr 15 04:18:32 BST 2020
Could not acquire lock.
Processing command 'schedule '
*Schedule 17540/11458/2/101/BBC ONE HD/1587585600/Great British Sewing Bee
*Trying source service/event ID.
_Found event - Great British Sewing Bee
_Successfully scheduled event.
Sending TBL_RESERVATION schedule information to remote server.
 Updating...
Sending skiplist information to remote server.

MymsMan said:
The schedule view show what it is looking for and will always be upper cased
Click to expand...
on HDR 1 it is FP.BBC.CO.UK/m/9XIX/01, on HDR 2 it is FP.BBC.CO.UK/m/9XIX
This is HDR 1

Capture.PNG
 
your rs log is exactly the same as mine
my nugget does not have the info , persistent log instead
 
I don't know how you got a lower case url into the schedule entry but it could be the cause of the problem if the Humax is upper casing the epg scrid before comparing it with crid in the schedule entry,

I just scheduled a series via RS and the crids were upper cased as expected. (they are mixed case in nugget.log)
1587669219332.png
 
I have been through the schedules on both HDRs (including the expired entries) and there is no lower case in any of them other than the Sewing Bee on both units; which both have the "m".
How come my HDR 2 has the same "m"? I scheduled that today using WebIf, so there must be something repeatable, but where to look for a diagnosis?
 
In case it is any help...
This is the nugget.log for HDR 2 scheduling via WebIf
Code: 
[nugget]: Thu Apr 23 16:14:01 2020: Persistent log starting, v1.0
[nugget]: Thu Apr 23 16:14:02 2020: schedule save starting.
[nugget]: Thu Apr 23 16:14:02 2020: schedule save complete.
[nugget]: Thu Apr 23 16:14:02 2020: Re-loading schedule database (27).
[nugget]: Thu Apr 23 16:14:02 2020: Closing database.
[nugget]: Thu Apr 23 16:14:02 2020: Schedule load failed.
[nugget]: Thu Apr 23 16:14:02 2020: NULL database handle.
[nugget]: Thu Apr 23 16:14:02 2020: Schedule failed to reload, deferring.
[nugget]: Thu Apr 23 16:14:02 2020: Deferred thread starting for '27:+12' (attempt 1)
[nugget]: Thu Apr 23 16:14:05 2020: Re-loading schedule database (27).
[nugget]: Thu Apr 23 16:14:05 2020: schedule reload complete (27).
[nugget]: Thu Apr 23 16:14:05 2020: slots(27, +12)
[nugget]: Thu Apr 23 16:14:05 2020: Processing slot +12 (12)
[nugget]: Thu Apr 23 16:14:05 2020:   The Great British Sewing Bee
[nugget]: Thu Apr 23 16:14:05 2020:    @ 1588190400 (Thu Apr 23 16:14:05 2020)
[nugget]: Thu Apr 23 16:14:05 2020:   CRID: 2/[FP.BBC.CO.UK/m/9XIX]
[nugget]: Thu Apr 23 16:14:05 2020:   Recorded:
[nugget]: Thu Apr 23 16:14:05 2020:   Last Event: 0
[nugget]: Thu Apr 23 16:14:05 2020:   Events: 1FP.BBC.CO.UK/m/A275|
[nugget]: Thu Apr 23 16:14:05 2020:  [0] 196648,1588190400,1588194000,11584
[nugget]: Thu Apr 23 16:14:05 2020:       Thu Apr 23 16:14:05 2020 +60m
[nugget]: Thu Apr 23 16:14:05 2020:  Wake 1588189500 - Thu Apr 23 16:14:05 2020
[nugget]: Thu Apr 23 16:14:05 2020: Ready 1588189470 - Thu Apr 23 16:14:05 2020
[nugget]: Thu Apr 23 16:14:05 2020: Adding timer(1588189470)
[nugget]: Thu Apr 23 16:14:05 2020:     - Thu Apr 23 16:14:05 2020
[nugget]: Thu Apr 23 16:14:05 2020: Deferred thread exiting.

and it schedule
Capture.PNG
 
Scheduled through WebIF on a HDR-FOX:

E5D015A7-48CA-4307-A742-723AA896089E.jpeg (lower case "m")

Scheduled through SUI on a HD-FOX:

1587707908559.jpeg (upper case "M")

Have to wait until Wednesday to see if they both record!
 
Black Hole said:
Have to wait until Wednesday to see if they both record!
Click to expand...
My prediction is they will both record (once it has the eventid number in the schedule it no longer needs the event crid)
More intersting will be whether it adds the following weeks epsisode to the schedule when that is added to the epg.
 
@af123: That there is any kind of difference between SUI and WebIF indicates there is a bug in the WebIF, in that it does not reproduce the behaviour of the SUI (even if the SUI's behaviour is flawed).
 
On further investigation the lower case m is a red herring - the webif always adds the 2nd half of the URL in mixed case (why?) and the humax upper cases it the first time it updates the entry when adding new entries

So why did @hairy_mutley's new event fail to schedule
hairy_mutley said:
Using the CF, I can view the schedule's Series CRID; on the first HDR it is SCRID:/m/9XIX/01, on the second it is SCRID:/m/9XIX
Not sure if that difference is relevant?
Click to expand...
The BBC has changed the series crid dropping the /01 suffix and so the humax could not find any new entries for /m/9XIX/01
the rest of us first scheduled the series after the BBC changed the series crid and so the humax could find next week's episode when it was added to the epg.
 
Last edited:
You must log in or register to reply here.
Back
Top