Steps to repro:
1. Setup ServIO to record pre-season football games of a team of your choice.
2. Verify day-of that the game is set to record (shows in tasks lists as highest priority).
3. One hour after game starts, attempt to watch time-shifted (ISSUE A).
4. One day after game started, review logs from Tuner to verify Servio requested and received the http stream
Code: Select all
20190830-01:59:29 Tuner: tuner0 tuning 1013 KCPQDT (auto:231MHz-1) 20190830-01:59:29 Tuner: tuner0 streaming http to 192.168.10.56:33145 20190830-01:59:29 CableCARD: tuner0 1013 KCPQDT (auto:231MHz-1) access = subscribed [[ … entries omitted … none related to tuner0, none related to channel 1013 … ]] 20190830-06:00:00 Tuner: tuner0 http stream ended (remote closed)
Expected Results (ISSUE A):
It is expected that, as soon as the recording begins, the recording will appear in the "Recorded" list.
Preferably, it will show as currently-being-recorded, such as with a red circle overlay.
Expected Results (ISSUE B):
It is expected that, after the recording ends, the recording will appear in the "Recorded" list.
Actual Results (Both A & B):
The recording of the football games did not appear.
During this time, other shorter recordings DID appear after they were recorded.
Note that there is NO viable workaround to enable time-shifted viewing of a currently-ongoing game. However, rebooting the Servio did cause multiple, previously-recorded but not-appearing-in-UI pre-season football games to suddenly appear in the UI.
So why the discrimination against pre-season football?
Is there something different for recordings that are set to record more than 3 hours of HD content?
Is the software verifying a filesize using a 32-bit signed integer somewhere by accident (and thus treating a larger value as negative)?
Is the Servio filled with advanced AI, that perceives that pre-season games don't count, and thus believes they could only be recorded by user error?
Thoughts on this are greatly welcome....