<div class="gmail_quote">On Tue, Mar 20, 2012 at 11:42 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/20/2012 09:00 AM, lists.md301 wrote:<br>
> So yes, for anyone searching the archive, 4-digit channel tuning does<br>
> work with the Prime, there is just a printf issue in the backend<br>
> logging reporting the channel tune number. I'm assuming the 4-digit<br>
> channel changes is still an outstanding issue with various STB's.<br>
<br>
</div>I'm assuming you reported the location of the logging error so we can<br>
just fix it (as that's something we could even do before 0.25 release)?<br>
<br></blockquote></div><br>No, not yet, both because of my above embarrassment and not getting any feedback on the list with guidance on that. I'd be happy to, though. Note that in both cases below, the channel identified as "5225" should more correctly be "51225". Here' s what I'm seeing in my backend log, tuning to BBCAHD on channel 1225, with just the default general,important options:<br>
<br>2012-03-19 19:33:12.199 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>2012-03-19 19:33:12.292 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>2012-03-19 19:33:12.524 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>
2012-03-19 19:33:12.539 Finished recording Top Gear: channel 5225<br>2012-03-19 19:33:12.556 LoadFromScheduler(): Error, called from backend.<br>2012-03-19 19:33:12.579 AutoExpire: CalcParams(): Max required Free Space: 5.0 GB w/freq: 14 min<br>
2012-03-19 19:33:12.606 Finished recording Top Gear: channel 5225<br>2012-03-19 19:33:12.682 MainServer::ANN Playback<br>2012-03-19 19:33:12.690 adding: tivo1 as a client (events: 0)<br>2012-03-19 19:33:12.700 MainServer::HandleAnnounce FileTransfer<br>
2012-03-19 19:33:12.708 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>2012-03-19 19:33:12.709 adding: tivo1 as a remote file transfer<br>2012-03-19 19:33:13.107 MainServer: HandleRemoteEncoder(cmd GET_STATE) Unknown encoder: 1<br>
2012-03-19 19:33:14.279 RecBase(8:8): GetKeyframePositions(19,9223372036854775807,#1) out of 2<br>2012-03-19 19:33:14.305 RecBase(8:8): GetKeyframePositions(19,9223372036854775807,#1) out of 2<br>2012-03-19 19:33:15.482 MainServer: HandleRemoteEncoder(cmd GET_STATE) Unknown encoder: 1<br>
2012-03-19 19:34:02.347 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>2012-03-19 19:34:02.357 TVRec(8): HW Tuner: 8->8<br>2012-03-19 19:34:02.371 LoadFromScheduler(): Error, called from backend.<br>
2012-03-19 19:34:02.392 AutoExpire: CalcParams(): Max required Free Space: 5.0 GB w/freq: 14 min<br>2012-03-19 19:34:02.495 Finished recording Top Gear: channel 5225<br>2012-03-19 19:34:02.848 HDHRSH(192.168.1.6-0) Error: UpdateFilters called in wrong tune mode<br>
<br>Looking further (because of your request), from the (remote) frontend log of this LiveTV session, I notice that the naming of the ringbuffer mpeg file name is also incorrect, so the issue goes deeper than logging. This may make a "fix" more complicated (since it's not just a logging issue), but I'll leave it to the developers to decide:<br>
<br>2012-03-19 19:34:07.950 AFD: Resetting byte context eof (livetv 1 was eof 0)<br>2012-03-19 19:34:19.710 RingBuf(myth://<a href="http://192.168.1.253:6543/5225_20120319193419.mpg">192.168.1.253:6543/5225_20120319193419.mpg</a>) Warning: Not starting read ahead thread, already running<br>
2012-03-19 19:34:20.120 Player(a): Forcing decode extra audio option on (Video method requires it).<br>2012-03-19 19:34:20.433 RingBuf(myth://<a href="http://192.168.1.253:6543/5225_20120319193419.mpg">192.168.1.253:6543/5225_20120319193419.mpg</a>): Waited 0.2 seconds for data to become available... 28108 < 32768<br>
2012-03-19 19:34:20.481 AFD: Opened codec 0xa29fc50, id(MPEG2VIDEO) type(Video)<br><br>If you'd like me to repeat this with more detailed logging and/or open a ticket, I'm certainly willing. It would be my first, but I'll figure it out.<br>
<br>