Main Menu

Recording Failures

Started by srto2, October 11, 2023, 05:21:36 PM

Previous topic - Next topic

srto2

I am still seeing these errors:  This is the third similar error this week.

Foreign Correspondent

'Series 2023, Episode 24'

ABC TV HD, 8:02pm, Thu, 12 Oct 2023, 34 minutes

Recording Options

This show is part of a series recording but will not be recorded. (There were not enough tuners to record this airing. It has been moved to the next airing on 2023-Oct-15 12:58:00)



8.02 PM??  With four tuners, I'm only recording from two networks this Thursday.  So is the problem with the Ice PlugIn/TvHeadend/Kodi/LibreElec or is it at the server end?

I can, and will, set a recording locally but the fundamental reson for subscribing in the first place is to, well, set and forget, and have the freedom to set recordings remotely.

I'm trying to be patient with these issues but would appreciate feedback, with some indication of any rectification progress.  I'm retired now and have limited funds for luxuries like my ICE subscription.

Regards, Rob

MD

Hi Rob,

It looks as if you are a BYOB user and I see you are using our tuners so could you tell us your setup as there are no known issues such as you described now we have new SSDs?

Daniel Hall at IceTV

Hi Rob,

Do you turn the box off overnight? or put it to standby at all?
Regards,

Daniel.
CTO.

raymondjpg

Quote from: Daniel Hall at IceTV on October 11, 2023, 09:41:21 PMHi Rob,

Do you turn the box off overnight? or put it to standby at all?
I'm not sure if it's helpful but I have seen this once before
https://forum.icetv.com.au/index.php?topic=7688.msg39770#msg39770 (and below).

It looks to me like some wrinkle with the EPG, but I don't have many timers set usually, and I haven't encountered it since so I haven't been able to see any pattern.

Also, and again I don't know if it's relevant, but I was seeing an issue yesterday with some empty slots in the EPG grid, and when I cleared the EPG and forced a download the grid only populated from about 10 hours in the future onwards i.e. the grid was completely empty from the current time until 10 hours later.
Beyonwiz T2, Beyonwiz U4, IceBox BYO with Hauppauge WinTV-dualHD (x2), Hauppauge WinTV-quadHD

IanL-S

You should also confirm that the USB tuners are correctly configured - you do this via the TVHeadend web server - URL is:

http:\\{ip address of IceBox}:9981/

Click on Configuration then DVB Inputs, all of the tuners should be depicted in bold text and set to DVB-T.

Was just checking my BYOB and found one of the tuners was not correctly configured - something seriously wrong as I cannot get it to "activate". My problem, not yours.

Ian
IceTV: IceBox + BYOB IceBox + 2xTRF-2400 + 2xTF7100HDPVRtPlus + SKIPPA [RIP] + T2 + U4 + V2
No IceTV: a few Toppys and T2
Synology NAS
Check out the oztoppy wiki and oztoppy Forum for Toppy help

srto2

Quote from: MD on October 11, 2023, 08:15:37 PMHi Rob,

It looks as if you are a BYOB user and I see you are using our tuners so could you tell us your setup as there are no known issues such as you described now we have new SSDs?
Thanks MD.

Well, it has happened before, and Daniel posted on 31/8/23 " We have seen an incorrect error come back now and then if the IceBox has been off or a while and then turns back on. We are actively working on a fix and have some ideas as to why this happens so hopefully we can get it resolved asap. "

I have two BYOB boxes, a Lenovo M920Q (i7, 16GB, Samsung 1tB SSD) and a Lenovo M700 (i5 8GB Crucial 1tB SSD).  When the M700 came up with the errors I switched to the M920 and the same errors returned. At least one of the machines is always up these days.

I appreciate that intermittent faults can be excrutiatingly difficult. The only thing I can see in each case is that the guide time for the particular program seems to be off by a minute or two when the problem has popped up.

And, for info, I have three Ice/Hauppauge tuners.  I purchased the third for testing a Raspberry Pi (4B) implementation of LibreElec/Kodi with the ICE XMLTV guide feed.  That works exceptionally well, but the third tuner does not behave normally when used with either of the Lenovo boxes.  It is fine from a cold boot but fails to initialise if the box is resuming from suspend mode.  The first two tuners don't exhibit the problem.  Not an issue with the Pi of course.

But if Daniel is right, could even an otherwise apparently A-OK tuner introduce some corruption when it is initialised following resumption from suspend or even a reboot?

Regards, Rob


 

IanL-S

Not sure what is happening in your case. But I find the following interesting:
QuoteI appreciate that intermittent faults can be excrutiatingly difficult. The only thing I can see in each case is that the guide time for the particular program seems to be off by a minute or two when the problem has popped up

TVHeadend can have difficulties when a timer is updated by a minute or so (for me this mostly on ABC); it apparently deletes the timer and can either schedule the recording of the previous episode of the program or the next instance of the same episode. I have seen both happen. In each case it results in the program not being recorded at the time intended. It is IceBox specific, the same programs record properly on my Toppys and Beyonwizs.
IceTV: IceBox + BYOB IceBox + 2xTRF-2400 + 2xTF7100HDPVRtPlus + SKIPPA [RIP] + T2 + U4 + V2
No IceTV: a few Toppys and T2
Synology NAS
Check out the oztoppy wiki and oztoppy Forum for Toppy help

srto2

Quote from: IanL-S on October 12, 2023, 04:25:33 PMTVHeadend can have difficulties when a timer is updated by a minute or so (for me this mostly on ABC); it apparently deletes the timer and can either schedule the recording of the previous episode of the program or the next instance of the same episode. I have seen both happen. In each case it results in the program not being recorded at the time intended. It is IceBox specific, the same programs record properly on my Toppys and Beyonwizs.
I think there will probably be a fix buried somewhere in the kludge that is LibreElec + TvHeadend + Kodi +Ice.  I have trawled all the relevant wikis and forums and ended up being amazed that anything works at all.

When I decided to repurpose a bunch of hardware, two pc's and Rpi, I recreated everything from scratch a few times and never experienced many obvious problems until installing the ICE specific version - which wouldn't install at all until Daniel Hall issued a patch. Transferring recordings from one box to another is ridiculously stupid but I have a work-around for that.  The initial straightforward copy of a recording ends up apparently "deleted" by TVHeadend... 

I'm using the "Amber" skin rather than the generic Kodi skin but the occasional recording snafu seems independent of that at least. I experimented with different skins to see whether any of them caused major issues.   The "Amber" menu structure is better but still suffers from Kodi's inability to implement sensible, consistent, remote control functions.

Having said all that I've come close to thinking that, as we use streaming options a lot now, maybe the ancient method of reading the guide and manually setting timers might suffice but I'll persist with the BYOB path for now.  Often now I'll set a timer to record a series and then binge the lot online anyway.

Daniel Hall at IceTV

Hi Rob,

There are a couple of things to this.

The error message on the website doesn't necessarily mean it was a tuner availability issue, this is just the most common cause when the feature was first introduced so it's hard coded into the website. This just means that the timer was marked as failed at some point.

My current theory is that there is a certain combination of EPG updates that cause this, but I have not been able to track down the exact combination as yet. There are some updates and fixes that are being prioritised at the moment ready for the next batch of IceBox's to arrive so it will likely be a couple of weeks before I will have a chance to try and test all the scenarios to find the one that causes this.
Regards,

Daniel.
CTO.

srto2

Quote from: Daniel Hall at IceTV on October 12, 2023, 06:08:23 PMHi Rob,

There are a couple of things to this.

The error message on the website doesn't necessarily mean it was a tuner availability issue, this is just the most common cause when the feature was first introduced so it's hard coded into the website. This just means that the timer was marked as failed at some point.

My current theory is that there is a certain combination of EPG updates that cause this, but I have not been able to track down the exact combination as yet. There are some updates and fixes that are being prioritised at the moment ready for the next batch of IceBox's to arrive so it will likely be a couple of weeks before I will have a chance to try and test all the scenarios to find the one that causes this.
Thanks Daniel,

When I embarked on the BYOB exercise I was originally hoping to implement an RPi solution in order to reduce power consumption.  (About $0.58 per peak kW/h here.) The Pi works well but of course I can't schedule recordings with ICE.  So I have played with the two PC's initially hoping that the ICE plugin (and the server end) would be a little more developed, and I'm still waiting!  Many years of pretty much flawless performance with Topfield and Beyonwiz PVR's sucked me in.

Unfortunately perhaps, my major career was aviation based, instrument landing systems, nav-aids, radio communications and so on, mostly back in the analog days, so my programming expertise is somewhat limited. The BYOB is forcing me to get re-acquainted with Linux though.

Meantime I appreciate what's happening in the background and I'll hang in for a bit longer...

Cheers, Rob

Daniel Hall at IceTV

Hi Rob,

We do plan to have an RPi build of the IceBox firmware at some point, there are some things we need to get done first before we look at branching out like that.
Regards,

Daniel.
CTO.

DeltaMikeCharlie

Firstly, I would check to see how many networks (not channels) you can manually record simultaneously via Kodi.  This should tell you fairy quickly how TVH is actually configured.

If this number does not match your expectations, perhaps TVH has a configuration issue with recognising its tuners.

If this is the case, double-check the link between the 'TV adapters' and the 'Networks' in the TVH Web UI.

http://<IceBox_IP_Address>/extjs.html#

In TVH, there is a chain of data structures that are required for a recording to occur.

A recording takes place on a 'channel'.  A 'channel' can be sourced from multiple 'services'.  Each 'service' originates from a 'mux'.  Each 'mux' comes from a 'network' and each 'network' is attached to one or more 'tv adapters' (tuners).

If you go into Configuration -> DVB Inputs -> Networks, you should see one called 'DVB-T Network'.  In Sydney, I have 60 'Services' and 'Mapped Channels' shown, although your location may be different.

Then go into Configuration -> DVB Inputs -> TV adapters and for all of your 'DVB-T' adapters, ensure that 'DVB-T Network' is included in the 'Networks' field.

If all of this is in order, then assuming that the timer in question gets all the way to TVH on the IceBox and then fails, perhaps enabling debugging/tracing on TVH may be able to provide some insights.

In TVH, you need to go into its Web UI -> Configuration -> Debugging.  If you press the Help button, you can get a list of the subsystems.

I would try logging for 'dvr' to see the timers.  I would also try 'epg' and 'epgdb' to see the EPG changes, although this will be very active and create a lot of log entries.  If an EPG change for the programme in question precedes a recording faulire, it may help narrow down the root cause.

Failing these, 'api' may show when TVH receives timer creation commands from the Ice add-on and 'uuid'/'idnode' may show when timer entries are created/edited/deleted.  'subscription' may also show when tuners are called into service, released or not available for live TV and/or recordings.

Because the Ice TV EPG is fed via XMLTV, it should also be possible for ICE to experiment by creating dummy EPG entries and see if they can force the error to occur.

It has been a while since I looked into how LibreELEC is built, however, I seem to recall that whilst Kodi is relatively up-to-date, it uses a very old version of TVH and perhaps you are encountering a bug that has already been identified and fixed long ago.

IanL-S

Not sure of the status of TVHeadend development; 4.2.X seems to be the lates, with 4.4 apparently abandoned, and 4.6 in early development (https://tvheadend.org/projects/tvheadend/roadmap).
IceTV: IceBox + BYOB IceBox + 2xTRF-2400 + 2xTF7100HDPVRtPlus + SKIPPA [RIP] + T2 + U4 + V2
No IceTV: a few Toppys and T2
Synology NAS
Check out the oztoppy wiki and oztoppy Forum for Toppy help

DeltaMikeCharlie

Quote from: IanL-S on October 13, 2023, 08:34:16 AMNot sure of the status of TVHeadend development;
I have been doing some development work on TVH and contributing via GitHub, etc.

From what I have been able to tell, they have stopped making official releases.  From what I can remember, the person that manages the project is fairly new-ish at it and does not have a lot of free time.  When a pull request is merged on GitHub, there are some build scripts that will make DEB files, etc, that some people install directly.

https://tvheadend.org/boards/5/topics/50181

The LibreELEC build process grabs a fairly old release of TVH, merges in a few patches and then compiles that version.

I am thinking about two (unsupported) ways of getting Ice and the latest version of TVH together:

1) Deconstruct the BYOB image and update the TVH component before reconstructing and then installing.
2) Build a 100% custom Linux/TVH/Kodi installation with all of the versions of things that I want and then extract the IceTV Kodi add-on from the BYOB image to be installed in Kodi.

IceTV could consider releasing the add-on as a stand-alone add-on.  I don't know how much margin they make on the IceBox hardware, but I imagine that the bulk of their revenue would come from the ongoing subscription fees.  Having an add-on only option could be marketed as one step down from the BYOB for 'DIY Enthusiasts'.

srto2

Quote from: DeltaMikeCharlie on October 13, 2023, 06:49:57 AMFirstly, I would check to see how many networks (not channels) you can manually record simultaneously via Kodi.  This should tell you fairy quickly how TVH is actually configured.

If this number does not match your expectations, perhaps TVH has a configuration issue with recognising its tuners.

If this is the case, double-check the link between the 'TV adapters' and the 'Networks' in the TVH Web UI.

http://<IceBox_IP_Address>/extjs.html#

In TVH, there is a chain of data structures that are required for a recording to occur.

A recording takes place on a 'channel'.  A 'channel' can be sourced from multiple 'services'.  Each 'service' originates from a 'mux'.  Each 'mux' comes from a 'network' and each 'network' is attached to one or more 'tv adapters' (tuners).

If you go into Configuration -> DVB Inputs -> Networks, you should see one called 'DVB-T Network'.  In Sydney, I have 60 'Services' and 'Mapped Channels' shown, although your location may be different.

Then go into Configuration -> DVB Inputs -> TV adapters and for all of your 'DVB-T' adapters, ensure that 'DVB-T Network' is included in the 'Networks' field.

If all of this is in order, then assuming that the timer in question gets all the way to TVH on the IceBox and then fails, perhaps enabling debugging/tracing on TVH may be able to provide some insights.

In TVH, you need to go into its Web UI -> Configuration -> Debugging.  If you press the Help button, you can get a list of the subsystems.

I would try logging for 'dvr' to see the timers.  I would also try 'epg' and 'epgdb' to see the EPG changes, although this will be very active and create a lot of log entries.  If an EPG change for the programme in question precedes a recording faulire, it may help narrow down the root cause.

Failing these, 'api' may show when TVH receives timer creation commands from the Ice add-on and 'uuid'/'idnode' may show when timer entries are created/edited/deleted.  'subscription' may also show when tuners are called into service, released or not available for live TV and/or recordings.

Because the Ice TV EPG is fed via XMLTV, it should also be possible for ICE to experiment by creating dummy EPG entries and see if they can force the error to occur.

It has been a while since I looked into how LibreELEC is built, however, I seem to recall that whilst Kodi is relatively up-to-date, it uses a very old version of TVH and perhaps you are encountering a bug that has already been identified and fixed long ago.
Thanks DMC,  Just a quickie here as I have to go out.  Sorry for the long quote too!

I can simultaneously, manually, record from four muxes.  I have 61 services and 61 mapped channels.  I've often had timers set for three muxes (ABC, SBS, Seven) with successful recordings

When the timer failure occurred most recently I shut down the BYOB, logged into ICE and transferred the timer list to my second BYOB.  The second BYOB immediately flagged the same timer errors.

Because boot or resume from suspend has been suggested as undesirable I am looking at NTP server queries to see how long each BYOB takes to get time sync.  There is a burst of four queries each to two NTP (1.* and 3.*) servers at bootup.  Maybe a time sync error can cause the intermittent hiccup?  I might point the NTP servers to 0.au.ntp.org and 1.au.ntp.org as well.

I appreciate what you're doing with TVHE and I would second your suggestion of ICE releasing their add-on if only that it would allow me to use an Rpi permanently .

I'll look at the remainder of your suggestions later in the day.

Regards, Rob