(my most recent prior post:
http://forum.kodi.tv/showthread.php?tid=...pid2308624)
Pursuant to post
http://forum.kodi.tv/showthread.php?tid=...pid2308588
I first checked for an update, none was reported (I assume the 2016.4.12 just hadn't propagated, I did not force-refresh the repository locally). Before my next post here I will update to 2016.4.12.
I performed the suggested edit to main.py in 2016.4.11, and it resolved the issue with regard to stuttering and performance to a degree, strictly according to bitrate settings. I invoked "always ask" and went through the settings to locate the most stable stream.
First, in live Pirates game available now, no 5400bps stream was available. Playback stabilized at 1200bps. All of the streams rendered at 29.970 fps.
Details follow:
3500bps: stream loads and immediately stutters, 1280x720. In framerate overlay, value 'vq' instantiates at 10% and drops to zero. the last line of the overlay is labeled "W" and contains a value 'cpu'; when 'vq' is at 10% or less this value climbs rapidly and fluctuates between 80% and 103%. Playback never improves.
2500bps: stream loads and immediately stutters, 960x540. In framerate overlay, value 'vq' instantiates at 10% and drops to zero. the last line of the overlay is labeled "W" and contains a value 'cpu'; when 'vq' is at 10% or less this value climbs rapidly and fluctuates between 80% and 103%. Playback never improves.
1800bps: stream loads and begins to fail at 2:24 of playback time, 896x504. In framerate overlay, value 'vq' instantiates at approximately 50% and holds steady until just after 2:15, when it drops to zero. the last line of the overlay is labeled "W" and contains a value 'cpu'; when 'vq' is at 10% or less this value climbs rapidly and fluctuates between 80% and 103%. After the 2.5 minute mark, occasionally a "buffering" notice appears top right but playback never improves.
NB: this setting appears to most closely approximate the prior settings that were successful under mlbmc on my rig last season; as noted previously, early in the year playback was problematic in a similar manner but resolved by increasing some sort of cache or buffer setting - my next research task is to locate what I did and share that here. I am aware of the ongoing discussion in this thread which seems to suggest that local temp file management is not applicable to this year's streams.
1200bps: stream loads and does not appear to fail in relatively short under five minute tests, 640x360. In framerate overlay, value 'vq' instantiates at approximately 100% and holds steady. 'cpu' holds steady at 0%. This is perfectly acceptable but definitely lower resolution than average resolution obtained via in-browser playback on mlb.tv. The primary advantage to this stream is avoidance of the slipstream video ads presented on mlb.tv.
Physical display is a 42" Sony LED at 1080p.
Thanks again for all your hard work, I hope this is of value.
(UPDATE: found the video cache thing.
http://forum.kodi.tv/showthread.php?tid=...pid1980365
tl;dr: I used advancedsettings.xml to increase the xmbc-wide video cache setting to 300mb. will investigate to see if kodi kept that setting at install and so forth.
UPDATE 2: advancedsettings.xml came over properly. doubled it to 600mb.)