![]() The ts urls define a set of video sources in different resolutions and frame rates. Just my 2 cents from my own observation and debugging the userscript / using the chrome/brave developer tools :)īut there is more complexity in the script and the stream chunk stitching process i think, so this is only a partial understanding of things which I have, i guess. Not sure how midroll ads are being handled tho. Instead of that 30sec dummy ad.īecause after when the 30s are elapsed, the stream would continue normally (last time i tested) even with vaft enabled. It seems (i can only guess now) that the previous approach of retrieving a lower res alternative player source like embed, proxy or thunderdome player types doesnt work out of the box any more because the according m3u8s contained "real" stream chunk data. I am assuming now that in order to skip the 30s of purple screen video chunks you might need to add up some timestamps and durations and "tell" the worker (which in fact is already executing parts of the user script) to move the play head beyond those duration or chunks which contain those "standard-ad" info. You can also see durations and sequence numbers inside those M3U8s. Shortly after start watching a stream for about ~30 seconds there we have some "standard-ad" info if the blocker is active (and real ad urls if the blocker is inactive) and i guess the the server "weaves" or "stitches" ads retrieved from those sources into the ts chunks so you cannot effectively intercept those by mere DNS since its all via the same domain / url. Looking inside those m3u8 responses, the hostnames of those transport stream (ts) urls contain "video-weaver", and inside the m3u8 there are some infos about "stitched" ads, triggers and whatnot. Obfuscation is the keyword here, and it makes understanding whats going on there very hard to nearly impossible. Unfortunately those are minified and assembled versions, so just pretty printing them wouldnt yield useful variable names and stuff like that. You can see some banner / log message in the console denoting it as "Amazon IVS version 1.15" or something along the lines. I think this wasm binary is the actual video player. Just by looking into chromes developer tools, it seems that there is a js service worker and a wasm worker doing a sequence of requests to cryptically-long named m3u8 urls. You have to keep in mind that those changes not roll out at the same time everywhere in the world and that just like last time when a Twitch team was actively battling ad blocking they very frequently do releases and just within few hours the behavior of ad blocking might change. This is probably because to do with the playertype currently being used by vaft and changes to that type by the Twitch team as mentioned above.Įdit: Mid-rolls can currently not be blocked via TTV LOL as I just saw in an ad heavy real stream. This test stream always gives you pre-roll ads and I could verify the behavior mentioned above with it: If you only use vaft you will currently get the "commercial break in progress" sign as OP provided. It doesn't matter that you have both vaft and TTV LOL installed as the latter one just has priority over the script apparently. It's very easy to verify that pre-roll ads are actually still successfully blocked (at least in my country) via TTV LOL. Firefox Developer Edition (Permanent): Go to about:config > Set to false > Extensions page > Gear > Install Add-on From FileĬontributions are welcome! Please read the contributing guidelines.After having issues with vaft as described in this post I added TTV LOL with vaft and the issue went away, at least for me anyway.Firefox all editions (Temporary): Go to about:debugging#/runtime/this-firefox > Load Temporary Add-on.Chrome (Permanent): Unzip > Go to chrome://extensions > Enable developer mode > Load unpacked.Manual installationĭownload the version for your browser under the "Assets" section of the latest release. ![]() Firefox Add-onsĭownload the extension from Firefox Add-ons. Chrome Web Storeĭownload the extension from the Chrome Web Store. ![]() Please clear your browser's cache after installing the extension. uBlock Origin is recommended as it is a general-purpose ad blocker. ⚠️ Please remove any other Twitch-specific ad blocker (this includes the VAFT script). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |