I agree with you on that. It is definitely fine with me.
As you’ve already said, it would be much easier for me to have a discussion like this in my native language.
Thank you very much for your patience.
2 Likes
Thank you, from one of those home users. 
I’ve been adding Packman for years with highest priority, and then switching packages to use it. I never really thought about whether that was still absolutely necessary. I suppose I can do the same with VLC repository, at least in regard to multimedia codecs.
1 Like
Yes, you can (eg vlc, vlc-codecs, libx264-165, libx265-215). The official OSS repository now supplies most of the remaining multimedia stack.
5 Likes
I need :
a) vlc-codecs to play some mp4. Without this, vlc can’t play all mp4s
b) gstreamer-plugins-bad-codecs
gstreamer-plugins-ugly-codecs
to play product presentation videos on the Amazon site with Firefox for example.
Until today I did not know the existence of gstreamer-plugins-bad and gstreamer-plugins-ugly
Do they replace gstreamer-plugins-bad-codecs and gstreamer-plugins-ugly-codecs ?
Is there a replacement for vlc-codecs?
Thanks
1 Like
There’s enough info here to provide an answer to your question. Search the forums.
a) vlc-codecs rpm contains
/usr/lib64/vlc/plugins/codec/libx264_plugin.so
/usr/lib64/vlc/plugins/codec/libx26410b_plugin.so
/usr/lib64/vlc/plugins/codec/libx265_plugin.so
These are all ENCODERS, they do not decode anything.
b) Firefox do NOT use gstreamer at all, it’s many many years ago since firefox was switched to use codecs from ffmpeg project.
I suspect what happend was that installing vlc-codecs pulled in Packmans/vlc’s rebuild of ffmpegs libavcodec and friends, and that “fixed” your issue.
Edit: Google ai says: Firefox switched to using FFmpeg by default on Linux with the release of Firefox 43 in December 2015.
1 Like
thanks for the explanation. I am not a techie person for this problem.
I only know that I must install vlc-codecs, gstreamer-plugins-bad-codecs and gstreamer-plugins-ugly-codecs to complete the installation of vlc and firefox.
Certainly this causes the installation of other packages.
Finally to fully install VLC we need to use the VLC repository and maybe also for Firefox use the Firefox repository.
In the VideoLAN repository, there’s an “additional codecs” package:
> LANG=C.UTF-8 zypper info --repo VideoLAN vlc-codecs
Loading repository data...
Reading installed packages...
Information for package vlc-codecs:
-----------------------------------
Repository : VideoLAN - VLC, libdvdcss, FFmpeg
Name : vlc-codecs
Version : 3.0.23-425.6
Arch : x86_64
Vendor : VideoLAN Project (http://www.videolan.org)
Installed Size : 114.2 KiB
Installed : No
Status : not installed
Source package : vlc-3.0.23-425.6.src
Upstream URL : http://www.videolan.org
Summary : Additional codecs for the VLC media player
Description :
This package enhances the functionality of the VLC media player by
codecs that are not available in the stock openSUSE distribution.
>
Did you mean this “vlc-codecs” package?
Repository URI – choose your openSUSE system before adding to your list of repositories → <https://download.videolan.org/SuSE/>
Thanks
yes I found it.
I have just switched to vlc repo. I replaced all packman packages by those of VLC repo.
Also I uninstalled gstreamer-plugins-bad-codecs and gstreamer-plugins-ugly-codecs.
I disabled packman repo.
I checked there is no side effect
1 Like
For a general desktop user, FFmpeg + the libav libraries are sufficient for most multimedia codec needs. For applications that do rely on the GStreamer framework, gstreamer-plugins-libav together with the FFmpeg libraries from the VLC repository can provide most of the codec support they might require. The gstreamer-plugins-libav plugin is essentially a bridge between GStreamer and FFmpeg’s/libav’s codec implementations.
2 Likes
thank you very much
for those who need APTX. for example to use PC speaker to play music or video on the phone.
You can found several packages freeaptx in the following repo :
https://download.opensuse.org/repositories/multimedia:/proaudio/openSUSE_Tumbleweed/
if you want in addition pipewire-aptx then use instead the following deposit:
https://download.opensuse.org/repositories/home:/alveus:/depository/openSUSE_Tumbleweed/
addendum : set the priority of these repos to 110 to avoid replacing standard packages with those of these repos.
Just wanted to drop the link to the Packman mailing list archive here for people who are interested in the current discussions regarding the future of the project:
https://lists.links2linux.de/pipermail/packman/
1 Like
Please be aware that those repos are development repos, so add them only if you know what you are doing, since there might be occasional conflicts with the other packages in the system.
1 Like
The packages I’m talking about do not exist in standard deposits.
Yes in these deposits, there are packages that are likely to replace standard packages. they make it avoid this is why I added:
addendum : set the priority of these repos to 110 to avoid replacing standard packages with those of these repos.
That is not where priorities are for. They only work for the installation of a not installed package.
After that “vendor stickiness” will avoid changing to another repository (in fact vendor) when an update is done and a newer version is available on that repo.
Thus you do not need priority to avoid “replacing”.
What you avoid is installing a new package from the repo with the low priority.
2 Likes
then how those codecs will be available, videos from my average android device also needed that to play, and for that only I installed packman, don’t say that download vlc flatpak for everything…
I’m on Leap 16.0
Made the move to VLC repo for vlc stuff. Downloaded a statically linked ffmpeg from github to bin folder for my scripts that need ffmpeg with all the goodies, there’s also fdkaac encoder i built from sources that i needed. Also built my own Mesa with proprietary codec support so hw acceleration works with vaapi in my browser and what not (tbf youtube can work fine with just vp9).
That’s probably 1% of what packman repo was doing and I’m now sort of liberated from something that is a dying project and potentially a problem.
My hope is that leap is no tumbleweed so my custom stuff is unlikely to break