2012-11-14, 19:17
(2012-11-13, 05:14)janbar Wrote: @all
Release 0.5.0 and the new adjustment of buffer size: Since 0.5.0 the buffer size has no fixed size to avoid stop show from backend.
When the tune of channel is bad sometime mythtv skip lot of frames. Because we requested to much before the backend stopped all (it is a rule in mythtv), we have limited the buffer size in these critical situations. But when situation become normal the buffer size is enlarged.like before.
The algorythm could be reviewed if you have to many problems with that. Let me know.
I done lot of test using a network over power line (4~5 Mbytes max (model 200Mb) ) and HD stream run well (1080i) but if you have other network traffic that would break the stream because HD stream need 4.5MBytes.
So prefer gigabyte network for HD stream.
br
Thanks for the explanation janbar, and for all your hard work.
1080i playback has never been an issue on my network, and still is not with tvheadend or earlier myth revisions. Requiring a gigabit connection for what should be a fairly low bandwidth stream seems excessive. Is it possible the new algorithm is too aggressive in reducing the buffer size, or is starving the buffer unnecessarily?
Are there a specific set of commits I can look at? I'm assuming the fixes marked "Protocol Improvements" would be a good place to start.