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

SmoothStreaming: Assume subtitles are not DRM'd in protected streams #4838

Closed
hereisclient opened this issue Sep 19, 2018 · 5 comments
Closed
Assignees
Labels

Comments

@hereisclient
Copy link

hi

Issue description

i reported subtitle issue
#4824

above link is my old issue link.
i checked commit contents today and i checked if this issue was solved.
my opinion about my old issue is "YES" .
Trackselector gets subtitle information properly.

but subtitle list is disable because getTrackSupport function returns subtitleRendererCapabilities.FORMAT_UNSUPPORTED_DRM

so i couldn't change subtitle language.

my test contents is just non-drm smooth streaming with subtitles.

Link to test content

i will send you my test link.

Version of ExoPlayer being used

2.8.3

Device(s) and version(s) of Android being used

version : 8.0
device : xiomi mibox3

@ojw28
Copy link
Contributor

ojw28 commented Sep 19, 2018

my test contents is just non-drm smooth streaming with subtitles.

It looks like at least the audio and video are DRM'd. Are you referring only to the text streams? If so then I see your point, but it's unclear to me how the player should determine that the text streams are not DRM protected as well. The manifest structure looks a bit like:

SmoothStreamingMedia
    Protection
    StreamIndex(video)
    StreamIndex(audio)
    StreamIndex(text)

Which we interpret as the Protection element applying to all of the StreamIndex elements, including the text one. The player then decides the text stream is not supported, because we don't support DRM protected text.

Are you aware of anything in SmoothStreaming specification that defines which StreamIndex elements a Protection element should apply to? We could "fix" the problem by not applying it to elements with Type="text", but I can't see it defined anywhere that this is correct client behavior, so it's somewhat unclear whether that's the right thing to do. Any ideas?

@hereisclient
Copy link
Author

hereisclient commented Sep 19, 2018 via email

@ojw28
Copy link
Contributor

ojw28 commented Sep 26, 2018

Did you receive any update from your client? Also, could you confirm that the video and audio are intentionally DRM protected in the provided sample, and that it's just the text stream that's not protected?

@hereisclient
Copy link
Author

i'm so sorry to be late reply because i was in vacation by yesterday.

i didn't any answer from my client about sample content. but i guess sample i was provided was not encrytped. just that used url redirection. if this sample was encrypted, before playing this , i must need customdata or somthing else.
and 3rd party player can easily play sample with subtitle.

but this is just only my opinion. if i get the another information from my client. i will notify you.

thank for a lot of your effort.

@ojw28 ojw28 changed the title subtitle item is disabled SmoothStreaming: Assume subtitles are not DRM'd in protected streams Oct 15, 2018
@ojw28
Copy link
Contributor

ojw28 commented Oct 15, 2018

We probably need to assume subtitles are not protected. Marking as a bug.

andrewlewis pushed a commit that referenced this issue Nov 26, 2018
@ojw28 ojw28 closed this as completed Nov 27, 2018
ojw28 added a commit that referenced this issue Nov 28, 2018
@google google locked and limited conversation to collaborators May 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants