Myth .23 tip (latest snapshot install)

[l3mce]

I have an HDHomeRun (HDHR t1 us), and this device only has one usable tuner, though LMCE detects 2. I presume the second is some sort of fake to allow recording one thing and watching another. I have a couple of crap cards that do the same thing, though I know there is only one usable tuner. Snapshot 22982 (or later) with the MythTV .23 shoehorn prioritizes the fake tuner and will not access the correct one before crashing. Deleting the tuners and redefining the single usable tuner gets overwritten as soon as the changes are applied (presumably after mythfilldatabase is run).

In order to prevent this, or more accurately allow your changes in MythTV Setup to be applied and not overwritten, in the web admin drop to device tree/Core/DCERouter/Myth TV Plugin. Towards the bottom of the page is a checkbox which says "Dont autoconfigure"

Then delete all, define card/input, and when it says mythtv is ready... it is. I am sure many of you are already aware of that checkbox... but it cost me almost 2 days... so naturally I think it's discovery is like finding Atlantis. Hope this helps someone having troubles.

[totallymaxed]

I have an HDHomeRun (HDHR t1 us), and this device only has one usable tuner, though LinuxMCE detects 2. I presume the second is some sort of fake to allow recording one thing and watching another. I have a couple of crap cards that do the same thing, though I know there is only one usable tuner. Snapshot 22982 (or later) with the MythTV .23 shoehorn prioritizes the fake tuner and will not access the correct one before crashing. Deleting the tuners and redefining the single usable tuner gets overwritten as soon as the changes are applied (presumably after mythfilldatabase is run).

In order to prevent this, or more accurately allow your changes in MythTV Setup to be applied and not overwritten, in the web admin drop to device tree/Core/DCERouter/Myth TV Plugin. Towards the bottom of the page is a checkbox which says "Dont autoconfigure"

Then delete all, define card/input, and when it says mythtv is ready... it is. I am sure many of you are already aware of that checkbox... but it cost me almost 2 days... so naturally I think it's discovery is like finding Atlantis. Hope this helps someone having troubles.

I use an HDHR DVB-T version here in the UK and apart from different firmware the hardware is the same. Unless I am misunderstanding you (if i am sorry!) you are not saying that your 2nd Tuner has a hardware fault. This would imply that the PnP script for the HDHR is not quite configuring it correctly...so you should report that if thats the case. Alternatively what you could do is manually setup the 2nd tuner using mythtv-setup at the Core. It sounds like you 2nd tuner has not had a source mapped to it correctly as both tuners should be usable in an HDHR...if your not using multi-rec then having two tuners allows you to record/watch two TV channels simultaneously. If you are using multi-rec then you can record/watch up to 5 channels on each Tuner (these settings can be configured in mythtv-setup)

All the best


Andrew

[l3mce]

The device manufacturer claims it to have a single tuner.
http://www.silicondust.com/products/hdhomerun_t1_atsc
LMCE finds a second tuner. That second tuner is not capable of grabbing signal, as it is not a valid tuner. Whatever it is that LMCE/Myth and even the SiliconDust winblows software finds and calls tuner 1, it also finds on other single tuner cards. I don't really understand the hardware at all which I am sure would reveal the nature of this phantom tuner. The only difference between all of these in myth, is that the snapshots which include myth .23, prioritizes the tuner that does not exist, and without making that change, will not let you delete it.

Hope that is clearer.

[totallymaxed]

The device manufacturer claims it to have a single tuner.
http://www.silicondust.com/products/hdhomerun_t1_atsc
LinuxMCE finds a second tuner. That second tuner is not capable of grabbing signal, as it is not a valid tuner. Whatever it is that LinuxMCE/Myth and even the SiliconDust winblows software finds and calls tuner 1, it also finds on other single tuner cards. I don't really understand the hardware at all which I am sure would reveal the nature of this phantom tuner. The only difference between all of these in myth, is that the snapshots which include myth .23, prioritizes the tuner that does not exist, and without making that change, will not let you delete it.

Hope that is clearer.

OK I understand now. Yes Silicondust does have a single tuner variant of the HDHR. The fact the PnP scripts are detecting secondary tuners in both your HDHR and other single tuner cards would indicate the problem is in those scripts. Make sure you create a Trac ticket so that one of the Devs can pickup on this issue and fix it.

All the best


Andrew

[tschak909]

Yes, the HDHR pnp scripts right now do assume two tuners. Let's make a trac and see if we can figure out what variant these devices are, so we can fix the scripts.

-Thom