Mailing List Archive: MythTV: Dev

Re: [mythtv-commits] mythtv commit: r22016 by ijr

Index | Next | Previous | View Threaded

nigel at ind

Sep 24, 2009, 1:41 AM

Post #1 of 2 (513 views)
Permalink

Re: [mythtv-commits] mythtv commit: r22016 by ijr

> Log:
> Hokey fix to make newer hdhomerun firmware revisions work. Retry
> tuning with "qam:<freq>" if "qam_256:<freq>" or "qam_64:<freq>"
> failed.

I'm curious what tune sequence was failing.
Do you have -v channel,record output?

(I hoped [21389] would have caught all the bad modulation
strings, but maybe something later, like UpdateFilters(),
was still using the bad value?)

--
Nigel Pearson |"I haven't tested it yet, |
nigel [at] ind | but it should be perfectly safe." |
Telstra, Sydney, Australia |"Just a bit of harmless brain |
9202 3900, fax 9212 6348 | manipulation, that's all" - Wallace|

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

ijr at case

Sep 25, 2009, 7:53 AM

Post #2 of 2 (441 views)
Permalink

Re: [mythtv-commits] mythtv commit: r22016 by ijr [In reply to]

On Thursday 24 September 2009 4:41:33 am Nigel Pearson wrote:
> > Log:
> > Hokey fix to make newer hdhomerun firmware revisions work. Retry
> > tuning with "qam:<freq>" if "qam_256:<freq>" or "qam_64:<freq>"
> > failed.
>
> I'm curious what tune sequence was failing.
> Do you have -v channel,record output?
>
>
>
> (I hoped [21389] would have caught all the bad modulation
> strings, but maybe something later, like UpdateFilters(),
> was still using the bad value?)

I didn't debug too much, really - it just wasn't tuning, and changing things
to 'qam' fixed it. No logs at the moment.

Isaac
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads