Opened 3 years ago

Closed 3 years ago

#12779 closed Bug Report - General (Fixed)

Cannot create new input connections

Reported by: peter.bienstman@… Owned by:
Priority: critical Milestone: 0.28.1
Component: MythTV - General Version: 0.28.0
Severity: high Keywords:
Cc: Ticket locked: no

Description

One a system with a rotor, I can only create a single input connection to one of the satellites. There is no option to create a second input connection for a second satellite (i.e. second input source), as was the case in Mythbuntu 14.04.

As a workaround, I tried to add a dummy duplicate capture card, which did allow me to create a new input connection for a new satellite, but now when I wish to change to channel from a different satellite, I get complaints that I should cancel the recording currently in progress (there are none scheduled).

This is on a fresh Mythbuntu 16.04 install, but having had a succesfully running Mythbuntu 14.04 on that hardware before.

Change History (3)

comment:1 Changed 3 years ago by gigem

Status: newinfoneeded_new

Creating additional capture cards is the correct way to configure tuners in MythTV 0.28 when diseqc is involved. Be sure to also enable the "open on demand" option to prevent the tuner from being accessed more than once simultaneously. I apologize that the configuration is not as good as it should be right now. The goal is to move it to the backend web interface and/or a new settings framework. Consequently, not much effort has been put into updating the old, "to be obsoleted" settings code.

I don't understand your comment about "cancel the recording currently in progress". Is this in live TV? Anyway, please make sure the "open on demand" option is enbabled for all diseqc tuners and then try again. If it still doesn't work, please reply with more details about your configuration and the steps you took when the problem occurred.

comment:2 Changed 3 years ago by peter.bienstman@…

'Open on demand' seems to have done the trick.

Glad the configuration system is being reworked to make it more logical, it's rather labyrinthine at the moment :-)

comment:3 Changed 3 years ago by Stuart Auchterlonie

Milestone: unknown0.28.1
Resolution: Fixed
Status: infoneeded_newclosed

Resolving as the original reporter has indicated this is now working.

Note: See TracTickets for help on using tickets.