| 开发者 | thystra |
|---|---|
| 更新时间 | 2026年8月23日 10:28 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
argentwolf-video-processor/<attachment-id>/ subtree.
Native HLS is used where the browser supports it. Other compatible browsers use
the locally bundled, pinned hls.js player. Progressive sources remain available
as fallbacks.
The plugin stores work in a database queue and processes one video at a time.
Its recurring WordPress event only starts a detached WP-CLI worker; FFmpeg does
not run inside the WP-Cron callback or an administrator web request.
No video, metadata, or usage information is sent to an external processing
service.
proc_open() and, for automatic dispatch, exec().No. The original WordPress attachment is preserved. Processing creates separate derivatives.
No. Metadata stripping applies to generated derivatives and HLS renditions. The original upload may retain its original metadata.
The plugin produces multiple HLS renditions. The player can move among available 360p, 480p, and 720p renditions as bandwidth and player size change.
Yes. Settings > ArgentWolf Video provides Smart queue, Add adaptive HLS only, and Force reprocess all operations, with an optional upload-date range.
No. Web and WP-Cron requests only queue or dispatch work. A detached WP-CLI worker performs the encode.
Adaptive HLS uses H.264/AAC fragmented MP4. The default progressive fallbacks use VP9/Opus WebM followed by H.264/AAC MP4.
Yes. Before starting a new transcode, the plugin checks the configured FFmpeg version and relevant compiled capabilities. Known-vulnerable or unverifiable builds are blocked. CVE-2026-8461 is checked against the MagicYUV decoder and linked from Diagnostics and Site Health: https://nvd.nist.gov/vuln/detail/CVE-2026-8461
No. It uses administrator-configured system FFmpeg and FFprobe binaries and checks their version, codecs, HLS muxer, and fragmented-MP4 support.
Automatic detached dispatch is unavailable. An operator may invoke
wp argent-video worker --once from a system scheduler. Encoding still requires
proc_open().
No. Video processing occurs on the WordPress server. The pinned hls.js runtime is bundled with the release and served locally.
{$wpdb->prefix}argentwolf_video_processor_logs.argent_video_jobs table for compatibility while using the canonical argentwolf_video_processor_* identifier for newly introduced tables.wp_upload_dir()['basedir']/argentwolf-video-processor/<attachment-id>/.hls.VERSION and hls.SHA256 from the installable ZIP.argentwolf-video-processor.open_basedir restrictions.open_basedir in diagnostics.