FoodLioon wrote: ↑Wed May 19, 2021 8:18 pm
Creating a Recording: Record Series Timer from Kodi with zero padding will actually have 30 seconds added to the start and end. A one-off recording will respect the zero setting.
I think this was discussed before but I couldn't find it. May be a feature of the DVR service, not a bug.
, I was unable to 100% duplicate the concern (I get the same results for both series and one-off rules), but I can explain what's going on here.
HDHomeRun DVR has a minimum/default setting of 30 seconds
for both start and end padding, whereas Kodi defines this value in minutes
. The addon currently translates "0 mins" to mean "30 seconds", and vice-versa, since values less than 30 seconds will be ignored by the HDHomeRun backend and silently converted to the default (30 seconds). I apologize for not remembering this, I believe this conversion has been in place for many years, probably since version 1.0.0
I did note something that needs to be fixed in that the updated HDHomeRun API documentation defines limits for the start/end padding that weren't previously noted (1 hour vs. 3 hours, respectively) that the addon should obey, and I feel that the addon should omit the padding value altogether rather than arbitrarily setting it to 30 seconds
if Kodi is trying to set 0 minutes
A change definitely needs to be made to accommodate the updated API boundaries, and it's mathematically impossible to resolve the time unit difference (seconds vs. minutes) without an arbitrary decision, but I am concerned that I was not able to see what you are seeing here. Are you able to expound any further on how you determined the difference between "0 seconds" and "30 seconds" in Kodi? Kodi deals in minutes and the existing addon logic (while seemingly imperfect) seems to hold up so far in the scenarios I've run to date. HDHomeRun should always pad a minimum of 30 seconds to both start and end; I have not found a way to make this any more granular...