slyguy.addons

slyguy.addons copied to clipboard

Kodi 19.1 Log: https://pastebin.com/raw/68mZWwjQ

Any findings with this one Matt?

@scottydulton could you please try latest version of the Binge add-on (0.3.4) and see if that is fixed?

Will try soon and get back to you mate thanks.

Hey @matthuisman, Still no good, froze after 5 or so minutes. ive enabled debug logging and got a fresh full log from today for you.

https://pastebin.pl/view/ba606a93

can you please update to latest versions (just pushed) then enable logging > component > curl then get mew a new log :)

Sorry mate been working I will get it done tonight for you

Hey @matthuisman it froze again but this time after about 30-40 mins, the log was just too big for pastebin and i wasnt sure what to remove so i just added a zip file lol kodi.zip l

Oh... So maybe it's now fixed? Can you keep trying? It was always 5mins on the dot previously?

nah for me most of the time was sooner rather then later, but sometimes i would get half hour out of it, i tried twice today, froze both times around 30 i can do some more tonight if u like wont be till later on though

@matthuisman tryed myself 3 times, froze within 5-10 mins each time

Hey @matthuisman i replicated this issue on kodi - windows 10, turns out it is seeing im using the max number of streams.

ERROR : CCurlFile::Open failed with code 403 for http://127.0.0.1:52103/plugin://slyguy.binge/?_=license_request: {"code":130401,"message":"Too many concurrent streams."} 2021-09-26 11:20:15.118 T:10804 ERROR : AddOnLog: inputstream.adaptive: License server returned failure

I have my account setup to 3 kodis at my house however they arent all watching at the same time, my plan allows 2 screens

oh right - that makes sense now, I was wondering why i could not replicate, I'll see what I can do about that :)

Hopefully something simple :)

@matthuisman did you find anything regarding this?

not really. does their app work if your streaming on X amount of other devices?

@matthuisman I have a binge account that allows 2 screens that I share with a sister and parents. We have all had this freezing issue for a while and doubt if we were all using binge concurrently. To verify I created a trial using my wifes details and set it up as a 2 screens account, but only playing it on 1 screen and it still produces the same result, within about an hour each time it froze, I experienced zero buffering up to the point it froze..this on a 4k firestick using kodi 19.1

@matthuisman yeh it does mate, ive tested on multiple screens in web browser/phone, however theres no official App compatible for firestick yet

could you guys try this build of Inputstream Adaptive and see if it helps / fixes inputstream.adaptive-19.0.0.1.zip

@matthuisman will try now, i was going to say too i feel like it hasnt done this forever, i feel like it was around the time of the issue with NBA no sound and all the changes to IA regarding HLS, but i could be 100% wrong

@matthuisman thanks ill try tonight

@matthuisman still failed mate

oh, thats good i guess as that PR i removed in the test did fix other stuff

Yeah mine failed too

@matthuisman ok so loaded kodi onto a nvidea shield and a samsung mobile.. put binge on both and had same issue as with my firestick. They didn't freeze at the same time but all froze between 5 and 45 mins of each other. Could it be an Android thing as opposed to a firestick thing?

@matthuisman just realised i also use your Kayo addon and both license requests are through streamotion, i dont have this issue with kayo on the same devices, just thought i would point that out maybe might help with diagnosis between the 2

@scottydulton I think now that Kayo is using the same DRM / endpoints - these are the same issue https://github.com/matthuisman/slyguy.addons/issues/402 https://github.com/xbmc/inputstream.adaptive/issues/1147

Gday mate Kayo Freezing again

cheers

not related sorry if you think its the addon - upload a full kodi debug log please

Ok cheers mate do I upload it here?

yup. if your using a shared login etc, then you will simply be hitting the concurrent stream limit