2022-12-02, 01:00 AM
Testing my new linux NextPVR setup for about 3 weeks now. Slow rolling to make sure everything works as expected but was also waiting for an ESR meter from China as my old Bell boxes need some new capacitors...
First week and a half: scheduled to record 3 series shows daily on different channels, times not consecutive. Periodically also used a browser to confirm channel changes worked. All good.
Next, added 2 consecutive timed weekly shows to record but on different channels. First show recorded okay but still included the default post padding. The recording includes the channel change info header at the end of the show when padding starts. The video and audio devices would still be in use for the the first recording so the second recording gets no data and fails.
Thought I might have messed something up so waited to see what happened the next week week. Same result.
Set up test recordings yesterday to confirm the behavior and it did. Consecutive recordings on the same channel recorded okay.
Set up 3 shows to record today to get a short log. First recording is at 3 pm is okay. Second recording is at 4 pm and third recording at 4:30 pm on a different channel. The second recording continues to the end of the post padding. The third recording is started at 4:30 and changes the channel but gets no data and fails. Log attached.
Probably the same issue but under different circumstances, I inadvertently left a channel running in the browser one night and it was still running the next morning. (Basement computer on low volume so it wasn't noticeable upstairs.) The scheduler made multiple attempts made to record a scheduled show on different channels during the night, all fails.
The behavior I would expect in this situation is that when a channel change is required, the first recording is stopped on time without post padding, then after a few seconds (or when the process is confirmed to have stopped) the next recording is started.
I assume this is a bug?
Platform info:
Linux Mint 21, up to date.
NextPVR version 6.1.1.221106
One extras tuner active, (second present but disabled and not set up), usb 3 HDMI capture devices
The extras tuner is a shell script that parses the channel number parameter, sends lirc commands to a Raspberry Pi 2b to do the blasting, then starts ffmpeg to create an mpegts stream to stdout.
First week and a half: scheduled to record 3 series shows daily on different channels, times not consecutive. Periodically also used a browser to confirm channel changes worked. All good.
Next, added 2 consecutive timed weekly shows to record but on different channels. First show recorded okay but still included the default post padding. The recording includes the channel change info header at the end of the show when padding starts. The video and audio devices would still be in use for the the first recording so the second recording gets no data and fails.
Thought I might have messed something up so waited to see what happened the next week week. Same result.
Set up test recordings yesterday to confirm the behavior and it did. Consecutive recordings on the same channel recorded okay.
Set up 3 shows to record today to get a short log. First recording is at 3 pm is okay. Second recording is at 4 pm and third recording at 4:30 pm on a different channel. The second recording continues to the end of the post padding. The third recording is started at 4:30 and changes the channel but gets no data and fails. Log attached.
Probably the same issue but under different circumstances, I inadvertently left a channel running in the browser one night and it was still running the next morning. (Basement computer on low volume so it wasn't noticeable upstairs.) The scheduler made multiple attempts made to record a scheduled show on different channels during the night, all fails.
The behavior I would expect in this situation is that when a channel change is required, the first recording is stopped on time without post padding, then after a few seconds (or when the process is confirmed to have stopped) the next recording is started.
I assume this is a bug?
Platform info:
Linux Mint 21, up to date.
NextPVR version 6.1.1.221106
One extras tuner active, (second present but disabled and not set up), usb 3 HDMI capture devices
The extras tuner is a shell script that parses the channel number parameter, sends lirc commands to a Raspberry Pi 2b to do the blasting, then starts ffmpeg to create an mpegts stream to stdout.
