[Smokey's Utilities] Maintain HD Quality option causes auto-play issues about add-ons HOT 11 OPEN

Gonna @smokey019 for this one

from add-ons.

what browser do you use? and do you have other extensions enabled for twitch? ie: auto point/drop claimer for twitch etc

from add-ons.

what browser do you use? and do you have other extensions enabled for twitch? ie: auto point/drop claimer for twitch etc

Vivaldi, which is on Chrome engine. PC. I also use BTTV, which indeed has auto points and drop claimer built-in.

from add-ons.

what browser do you use? and do you have other extensions enabled for twitch? ie: auto point/drop claimer for twitch etc

Vivaldi, which is on Chrome engine. PC. I also use BTTV, which indeed has auto points and drop claimer built-in.

gotcha i can replicate this. i can look into finding a solution soon ™️

from add-ons.

Any news on this one?
I have also noticed the same issue happens when you have an offline channel page open and then the stream starts - if the tab is not active, the player will stuck in the same black buffering state until you pause and un-pause it.
Also, when it's in this black screen state from any cause, changing the video quality doesn't fix it, even though normally it would refresh the stream i.e. standart buffering or delay would get fixed.

from add-ons.

still trying to find a fix

from add-ons.

Update 1.2.1 unfortunately does not seem to have fixed this issue.

from add-ons.

Still an issue to this day. Updated the opening message to include another auto-play issue that I mentioned some time ago.

from add-ons.

as far as i know, there's no way to fix this for now

from add-ons.

as far as i know, there's no way to fix this for now

Since this only broke after specific commit, is it possible to revert the changes or re-implement parts of the older code?

from add-ons.

as far as i know, there's no way to fix this for now

Since this only broke after specific commit, is it possible to revert the changes or re-implement parts of the older code?

it didn't break after a specific commit. i tried a couple different things to get it to work and nothing seemed to actually make it work.

if you open a new browser after it crashes, it won't have this issue when you ask it to re-open tabs. but it only happens when you start a fresh browser. so it's likely something to do with the browser and not necessarily the code.

commanderroot's script also has this same issue, so there's likely nothing we can do about it. again, at least as far as i know.

the code is open source, so feel free to commit changes if you happen to find out what is causing it :)

from add-ons.