Streampunk / beamcoder

Node.js native bindings to FFmpeg.
GNU General Public License v3.0
397 stars 76 forks source link

Cannot download dev header of ffmpeg on WIndows #50

Closed arition closed 3 years ago

arition commented 4 years ago

The install_ffmpeg.js script will download https://ffmpeg.zeranoe.com/builds/win64/dev/ffmpeg-4.2.1-win64-dev.zip on windows systems. For now this zip file does not exist on the server (returns a status code of 404).

The website also says that it will stop operating on Sep.18. Maybe we need to find a way to host the binary file.

Rock-N-Troll commented 3 years ago

Still not resolved. I came here to see why install wasn't working and I guess this is why based on the timeout. I'll look for a work around in the mean time

https://www.reddit.com/r/ffmpeg/comments/ikht2k/ffmpegzeranoecom_will_close_on_sep_18_2020/

https://www.gyan.dev/ffmpeg/builds/

Rock-N-Troll commented 3 years ago

it looks like getting full_build-shared.zip from https://www.gyan.dev/ffmpeg/builds/packages/

As noted on the front-page: "In addition, the release full variant is available as a shared build with development files."

Update: I ended up getting it to work by 1.downloading the beamcoder source from github 2.downloading the full_build-shared.zip as mentioned above,

  1. extracting the zip into ffmpeg folder (if not already created) and saving duplicates of it as the 2 files named -dev and -shared as shown in the screenshot (even though the old 4.2.1 version name is used.)
  2. Comment out the async function win32() {} function in install_ffmpeg.js which is supposed to download the zip file into ffmpeg folder we already extracted sneakily into -dev and -shared folders
  3. Install from locally download beamcoder source via something like npm install -g ./beamcoder-master

image

This is obviously not a long term solution as it's very manual and the versions don't match up, but it looks like the gyan.dev site owner might be ok with being incorporated into this project for the npm install.

scriptorian commented 3 years ago

Thanks for your patience and determination! This should be working again now, v0.6.1.