mythbuntu-bugs team mailing list archive

[DAP <538641@xxxxxxxxxxxxxxxxxx>]

Wow, 6 months.

In answer to your question, Yes & no.

My analog tuner driver is still broken. I have been unable to use it.

The scheduling problem no longer exists because I finally found the
documentation on scheduling, and untangled the mess I made of my setup.

The analog tuner is now last, so I can not use the option to avoid
conflicts with live TV since that would choose the analog tuner for live
TV, and when I attempt to use my analog tuner, myth front end crashes.

Btw, I am now using the daily build of 0.24.

I reported the analog tuner problem as bug #582523

You can probably close this bug (not the analog tuner bug, that one is
still relevant) since it is no longer relevant.

** Changed in: mythbuntu
       Status: Incomplete => New

-- 
Recording priority is broken
https://bugs.launchpad.net/bugs/538641
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New

Bug description:
Wrong tuner gets in scheduled recording list.
I have an ATI HD Wonder. I've never been able to get the analog portion to work, but I have it set up so that I can experiment with it. I have the digital portion working and I have it set up in the same tuner group so that the system won't try to record on both at the same time since there is only one physical tuner for both analog & digital.
A particular channel is available on both analog & digital.
I have three digital tuners that can receive this channel (the other two are HDHomeRuns)
There is a NCIS marathon on the date in question, there is nothing else on at the same time. This should be easily handled by two tuners
I set the analog tuner priority to -99 and the digital tuner priority to 0, the analog tuner shows up in the upcoming recordings list, but not the digital. For the specific event in question, I went and changed the channel priority for the specific channel on the analog channel to -99, and it still shows up in the recording list.
This is a cut & paste from Mythweb upcoming recordings:
 	HDHomeRun Cable0  	NCIS: Frame-Up  	42 - USA Network  	Sat Mar 20, 2010 (08:55 AM)  	1 hr 10 mins  	Don't Record  	Never Record
  	HDHomeRun Cable1 	NCIS: Hiatus 	42 - USA Network 	Sat Mar 20, 2010 (09:55 AM) 	1 hr 10 mins 	Don't Record 	Never Record
  	HDHomeRun Cable0 	NCIS: Hiatus 	42 - USA Network 	Sat Mar 20, 2010 (10:55 AM) 	1 hr 10 mins 	Don't Record 	Never Record
  	HDHomeRun Cable1 	NCIS: Shalom 	42 - USA Network 	Sat Mar 20, 2010 (11:55 AM) 	1 hr 10 mins 	Don't Record 	Never Record
  	ATI HD Blunder Analog 	NCIS 	42 - USA Network 	Sat Mar 20, 2010 (12:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	Conflict 	NCIS 	42 - USA Network 	Sat Mar 20, 2010 (01:55 PM) 	1 hr 10 mins 	Record This 	Never Record
  	HDHomeRun Cable0 	NCIS: Requiem 	42 - USA Network 	Sat Mar 20, 2010 (02:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	HDHomeRun Cable1 	NCIS: Chimera 	42 - USA Network 	Sat Mar 20, 2010 (03:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	ATI HD Blunder Analog 	NCIS 	42 - USA Network 	Sat Mar 20, 2010 (04:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	Conflict 	NCIS 	42 - USA Network 	Sat Mar 20, 2010 (05:55 PM) 	1 hr 10 mins 	Record This 	Never Record
  	HDHomeRun Cable0 	NCIS: Twilight 	42 - USA Network 	Sat Mar 20, 2010 (06:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	ATI HD Blunder Analog 	NCIS 	42 - USA Network 	Sat Mar 20, 2010 (07:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record
  	HDHomeRun Cable0 	NCIS: SWAK 	42 - USA Network 	Sat Mar 20, 2010 (08:55 PM) 	1 hr 10 mins 	Don't Record 	Never Record

As you can see, it should have been possible to handle with two tuners, but for some reason, after 4 successful events, it chooses the analog tuner which should have a priority of -198 over the ATI digital which has a priority of 0. Then it screws up even worse by claiming a conflict when there isn't one.

Mythfrontend version: trunk (23729)