Posts: 2,506
Joined: May 2007
Reputation:
118
Great news! I think 🤔
Will check new sample shortly. Does the new sample work ok on CoreElec?
I.e. it’s only libreElec where it doesn’t work?
Posts: 61
Joined: Jun 2016
Reputation:
0
@phunkyfish I made seven different test recordings last night.
1. duration 36:59
2. duration 36:59
3. duration 1:07:00
4. duration 1:06:59
5. duration 36:59
6. duration 1:06:59
7. duration 32:00
Testing with Raspberry Pi3 and two different versions of Kodi; stable LibreElec and latest Milhouse build (#0109)
Stable:
1. wrong duration (9:40:07), skipping works
2. wrong duration (9:40:08), skipping works
3. working ok
4. working ok
5. wrong duration (9:40:08), skipping works
6. working ok
7. wrong duration (17:59:36), skipping works (duration is very wrong!)
Milhouse:
1. cannot see duration, skipping doesn't work
2. cannot see duration, skipping doesn't work
3. cannot see duration, skipping doesn't work
4. cannot see duration, skipping doesn't work
5. cannot see duration, skipping doesn't work
6. cannot see duration, skipping doesn't work
7. working ok
I know that in old LibreElec there is no implementation of GetStreamTimes, but just testing if you can find any correlation between those problems.
I cannot test CoreElec at the moment. Just Raspberry and PC.
Posts: 2,506
Joined: May 2007
Reputation:
118
Great, I think raspberry is enough for now.
The fact that the only recording that works correctly is under 36 mins in the nightlies backs up my theory on the int32/64. I think the others result in a negative number which doesn’t get displayed.
I have changed a cast used in GetStreamTimes from time_t to int64 in the latest PR (3.16.2). The type time_t is not guaranteed to be 64bit on all platforms. Fingers crossed this one solves it.
We’ll have to wait for the next nightly build to see!