No longer able to record from 2nd card with concurrent recording

[bib1963]

Grabbed the latest git master.

2 cards, first Sat - PCI, 2nd T2 - USB.

If I set a recording it get scheduled on the Sat card as expected. If I then set a recording to happen at the same time, it should record as normal on the T". It doesn't. It says there is a conflict.

This is with a minimal setup change from the defaults.

[Klaas de Waal]

Assuming you have done the following:

• For your DVB-S/S2 tuner card you have created a video source and you have done a channel scan. This results in a collection of channels that you can receive with the DVB-S/S2 tuner card.
• For your DVB-T2/USB tuner card you have created a second video source and you have done also a channel scan. This results in a new/different collection of channels that you can only receive with the DVB-T2/USB tuner card.

In the Program Guide you see all channels combined but you cannot see which channel is from which video source, unless you can infer this from the channel number or the channel name.

If you want to record two programs at the same time but both programs are on channels of the same video source then you will get a conflict. This is correct.

If you want to record two programs at the same time, one from the DVB-S/S2 tuner card and one from the DVB-T2/USB tuner card, then this will work.

[bib1963]

Yes... I know... I am capable of setting it up properly.

Your last sentence, basically explained what I was doing, but could not.

I reset everything, along with a DVB-T card, so I had S, T & T2. Concurrent recordings on S & T failed as above.

Anyway. seems that if mod_sys in dtv_multiplex is set to UNDEFINED, then this will stop concurrent recordings onto that card.

When I set the the T card to "DVB-T", it correctly allowed the recordings.

[Klaas de Waal]

Comment#2 indicates that the problem has been solved by configuring column mod_sys in table dtv_multiplex to a correct value, DVB-T, instead of UNDEFINED. This ticket is now closed. If the problem appears again then please re-open this ticket or create a new ticket.