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

Greenish lines observed when initialized the encrypted channel playback on Shaka player #6420

Closed
Ramajayadevi174 opened this issue Apr 9, 2024 · 8 comments
Labels
type: bug Something isn't working correctly
Milestone

Comments

@Ramajayadevi174
Copy link

Have you read the FAQ and checked for duplicate open issues?
yes

If the problem is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?
v4.7.11-uncompiled

Can you reproduce the issue with our latest release version?
Using latest version v4.7.11

Can you reproduce the issue with the latest code from main?

Are you using the demo app or your own custom app?
The demo

If custom app, can you reproduce the issue using our demo app?
N/A

What browser and OS are you using?
Mozilla firefox

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A

What are the manifest and license server URIs?
No asset

What configuration are you using? What is the output of player.getConfiguration()?

What did you do?
Configure the Manifest url, license server url and header values to play the encrypted playback.

What did you expect to happen?
There should be a playback without any macroblocks/Greenish lines over a playback.

What actually happened?
Observed greenish lines while initiate a playback and its recovered when we enabled/disabled the Low latency Mode and Auto Low latency mode options on the Settings menu on the player.
greenish_lines_encrypted_pb_shaka

@avelad
Copy link
Collaborator

avelad commented Apr 9, 2024

Please provide a sample stream to test it! Thanks!

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 9, 2024
@Ramajayadevi174
Copy link
Author

Ramajayadevi174 commented Apr 12, 2024 via email

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 12, 2024
@joeyparrish
Copy link
Member

@Ramajayadevi174, please follow these instructions from the issue template:

**What are the manifest and license server URIs?**
<!-- NOTE:
  You can send the URIs to <shaka-player-maintainers@googlegroups.com> instead,
  but please use GitHub and the template for the rest.
  A copy of the manifest text or an attached manifest will **not** be
  enough to reproduce your issue, and we **will** ask you to send a
  URI instead.  You can copy the URI of the demo app to send us the
  exact asset, licence server, and settings you have selected there.
  If you send the URIs to email, the response time and resolution
  will be much higher.
-->

If you need to send us additional instructions for authorization, include that in the email.

Without a way to reproduce and debug your issue, we can't work on it.

If you want to work on your own PR to resolve the issue, we can assign it back to you.

@joeyparrish joeyparrish added status: waiting on response Waiting on a response from the reporter(s) of the issue type: bug Something isn't working correctly labels Apr 12, 2024
@shaka-bot shaka-bot added this to the v5.0 milestone Apr 12, 2024
@Ramajayadevi174
Copy link
Author

Ramajayadevi174 commented Apr 15, 2024 via email

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 15, 2024
@joeyparrish
Copy link
Member

I'm unable to access your content. Your hostname doesn't resolve: https://www.nslookup.io/domains/live.pl10d.vdochne2e.com/dns-records/

@joeyparrish joeyparrish added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 20, 2024
@Ramajayadevi174
Copy link
Author

Ramajayadevi174 commented Apr 22, 2024 via email

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 22, 2024
@joeyparrish
Copy link
Member

It's not a matter of my IP, unless your name servers need to allow-list me to resolve the domain name. Please check the link above. Your domain has no public A or AAAA records at all.

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 23, 2024
@avelad avelad modified the milestones: v4.8, v4.9 Apr 26, 2024
@shaka-bot
Copy link
Collaborator

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working correctly
Projects
None yet
Development

No branches or pull requests

4 participants