Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitrate difference #207

Open
CristianGrecu opened this issue Feb 21, 2024 · 11 comments
Open

Bitrate difference #207

CristianGrecu opened this issue Feb 21, 2024 · 11 comments
Assignees
Labels
API issue third party app can only access the provided api, sometimes those api stop working or change bug Something isn't working Resolved

Comments

@CristianGrecu
Copy link

CristianGrecu commented Feb 21, 2024

Hello, I am not 100% sure this is a real problem, so I apologise if this is a waste of time. I've recently noticed that the bitrate that the top right stats panel shows is way lower than normal. Streams that used to show 9 Mbps now show 4-5. A lot of streams seem to be at even lower values like 3 Mbps. Only a few IRL streams show normal values like 7 Mbps. I checked on a PC using Chrome and the bitrates are much higher as expected. I'm not sure if there is an actual difference in image quality because the displays that I use are so different vs a large TV.

I am not a software developer so I have no idea if Twitch started messing with some codecs implementing the AV1 support, or if there's anything wrong to begin with.

Thank you in advance!!

@fgl27
Copy link
Owner

fgl27 commented Feb 21, 2024

Is a Twitch bug, they are providing the wrong bitrate for lives

If you go to the VOD of the same Live you can see the proper value

I expect them to fix this but technically they may not, so I will have to come up with a workaround as this messes up the auto playback that is bitrate base as it depends on analysing the internet available bandwidth vs bitrate to determinate what quality to pick.

@fgl27 fgl27 self-assigned this Feb 21, 2024
@fgl27 fgl27 added bug Something isn't working API issue third party app can only access the provided api, sometimes those api stop working or change labels Feb 21, 2024
fgl27 added a commit that referenced this issue Feb 21, 2024
partial solve #207

We need to comeback and improve or remove this in the future
@fgl27
Copy link
Owner

fgl27 commented Feb 21, 2024

The above fixes it for now, I will let this open so I can improve in the future

the above was pushed to the app just close and reopen it so the app update it self

@fgl27 fgl27 added the Resolved label Feb 21, 2024
@fgl27
Copy link
Owner

fgl27 commented Feb 21, 2024

if any other related issue is found let me know here

@CristianGrecu
Copy link
Author

Thank you!

@RikuXan
Copy link

RikuXan commented Mar 3, 2024

Just to clarify: the bitrate is still displayed incorrectly, just the choice of quality logic has been fixed, correct?

@fgl27
Copy link
Owner

fgl27 commented Mar 4, 2024

Just to clarify: the bitrate is still displayed incorrectly, just the choice of quality logic has been fixed, correct?

the bitrate of affected streams for the source stream is approximated but that isn't incorrect.

@RikuXan
Copy link

RikuXan commented Mar 4, 2024

Ah sorry. I had a few streams where the displayed bitrate was still surprisingly low.
But if there is no accurate information given out by Twitch anymore an approximation is all you can do.

@fgl27
Copy link
Owner

fgl27 commented Mar 4, 2024

For now yes, from the streams that I checked the diff is around 0.5 to 1 Mbps

To check is simple you just open the vod if there one and compare.

For some wild reason the vod values are fine.

also this seems a issue only from a few country's, for example some us stream are affected but eu of the same type resolution fps aren't.

@CristianGrecu
Copy link
Author

Hello again, it seems that the problem is back, but only for specific channels this time. I've found quite a few examples that show 3.59 Mbps while live, but 8.76 while watching the VOD. I only watch at source quality, but I guess it could affect the people using "auto".

@fgl27
Copy link
Owner

fgl27 commented Mar 8, 2024

That isn't a problem

As long the source bitrate is bigger then the rest auto playback will just work.

Nothing I can do if all bitrates not just the source one are fucked

@CristianGrecu
Copy link
Author

Oh, I see, I've never used anything lower than source or "auto", so I didn't even think about checking the values. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API issue third party app can only access the provided api, sometimes those api stop working or change bug Something isn't working Resolved
Projects
None yet
Development

No branches or pull requests

3 participants