You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across this issue today. If you specify an MPD where source video is .webm, and audio/video encrypted with different keys - then N-m3u8DL-RE is not able to decrypt the video and mux files together. The audio is decrypting fine. It's like the tool does not know it can use a key on the video.
e.g.
MPD
Video (.webm) > kid1:key1
Audio (m4a) > kid2:key2
mux to mp4 or mkv = audio working, no video
If you use shaka-packager manually on the webm file, it decrypts ok. So I think the tool needs to support this format (webm) better for decryption.
The text was updated successfully, but these errors were encountered:
Hello, excuse me. This 63626465653765363339616330313832 can be found in the mpd file, but where did the 61653836613537613039366561643735 data come from?
I came across this issue today. If you specify an MPD where source video is .webm, and audio/video encrypted with different keys - then N-m3u8DL-RE is not able to decrypt the video and mux files together. The audio is decrypting fine. It's like the tool does not know it can use a key on the video.
e.g.
= audio working, no video
If you use shaka-packager manually on the webm file, it decrypts ok. So I think the tool needs to support this format (webm) better for decryption.
The text was updated successfully, but these errors were encountered: