Build 7817 (v3.5.2 / v4.5.2) Release Notes

[djp952]

Build 7817 - v3.5.2 / v4.5.2 (2021.05.27)

• Update SQLite database engine to version 3.35.5
• Update cURL library to version 7.77.0
• Prevent recording rule padding values from exceeding specified limits (1 hour for start padding, 3 hours for end padding)
• Fix bug that incorrectly set recording rule padding values to 30 seconds instead of zero seconds when specified as "0 min" in Kodi
• (Matrix) Fix "Unable to resolve timer type" errors reported in Kodi log when adding recording rules due to missing timer capabilities flag
• Apply channel logo image associated with a recording as the icon for that recording when available

Update SQLite database engine to version 3.35.5

Third-party dependency update; no anticipated impacts to the system.

Update cURL library to version 7.77.0

Third-party dependency update; no anticipated impacts to the system.

Prevent recording rule padding values from exceeding specified limits (1 hour for start padding, 3 hours for end padding)

This was a missed impact from some point in the past; the backend API limits the amount of padding that can be applied to any given recording rule, this change enforces that. An attempt to set start padding greater than 60 minutes or end padding greater than 180 minutes will be silently limited to those extents.

Fix bug that incorrectly set recording rule padding values to 30 seconds instead of zero seconds when specified as "0 min" in Kodi

This was a long standing defect attributed to misinterpretation of the backend API. When creating recording rules, not specifying a start/end padding value will be interpreted as "30 seconds", whereas the lack of start/end padding tags on a queried recording rule should be interpreted as "0 seconds". Reserving any judgment of the backend API inconsistency here, this change fixes things so that a padding value of "0 min" in Kodi will result in an equivalent recording rule with "0 seconds" of padding instead of "30 seconds". NOTE: Existing Kodi Timer Rules that were set to "0 min" (this is the default) will need to be updated to properly reapply the padding value(s). I suggest changing one of the padding values, save it, then go back into that Timer Rule and set it back to "0 min".

(Matrix) Fix "Unable to resolve timer type" errors reported in Kodi log when adding recording rules due to missing timer capabilities flag

This was a fairly benign defect that only existed on the Matrix baseline. Due to a missing capabilities flag for the PVR addon's EPG-based timers (PVR_TIMER_TYPE_REQUIRES_EPG_SERIESLINK_ON_CREATE) Kodi 19 "Matrix" was reporting an "Unable to resolve timer type" error in the Kodi log any time the addon timer types were queried. No change to any functionality is expected.

Apply channel logo image associated with a recording as the icon for that recording when available

Kodi "Matrix" version 19.1's default Estuary skin added icons to the Recordings area/lists. For individual recordings, this icon is requested via an optional property that the PVR addon did not support, which led to display of a generic movie projector icon for all items:

This change supplies Kodi with that optional icon based on the only other icon/thumbnail metadata provided by the HDHomeRun backend, which will be the channel logo:

A pending change already approved for Kodi 19.2 will automatically default this icon to the channel icon if the PVR addon does not supply one for the recording item. To that end, I've made reporting the channel icon dependent upon the General / Disable backend channel logo images addon setting. If this setting is set to OFF (default), the addon will supply the backend channel logo as the recording icon. If this setting is set to ON, the addon will not supply any recording icon. Users that have this set to ON will not notice any change until Kodi 19.2, but at that point any custom channel icon(s) that have been set in Kodi are expected to appear here "automagically".

Questions, Concerns? Let me know!