summaryrefslogtreecommitdiffstats
path: root/packaging/win/fetch-ffmpeg.ps1
diff options
context:
space:
mode:
Diffstat (limited to 'packaging/win/fetch-ffmpeg.ps1')
-rw-r--r--packaging/win/fetch-ffmpeg.ps19
1 files changed, 6 insertions, 3 deletions
diff --git a/packaging/win/fetch-ffmpeg.ps1 b/packaging/win/fetch-ffmpeg.ps1
index 5f6123d..6ffbc51 100644
--- a/packaging/win/fetch-ffmpeg.ps1
+++ b/packaging/win/fetch-ffmpeg.ps1
@@ -3,9 +3,12 @@
Download, verify and stage the ffmpeg/ffprobe MeshBay bundles by default.
.DESCRIPTION
- MeshBay transcodes browser-incompatible video to H.264 (webrtc_server.py,
- `-c:v libx264`) -- a real encode, not just remux/probe -- so only a GPL
- ffmpeg build works here; libx264 is GPL, no LGPL-only build includes it.
+ MeshBay transcodes browser-incompatible video to H.264 (webrtc_server.py)
+ -- a real encode, not just remux/probe -- so only a GPL ffmpeg build works
+ here; libx264 is GPL, no LGPL-only build includes it. The gpl-shared
+ preset also carries h264_qsv and h264_nvenc, which hwaccel.py uses to put
+ that encode on the GPU where there is one; a build without them still
+ works and is simply slower, on the machines that can least afford it.
Asking an end user to separately install ffmpeg (`winget install ffmpeg`)
is not viable for a non-technical install: it needs network access and
winget/App Installer present at that exact moment, and fails silently