drm free content batch downloader, widefrog

[Obo]

You do know that the JWT has a very limited lifetime (just 2 minutes) and probably needs to be refreshed with the refresh token handed out after login? That would at least be an explanation for the error response you got.

You've stripped the refresh workflow from the original service script though...

To check the payload of a JWT you can use the site jwt.io (or base64-decode the second part of the JWT).

[Kevste]

I've been having some trouble downloading from VTMGo, even though it has worked for over a year.

Microsoft Windows [Version 10.0.26200.8037]
(c) Microsoft Corporation. Alle rechten voorbehouden.

D:\Film en Series\DRM 2>venv\Scripts\activate.bat

(venv) D:\Film en Series\DRM 2>cd widefrog

(venv) D:\Film en Series\DRM 2\Widefrog>python widefrog.py "https://www.vtmgo.be/vtmgo/afspelen/7c0ac9e3-6c1a-4175-b9d5-f63f0f0c562d" --debug
[INFO] Current app version: 3.2.0
[INFO] Running on: windows/64bit/python 3.12.3
[INFO] Starting the service initialization stage.
[INFO] Current progress: [1/1]
[INFO] Starting the collections extraction stage.
[INFO] Current progress: [1/1]
[INFO] Starting the media data extraction stage.
Traceback (most recent call last):
File "D:\Film en Series\DRM 2\Widefrog\widefrog.py", line 124, in <module>
main_service.run_service(response)
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 442, in run_service
dwn_cmds, failed_cmds, proc_cmds = main_service.get_download_commands_parallel(demo_u rls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 395, in get_download_commands_parallel
success, fail, proc = future.result()
^^^^^^^^^^^^^^^
File "C:\Python312\Lib\concurrent\futures\_base.py" , line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "C:\Python312\Lib\concurrent\futures\_base.py" , line 401, in __get_result
raise self._exception
File "C:\Python312\Lib\concurrent\futures\thread.py ", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 281, in get_download_commands
raise e
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 266, in get_download_commands
dl_cmds, pr_cmds = main_service.get_download_command(service, source_element)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 84, in get_download_command
raise e
File "D:\Film en Series\DRM 2\Widefrog\utils\main_service.py", line 63, in get_download_command
manifest, pssh, additional = service.get_video_data(source_element)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Film en Series\DRM 2\Widefrog\services\vtmgo_be.py", line 125, in get_video_data
raise CustomException(ERR_MSG.format(
utils.structs.CustomException: [USER_ERROR]/[APP_ERROR] Failed to download: https://www.vtmgo.be/vtmgo/afspelen/7c0ac9e3-6c1a-4175-b9d5-f63f0f0c562d. Reason: This content is no longer available or refresh the site cookies or VPN issues (Belgium). Solution: Do not attempt to download it or sign into your account using Firefox and play a random video or fix your VPN. If it persists then debug the service.

(venv) D:\Film en Series\DRM 2\Widefrog>

I'm using Firefox to watch the video before I even open cmd, that's how it always worked in the past to make sure it picks up the cookies.

[Virgil]

I am using the widefrog.exe (widefrog_v3_2_0_windows) file to download from VTMGo. This worked well but recently I also experienced something strange after cookie updates. Now I get the following error :
[USER_ERROR] Failed to download: from vtmgo_be. Reason: Need account for this service. Solution: Sign into your account using Firefox.

Although the video plays in firefox, widefrog fails. I think that something has been changed related to DPG media and the way the login details are stored.

[Hutrx]

Can you provide a diff of what you changed?

From what I can tell you'll at least need to change
- headers for graphql requests to include something like:

            'joyn-distribution-tenant': 'JOYN_AT',
            'joyn-user-state': 'code=R_A;sessionLocation=AT;userLocation=AT',
            'origin': 'https://www.joyn.at',

- Login URL should point to www.joyn.at/oauth
- you'll likely need an austrian account

Best to look at saved headers from a working browser request. I'd suggest to save them as HAR file.

So out of curiosity, is Joyn.de working for other people?

I tried to debug it preperly a few weeks ago, but while I'm certainly not new to coding (I've worked mainly with C++), I am new to Pyhon (not an issue - it's just logic), and web (more of an issue - a lot of alien concepts). I concluded Joyn changed the login flow and I needed to start on a simpler project. Seems I was wrong and for some it works? Or is it only working when you hard-code the token copied from a real browser login, as opposed to the "not signed in" token? I tried and failed to locate the latter...

I have read elsewhere that 1080p is possible with L3, so it may have been choice of content (e.g. https://www.joyn.de/serien/kuestenwache/17-21-hexenloch) which limited the resolution, or possibly that my "fix" was based on the token used when you don't log in.

(I'm not expecting a fix or a download. I got 540p for the things I wanted from Joyn (it wasn't just this), which may be all that's on offer anyway, at least with my Android Studio L3 cert. My aim is to get to the point of writing my own scripts, so more, it's for my education .)

[Obo]

Joyn works for me, but I use a cached token + refresh token workflow, and don't use widefrog. I can't tell you if they changed the login flow.

For 1080p you'll need a valid paid subscription; I've once tested it and wasn't able to download 1080p material then, but L3 should suffice.

[Hutrx]

Joyn works for me, but I use a cached token + refresh token workflow, and don't use widefrog. I can't tell you if they changed the login flow.

For 1080p you'll need a valid paid subscription; I've once tested it and wasn't able to download 1080p material then, but L3 should suffice.

Thanks for taking the trouble to respond. When it comes to Widefrog, I've taken the view that it's abandonware, and it's up to the people that want services to work to fix them. And really I don't see why I can't fix it given time (which is in short supply right now anyway), and if I fix it, I'll post the solution.

But it sounds like I'm already getting as good as I can. I am unable to subscribe anyway, as they've rejected my payment, I guess based on billing address (I learn German, but I don't live in D-A-CH).

In practice, I've found most of what I can't get is available elsewhere at 1080p, if you know where to look...

[Lostion]

Joyns own Stuff is 1080p with L3 but external stuff like FBI, NCIS etc is 1024/1280 browser only, you need the TV endpoint for 1080p but then you need L1 or PlayReady.

[Hutrx]

Joyns own Stuff is 1080p with L3 but external stuff like FBI, NCIS etc is 1024/1280 browser only, you need the TV endpoint for 1080p but then you need L1 or PlayReady.

Thanks! It's really their own stuff I'm after anyway. There's not much need for anyone to download the FBI stuff themselves, and it's not really what I'm after, but useful to know it wouldn't work...

German TV helps me learn German, and fixing/writing a downloader will help me learn web, which is a huge gap in my knowledge. So with something like this...
https://www.joyn.de/serien/ein-hof-zum-verlieben

...which is their own and new, I have a feeling that it looks like 1080p in Brave (I don't even need VPN to play it), although that's by eye, of course.

I am wondering if for someone like me (can write code, but knows nothing about the web), fixing Widefrog isn't the right thing for me to do. The real requirement is to download from Joyn at the best resultion possible with the cert I have, and I might learn more with a dedicated script anyway, which could use a cached token, just as others do.

Thanks for your hints

[Hutrx]

Joyns own Stuff is 1080p with L3 but external stuff like FBI, NCIS etc is 1024/1280 browser only, you need the TV endpoint for 1080p but then you need L1 or PlayReady.

Actually, could I just ask one minor thing on this. You say there's a separate TV endpoint that needs L1 / PlayReady, and of course there is a web endpoint. Do you need to use the TV endpoint for all 1080p but the level or protection changes depending on the content? Or is it 1080p in the browser if it's theirs?

I think you meant the latter, but I wanted to check. I have not paid, but I think for that show I sent, I am getting better than 540p, but hard to be sure how much better.

Thanks again

[Lostion]

If its in 1080p in browser then its L3 if you can only get 1024/1280 its still L3 but 1280/1080p is L1 (depends on the series sometimes 1280 is available in browser but mostly not for licensed stuff like FBI/NCIS and so on).

I don't have premium at the moment so i cant test

[Hutrx]

If its in 1080p in browser then its L3 if you can only get 1024/1280 its still L3 but 1280/1080p is L1 (depends on the series sometimes 1280 is available in browser but mostly not for licensed stuff like FBI/NCIS and so on).

I don't have premium at the moment so i cant test

Thanks!