Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60667 - [mpv] consider compiling with vapoursynth

Attached to Project: Community Packages
Opened by hexchain (hexchain) - Thursday, 01 November 2018, 11:11 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:07 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 15
Private No

Details

Description:
MPV supports vapoursynth but is not compiled with it, so the current MPV build does not actually work with it even if it's installed.

Please consider adding vapoursynth as a dependency, as it is needed for --vf=vapoursynth and other things like SVP.

Additional info:
* package version(s)

mpv 1:0.29.1-2
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:07 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/mpv/issues/1
Comment by hexchain (hexchain) - Thursday, 19 March 2020, 12:19 GMT
Hello, I see something similar has been done for sndio. What could be the obstacle here? AFAIK just adding "vapoursynth" to the "depends" array should be sufficient. Is it because vapoursynth is too big, or are there other reasons?
Comment by Christian Hesse (eworm) - Thursday, 19 March 2020, 13:24 GMT
The package vapoursynth is bigger on its own, and it pulls in same more dependencies.
Still unsure about this one.
Comment by zerkshop (zerkshop) - Tuesday, 07 March 2023, 04:32 GMT
Any further thoughts on this? It would be very convenient to have official support.

How about a split package for "mpv-vapoursynth"? That's what is done for different versions of opencv, e.g:

https://archlinux.org/packages/extra/x86_64/opencv/
https://archlinux.org/packages/extra/x86_64/opencv-cuda/

comparing the file lists of those two packages
- opencv: 794 files and 99 directories.
- opencv-cuda: 922 files and 114 directories. 793 files are the same path. The extra files are specific to the cuda support

Comment by kalio (kalio) - Sunday, 02 April 2023, 19:59 GMT
I just created  FS#78100  for vapoursynth to remove most of its dependencies (libass, ffmpeg, imagemagick, tesseract), because upstream vapoursynth removed the features requiring them (in 2021).

If that change is made, vapoursynth could be added to mpv without pulling in any other dependencies. zimg won't be additional, because mpv already requires ffmpeg which requires zimg. python won't be additional, because mpv already requires libplacebo which requires glslang which requires python.
Comment by zerkshop (zerkshop) - Thursday, 25 May 2023, 00:40 GMT
FYI  FS#78100  is now closed
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.
Comment by Martin Rys (C0rn3j) - Sunday, 01 October 2023, 21:43 GMT
@eworm

Now with Vapoursynth not requiring extra dependencies, would you consider adding it?

Loading...