as in summary. cuda use mask has been dropped for media-video/mpv in: https://gitweb.gentoo.org/repo/gentoo.git/commit/profiles/arch/amd64/package.use.mask?id=4172e5ff62cf6439226543cb15ca691ce4eff7ea Alright, ffmpeg-3.3 is in tree but it does not do anything about cuda at all. So, if you enable cuda USE for mpv, it will just install ffmpeg-3.3.x, if its not already installed. None of ffmpeg ebuilds in portage tree have cuda support enabled, via USE's and configure options. Before ffmpeg get the cuda support, mpv[cuda] is meaningless. Reference: https://bugs.gentoo.org/595450 Reproducible: Always
(In reply to Oleg from comment #0) > as in summary. > cuda use mask has been dropped for media-video/mpv in: > https://gitweb.gentoo.org/repo/gentoo.git/commit/profiles/arch/amd64/package. > use.mask?id=4172e5ff62cf6439226543cb15ca691ce4eff7ea > Alright, ffmpeg-3.3 is in tree but it does not do anything about cuda at > all. > So, if you enable cuda USE for mpv, it will just install ffmpeg-3.3.x, if > its not already installed. None of ffmpeg ebuilds in portage tree have cuda > support enabled, via USE's and configure options. Before ffmpeg get the cuda > support, mpv[cuda] is meaningless. > > Reference: > https://bugs.gentoo.org/595450 > > Reproducible: Always I don't have an NVIDIA card, but CUDA with mpv reportedly works. mpv reimplements most of the required bits and don't require cuda bits from ffmpeg except for one header, which are always there (/usr/include/libavutil/hwcontext_cuda.h). If you have NVIDIA card and CUDA support with mpv is broken for you, please open a new bug describing what runtime/buildtime problem you have. *** This bug has been marked as a duplicate of bug 603974 ***
this is not duplicate and the reference bug does not deal with any CUDA-enabled ffmpeg in *portage tree*. This is discussion about user and proxy maintainer User who have mpv/ffmpeg working but the origin of his testing ebuild for ffmpeg is unknown, so it was completely artificial judgement about cuda is working, Please, re-read the logic of this report there is no CUDA-workinf ffmpeg in portage tree (official one that is offered to users).
to make it move obvious: cuda? ( >=media-video/ffmpeg-3.3:0 ) alright, it will pull in ffmpeg-3.3. Does it pull ffmpeg that have CUDA options enabled? No. Correct way is, bring ffmpeg that is capable to utilitize CUDA, when compiled with cuda support. This is reported in https://bugs.gentoo.org/595450. So, only when this fixed, then: cuda? ( >=media-video/ffmpeg-3.3:0[cuda] ) does make sense. Thank you.
(In reply to Oleg from comment #3) > to make it move obvious: > cuda? ( >=media-video/ffmpeg-3.3:0 ) > alright, it will pull in ffmpeg-3.3. Does it pull ffmpeg that have CUDA > options enabled? No. > Correct way is, bring ffmpeg that is capable to utilitize CUDA, when > compiled with cuda support. This is reported in > https://bugs.gentoo.org/595450. > So, only when this fixed, then: > cuda? ( >=media-video/ffmpeg-3.3:0[cuda] ) does make sense. You are wrong. Let me repeat again the most important part from my comment above: mpv don't require cuda bits from ffmpeg except for one header, which is always there (/usr/include/libavutil/hwcontext_cuda.h). It seems you've skipped the comments that explains cuda situation in great details: https://bugs.gentoo.org/603974#c1 See also https://github.com/mpv-player/mpv/issues/3941 Again, mpv since 0.23.0 is specifically tailored upstream to work WITHOUT any special ffmpeg build options or any cuda packages from nvidia. You just need libcuda.so provided by nvidia-drivers.
