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

A stream from a channel doesn't load at source quality #289

Open
Keula opened this issue Dec 15, 2023 · 6 comments
Open

A stream from a channel doesn't load at source quality #289

Keula opened this issue Dec 15, 2023 · 6 comments
Labels
Device bug A specific bug that happens only to a specific device or one specific user

Comments

@Keula
Copy link

Keula commented Dec 15, 2023

Describe the bug
So for some reason, source quality from singsing stream doesn't load neither live or from for vods December 12th onwards which is when they upgraded their streaming setup apparently. Older vods work and lowering quality to 720p60 works. Couldn't find another streamer that i follow with this issue, so no idea if there are any others.

The differences i could find was the codec reported by the twitch website video stats of these new Dec 12th onwards streams is now:
avc1.640032,mp4a.40.2
instead of
avc1.64002A,mp4a.40.2
Idk what that means or if that's relevant at all, but it's a difference at least, I haven't found other streams with that specific codec yet so testing those in the app might give some answers, so gonna go and try to find one.

Also higher bitrate, seems to be 7.5-7.9Mb/s as opposed to 6mb/s that it was before, but other streamers streams/vods with high or even higher bitrates work just fine in the app so that doesn't seem to be the issue, but maybe with the codec stuff it's relevant info.

To Reproduce
Steps to reproduce the behavior:

  1. Go to singsing stream or a vod from dec 12th onwards in the app
  2. Use source quality
  3. Results in just a black screen with the video/stream not playing, unless lowering the quality

Expected behavior
The stream to load.

Device:

  • TV Model: UMU6103
  • Os version: Tizen 3.0
@fgl27
Copy link
Owner

fgl27 commented Dec 15, 2023

that codec is unsupported by your device

@fgl27 fgl27 added the Device bug A specific bug that happens only to a specific device or one specific user label Dec 15, 2023
@Keula
Copy link
Author

Keula commented Dec 15, 2023

Ah.
Well okay then. mystery solved.

@fgl27
Copy link
Owner

fgl27 commented Jun 7, 2024

I have added automation to try to play the next available stream quality example drop from Source 1080p60 to 720p60

As in most streams, only the source codec is problematic.

@someone30
Copy link
Contributor

someone30 commented Jul 5, 2024

I have added automation to try to play the next available stream quality example drop from Source 1080p60 to 720p60

As in most streams, only the source codec is problematic.

I would love to have an option to set 720p(60) as the default bitrate for all videos/streams. It would save bandwidth (usually more than 50%) and reduce the response time when fast forwarding / rewinding in VODs.

Yes, the bitrate can already be manually lowered through the control panel on a per-video/-stream basis, but it would be so much easier to (optionally) have 720p(60) as the default and instead switch to the highest quality manually when needed (maybe 10% of the time in my case). Also see my old feature request #39 from 2019. 🙂

@fgl27
Copy link
Owner

fgl27 commented Jul 6, 2024

I have added automation to try to play the next available stream quality example drop from Source 1080p60 to 720p60
As in most streams, only the source codec is problematic.

I would love to have an option to set 720p(60) as the default bitrate for all videos/streams. It would save bandwidth (usually more than 50%) and reduce the response time when fast forwarding / rewinding in VODs.

Yes, the bitrate can already be manually lowered through the control panel on a per-video/-stream basis, but it would be so much easier to (optionally) have 720p(60) as the default and instead switch to the highest quality manually when needed (maybe 10% of the time in my case). Also see my old feature request #39 from 2019. 🙂

I know I'm lagging in adding features
those two can be added is not that complicated I will see to do so next time I have some proper free time

@someone30
Copy link
Contributor

No problem at all. I just thought maybe you can use parts of the "auto bitrate drop" code to realize that old feature request. That's why I mentioned it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Device bug A specific bug that happens only to a specific device or one specific user
Projects
None yet
Development

No branches or pull requests

3 participants