Problems with channels on same mux

[something_fishy]

I am using the npvr docker (on Unraid) with a Megasat MEG-8000 SatIP server. 

If I request recordings of two channels on the same mux the second channel knocks off the first (ie the first record is terminated with a stop time equal to the time the second program record starts, the first program is unhighlighted in the web program guide, however npvr still gives me a "cancel record" option on the first program). 

Tested in the attached logs with BBC2 HD and CBBC HD.

The same hardware will pull two channels off the same mux in TVheadend and dynamically takes a second physical tuner if needed. Npvr has no problem with two simultaneous records on different frequencies. 

Thanks

Eric

[mvallevand]

Sub will need to look, I can see by the logs that recordings are being abruptly stopped. These are in-progress recordings, though do you have the same trouble for scheduled future recordings?

Code:

2022-04-07 09:25:18.695    [DEBUG][9]    Reloading recording schedule
2022-04-07 09:25:18.697    [DEBUG][9]    PowerManagement CancelRecordingWakeupRequests (needs implementation)
2022-04-07 09:25:18.697    [DEBUG][9]    [Ratchet & Clank] at 04/07/2022 08:00
2022-04-07 09:25:18.697    [DEBUG][9]    Requesting wake up for 'RecordingOID860' [Ratchet & Clank] at 04/07/2022 07:58
2022-04-07 09:25:18.697    [DEBUG][9]    PowerManagement ScheduleWakeup (needs implementation)
2022-04-07 09:25:18.708    [DEBUG][9]    DefaultDirectoryChoice: first
2022-04-07 09:25:18.709    [DEBUG][9]    Preferred filename is 'Ratchet.&.Clank.(2016)'
2022-04-07 09:25:18.710    [DEBUG][9]    allocating recording target filename: /recordings/Ratchet & Clank (2016)/Ratchet.&.Clank.(2016)-0.ts
2022-04-07 09:25:18.711    [DEBUG][9]    About to start recording (860 on 21): /recordings/Ratchet & Clank (2016)/Ratchet.&.Clank.(2016)-0.ts...
2022-04-07 09:25:18.711    [DEBUG][9]    (Recording is due to be stopped at 04/07/2022 09:30)
2022-04-07 09:25:18.712    [DEBUG][9]    Stop SATIP stream
2022-04-07 09:25:18.712    [DEBUG][9]    StopStream handle: 3
2022-04-07 09:25:18.712    [DEBUG][9]    Closing TSWriter....: /recordings/BBC News/BBC News_20220407_09001200.ts
2022-04-07 09:25:18.712    [ERROR][9]    writer.Close() did not complete in a timely fashion
2022-04-07 09:25:18.712    [DEBUG][9]    Close@2

Martin

[something_fishy]

@mvallevand
To be honest I'm not sure, I will set up a series record on BBC1HD and BBC2HD (same mux) to test and report back.

At the risk of taking off topic, is npvr remuxing or transcoding the streams for your uidroid client? The reason I ask is that the SageTV android client (which uses exoplayer by default) can't handle UK OTA HD satellite feeds. Even remuxing doesn't seem to work reliably all of the time.

Cheers

Eric

[something_fishy]

To be honest I'm not sure, I will set up a series record on BBC1HD and BBC2HD (same mux) to test and report back.

The timeline has just advanced to the point at which both records should be running concurrently and the epg is only showing one highlighted and the recent recordings screens shows the first terminated after 5 seconds (npvr staggers simultaneous starts by a few seconds?). The logs are attached but it looks to me like the same behaviour is appearing.

[mvallevand]

No, NextPVR records the raw stream and all the UI clients including uidroid default to direct play via http. The mini client might be using a data push based on the older logic in their extenders that is different than http. There are some tricks in uidroid to use http.

I have noted that a few UK samples I have play better after they were remuxed, to strip out the "unknown" sub streams

On topic sub will need to look at the logs.

Martin

[something_fishy]

No, NextPVR records the raw stream and all the UI clients including uidroid default to direct play via http.  The mini client might be using a data push based on the older logic in their extenders that is different than http.  There are some tricks in uidroid to use http.

Whatever you do it works, FWIW the Channels client (on current generation FireTV) has problems with UK OTA HD streams also (and remuxing breaks its ability to skip forward and backward in my case). 

Apologies for taking off topic. 

Eric

[gEd]

Hi Eric
I use a UK DVB-T2 and the uidroid client doesn't like live TV or the native recordings (H.264 + LATM)
if you are interested in how I successfully re-mux them (via postprocessing.bat), open a new thread and I'll comment there.