Opened 6 years ago
Closed 6 years ago
Last modified 6 years ago
#13139 closed Bug Report - General (fixed)
hdhomerun second tuner not configured correctly in 0.29
Reported by: | Owned by: | Peter Bennett | |
---|---|---|---|
Priority: | minor | Milestone: | 29.1 |
Component: | MythTV - Mythtv-setup | Version: | v29-fixes |
Severity: | medium | Keywords: | HDHomeRun 0.29 tuner |
Cc: | Ticket locked: | no |
Description
I'm running mythtv backend 29.0+fixes.20170929 from the mythbuntu repo on ubuntu 16.04
Trying to configure an HDHomerun Extend in mythtv-setup. I can add the first tuner without problem using either [deviceID]-0 or [IPaddress]-0. The string is parsed correctly and the setup page shows the correct IP and tuner number 0.
When I try to add the second tuner, using either [deviceID]-1 or [IPaddress]-1, the setup page initially displays the correct IP and tuner number 1. However, when I save the capture card, then re-edit that card, the tuner number has changed to 0 (the IP address is still correct). In MythWeb, only the first encoder is shown or used, I'm guessing that's because there's a conflict with both cards having the same address and tuner number?
Both capture cards are in the DB and both rows seem to have correct info with different cardid, videodevice, and displayname fields. I don't see a tuner number field, so I assume it is being parsed from the '-#' part of videodevice, but that is failing at some point.
Change History (8)
comment:1 Changed 6 years ago by
Component: | MythTV - General → MythTV - Mythtv-setup |
---|---|
Owner: | set to Peter Bennett |
Status: | new → assigned |
comment:2 Changed 6 years ago by
comment:3 Changed 6 years ago by
You are correct, the backend was not getting restarted. I was re-running mythtv-setup and answering yes to stopping the backend and yes to re-starting on exit, but I didn't have the backend start / stop command configured correctly, so I was not actually restarting the backend. Once I restarted, the backend both tuners appear in mythweb.
So, the only remaining issue is the small interface glitch of id-1 showing a tuner number of 0.
Thanks for looking into this.
comment:4 Changed 6 years ago by
There are actually multiple things wrong with the new HDHomerun setup. After comparing with the old version, the following are problems that exist with the new setup.
- When an existing capture card is selected, Available devices shows "Manually enter". It should show the selected id.
- When an existing capture card is selected the currently selected shows "warning already in use". It should only show that if it is in use on another tuner.
- Device id must always be read-only. currently it is always updateable.
- When "manually enter ip address" is selected, IP address and tuner should be updateable. They are not.
- When updating ip address or tuner, the device id should be changed to match what is entered.
- When editing an existing tuner, the tuner id shows as 0. It should show the correct value.
comment:5 Changed 6 years ago by
Milestone: | needs_triage → 29.1 |
---|---|
Status: | assigned → accepted |
comment:6 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
comment:8 Changed 6 years ago by
Owner: | changed from Peter Bennett to Peter Bennett |
---|
I agree the tuner number is not displaying correctly when going back into setup after adding the second tuner, but I am seeing both tuners in MythWeb. Did you restart the backend after adding the second tuner. After adding both, then going back into them and making a change (turning off EIT), and saving, the mythweb display is as below, after restarting the backend.
I will look into fixing the display of tuner number in the setup, but it does not seem to be causing any operational problems.
I tested with an HD Homerun Prime, which should work the same as your HD Homerun Extend, on master, which should be the same as v29 for this.