Dear Sirs,

I am from Karachi, Pakistan and after the release of Bahrain Servers on AWS. It is requested to the Twitch team to release Bahrain CDNs for Twitch too so that the Middle Eastern countries can stream on low latency with better performance as the nearest servers for Middle eastern countries are Europe: UK, London and Asia: Singapore for Content Delivery.

There arent any servers in between, but as AWS has already established Bahrain servers 2 years ago, it is requested to you all to do the same so that new content creators from this region can rise up for your platform.

Thanks.

I find myself becoming ineffective as a Mod when my buffer slips to 20 and 30 seconds long. Any time the stream from the channels I mod gets laggy I find myself seriously behind Real Time. While reloading the page can help with this, every time I do I miss large chunks of stream time, possibly missing relevant contextual information for knowing when to Allow or Override the AutoMod. (When AutoMod catches the message "Oh look, its Captain D i c k!" it's relevant for me to quickly know that a man named D i c k was just introduced on-stream.) (Edit: Really? As if to prove my point that context is important, I had to edit this name in order to not have it censored in this message)

I can understand that an option like this can make the stream choppier, and that you may be hesitant to open an option like this to the general userbase, but for someone who is "working" its worth the compromise.

Guys during livestreams there are often bandwidth issues, so basically you have to accept really ****** quality & interrupts to stay live. For some events though I totally would not mind being 10 minute delayed or so in order to have the stream preloaded and available in good quality and sacrificing real time. Such a feature would be great. Also when rewatching videos - the download should continue when the pause button is pressed or should not reload when you jump back in time - it is a pitty that you can't really watch high quality videos, because the player does not utilize local storage efficiently...

Hi Twitch!

I'm certain y'all know about this problem already, but I wanted to tack on some details in case it might help along with solutioning.

Since COVID-19, DJs all flocked to streaming, many of them on Twitch. Low Latency Mode is creating jarring pitch bends that most DJs nor their listeners know about. Savvy listeners think the DJ is just doing a bad job. Even non-savvy listeners can tell something's not right. But DJ's have no idea that this is happening; even if they enable past broadcasts, their VOD won't have this problem. When listeners point this problem out, DJs often have no idea what the listeners are talking about.

I'm sure you know the cause but I'll elaborate for everyone's sake.

Low Latency Mode, if I understand correctly, tries to catch up viewers who've fallen behind (e.g. due to a temporary blip in their Internet), to the latest point in the stream, by ever-so-slightly increasing the speed of playback. This doesn't matter too much for speech: people notice a change, but it doesn't affect their understanding. It also doesn't matter too much for video game music: people notice a change, but it's the ambience / energy that matters, not so much the pitch.

When it comes to music performance though, it can be a big deal, particularly for DJ streams, which have exploded since the virus outbreak. DJs aim to provide a smooth, uninterrupted feel over extended periods of time. But low latency mode disrupts the vibe and even makes people stop dancing. Look, I know how annoying musicians can be, but I'm not exaggerating: I've been in Zoom dance parties or hanging with a few friends where even non-musical ones stop dancing and feel something "off" has happened.

Even non-trained ears can hear pitch differences with surprising accuracy. I can make a recommendation that would make the pitch difference much more tolerable.

By my ears, the pitch shift I hear is around around 50 cents (i.e. about a quarter tone) for music playing at 123 bpm. I suspect the catch-up speed factor actually varies, but I don't know your algorithm. Anyway, centered around 123 bpm (since pitch is logarithmic), each 1 bpm up shifts pitch ~14 cents. So for me to hearing 50 cents, your algo must be pushing 123 bpm to 126-127 bpm. In other words, low latency mode is increasing speed by as much as 3%. It's understandable that 3% sounded totally acceptable from a general playback product perspective that wasn't geared toward DJs. But, this probably has to be reviewed if you want to continue supporting DJ streams. (Which, if you don't care, that's fair :-)

So what if we take a practical approach. "Instrument Timbres and Pitch Estimation in Polyphonic Music," Loeffler, B. D. (2006) says that the smallest pitch difference human ears can detect is 6 cents. But it's not like you have to fool professional musicians. I'm sure even lowering the shift from 50 to 15 cents will make a world of difference. To do so, you have to cap the speed increases to +1% at most.

So:

1. Is it viable to cap low latency mode's speed increases at +1%?


2. If no, is it viable to do so just for Music & Performance Arts channels?


3. If no, is it viable to make it an opt-in setting for the broadcaster?


4. Or maybe some compromise where, when the user's not too far behind it caps, but when they are, it does whatever it does today?

I trust y'all to make the right call. I also trust that you may have bigger fish to fry.

Appreciate all your work and wishing the best to everyone there.

It's been a few weeks since Twitch changed how stream quality auto changes based on whether the tab is in the current tab/window or not. This change automatically lowers the quality of streams to 480p (or lower) for streams not in the current tab, and when the stream is tabbed back into focus it does not always resume the originally selected quality.

This is affecting multiple browsers, with or without extensions, so this is seems very much a Twitch end feature to lower data use.
This change however has resulted in some issues:
-More buffering
-Streams hanging/pausing when tabbed out
-Quality not restoring when tabbed back
-Playback issues such as audio desync when the stream quality changes and latency has to catch up
-Streams in background no longer has thumbnail view in task view (windows key + tab) to simultaneously view multiple streams and is instead just a black screen video player.

Overall I feel like the changes have not improved the user experience and has instead introduced more issues than it saves. It should be up to the user to open as many streams as they wish at whichever quality and maintain such experience regardless of window focus.