A possible solution to this may be to have a special case for LiveTV for the backend to communicate to the frontend how fast to read. This way the frontend can start reading right after the backend's first or second write and never attempt to read too much to cause a prebuffer pause.
<br><br>- Mark.<br><br><div><span class="gmail_quote">On 7/12/07, <b class="gmail_sendername">migmog</b> <<a href="mailto:migmog@gmail.com">migmog@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 12/07/07, Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br>> Your patch didn't come through. Please resend.<br>><br>> (And, writing that patch is the best way for you to answer your own
<br>> questions. Then, you can explain to others why Myth is "so slow.")<br>><br>> Mike<br><br>Erez, thank you for your analysis.<br><br>Please forgive Michael's terseness. You may not be aware that this
<br>issue of slow channel changing has been discussed at length before,<br>and nobody has yet come up with an explanation or a solution.<br><br>From your messages, it looks like you may be the person with the<br>skills and the motivation to do something about it!
<br><br>If you did, I for one would be MOST grateful.<br><br>Andrew<br>_______________________________________________<br>mythtv-dev mailing list<br><a href="mailto:mythtv-dev@mythtv.org">mythtv-dev@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br></blockquote></div><br>