Jump to content
Ketarin forum

Can't read source created with Javascript


Recommended Posts

I always got the ffmpeg build number from this site: https://ffmpeg.zeranoe.com/builds/ but they changed it a few days ago. Now the sourcecode just says 

<!DOCTYPE html><html lang=en><head><meta charset=utf-8><meta http-equiv=X-UA-Compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1"><link rel=icon href=/builds/favicon.ico><title>FFmpeg Builds - Zeranoe</title><link href=/builds/css/chunk-vendors.1392eb48.css rel=preload as=style><link href=/builds/js/app.6985bf45.js rel=preload as=script><link href=/builds/js/chunk-vendors.ce69c532.js rel=preload as=script><link href=/builds/css/chunk-vendors.1392eb48.css rel=stylesheet></head><body><noscript><strong>We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id=app></div><script src=/builds/js/chunk-vendors.ce69c532.js></script><script src=/builds/js/app.6985bf45.js></script></body></html>

and I'm no more able to get the version.

Can someone give me a hint how to solve this?

Link to post
Share on other sites
  • 4 weeks later...

They've changed the zeranoe Builds page several times over the years. I gave up parsing it long ago.

I always parse the version number from ffmpeg.org here:
https://ffmpeg.org/download.html#releases

While that is the current "release" from the FFmpeg project, there is a small window where it might not be the actual release version on the zeranoe site (unlikely though since it's a triggered build).

You could also get the version number directly from the Git repo here:
https://git.ffmpeg.org/gitweb/ffmpeg.git/blob_plain/HEAD:/RELEASE

Then you can use the latest-static download link from zeranoe:
https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-latest-win64-static.zip
https://ffmpeg.zeranoe.com/builds/win32/static/ffmpeg-latest-win32-static.zip

If you wanted to solve the problem you actually described instead of work around the JS-built website problem, you'd need to set at least three variables. One to download the initial site and cache the URL to the app*.js file. Then parse that for the git.ffmpeg.org call to collect the release versions, then parse the latest version from the tags. It's a lot of work for a single value though and fraught with potential issues should the JS file name pattern change or the appJS content structure change.

Link to post
Share on other sites
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.