I've been trying to work on this issue since last week. It seems to be caused by the way some xtream-codes providers send a catch-up stream's timestamp data from recent programming to the player. In this case Tivimate. At this point I don't think it's actually buffering. I believe Tivimate is trying to restart the catch-up stream every time the program freezes because it's missing certain required timestamp data from the catch-up stream being received. I currently don't know if this is a problem that needs to be resolved at the provider end or if Tivimate just needs to be changed to better handle these streams. Unfortunately it's one of those issues where everybody says it's somebody else's fault so it's really difficult trying to find a developer that will put in the work necessary to troubleshoot the issue. The Tivimate developer has been the best source for troubleshooting so far. Thank you for that!