-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
[Bug]: Decrypted video lessons with size 250 to 300 bytes #256
Comments
I’m experiencing the same issue, and it’s quite frustrating. Although the first lecture downloaded successfully, the others are unusually small in size and unplayable. As far as I know, the DRM is configured correctly. |
Hey, I realized that this issue was related to the Docker container. I was running the repository within a Docker container on an M Silicon MacBook. I created a virtual environment from scratch, installed shaka-packager, and linked the virtual environment, so it works now. |
@celikemir I also run the script in docker and have the same issue where encrypted files have a small size, but the DRM config is okay. What did you do with shaka-packager exactly ? you added it to your docker compose ? |
The latest version of the script doesn't use shaka-packager for decryption anymore and uses FFmpeg instead, you need version 5 or higher. That might be the issue with docker |
@Puyodead1 You were right, I modified the dockerfile to force the latest ffmpeg version, rerun the script and the video files were well decrypted and I could play them. Here's the updated dockerfile I made :
|
What happened?
Decrypted video lessons with size 250 to 300 bytes
Since the latest changes made to the script (a couple of months ago), I only get corrupted video files, with ridiculous size. If we talk only about this specific problem, the previous version of the script did not present this serious problem.
Expected Result
The script should download, decrypt and multiplex the playable video files for each of the lessons.
Branch
master/main
What operating systems are you seeing the problem on?
Linux/Unix, MacOS
Relevant log output
Other information
I'm using:
The text was updated successfully, but these errors were encountered: