2014-03-18, 16:05
(2014-03-18, 13:07)learningit Wrote: I guess I'm not being clear with what I'm saying here. Regardless of the other bug(s) and their solutions, the player is ignoring the 'live' parameter when it is set and being specifically told not to seek - even if the player seeks perfectly. There are times when you know that you don't want it to seek and choose to tell the player that through the 'live' parameter. I guess that it may also be a temp fix for other problems, but in and of itself it is also a problem which is different from the other problems previously reported.I agree, we have two bugs here, not one. Fixing either one would prevent a total freeze that requires force quitting XBMC (not easy on some platforms) when accidentally pressing the seek button during a live stream. From an end user perspective a major usability issue where it doesn't really matter which contributing bug is fixed first. It seems cleaner to me (and probably easier) that seeking should simply be disabled by honouring live=1 when a live stream is detected.
If devs want to pursue a fix for the other bug (eg why does the player hang/deadlock/freeze when it tries to seek an un-seekable stream) then its easy enough to revert the first fix temporarily in a test build so that live=1 is ignored again and the player bug can be investigated further. Why make end users suffer for so long (this problem has been there seemingly forever) just so the harder more challenging bug can be fixed before the easier one ? Doesn't make sense.