Just a note that since March 2018 there is a problem with the x264 and x265 binaries being distributed by Packman, widely advertised here as a solution to the non-support of x254/5 codecs in the default SuSe repos.
What looks like an innocuous comment in the recent updates (e.g. x264-152, x265-151), is a major problem in reality:
- Conditionally BuildRequire nasm for current versions of
openSUSE and pass conditional --disable-asm to openSUSE Leap 43.3
Without use of an assembler (was YASM, now NASM), there are no MMX or SSE instructions used - the machine will likely use 100% CPU, may overheat or not be able to encode/decode some material at all. The clue is in the detailed log output, which looks like this:
"x265 [info]: using cpu capabilities: none!"
NASM can be easily installed (in main OSS repo) and you can build the packages yourself to restore expected functionality, not sure why Packman doesn’t do this.
For the future, I think SuSe should look at a better way of dealing with this long-standing licensing issue, such self-inflicted wounds will do nothing to help the distro’s popularity.
There is no distro making contributing so easy as openSUSE. We’re a community distro, anyone can step up and do whatever they want. Report bugs, help out fixing them, building better packages, Feel welcome to help find a solution or at least report a bug if you’re convinced this is one .
afaik current packman builds are compiled with nasm I don’t encode that much but I did view an HD h265 video with software decoding (my gpu doesn’t support h265) and the playback was smooth
if you haven’t already just do an update
* Fri Mar 23 2018 firstname.lastname@example.org
- Build with nasm >= 2.13 for openSUSE Leap 42.3 and SLE-12.
* Thu Mar 01 2018 email@example.com
- Update to version 2.7:
- Moved from YASM to NASM assembler. Supports NASM assembler
version 2.13 and greater.
- Replace yasm with nasm BuildRequires following upstreams changes.
The real problem was that Leap 42.3 comes with a too old nasm though (version 2.10.09), i.e. it actually was not possible to build x264/x265 with nasm in the first place anymore.
This has been “fixed” by adding nasm 2.13 to Packman as well.