Jump to content

HEVC x265 video doesn't work anymore


bernux

Recommended Posts

I don't understand what happen but since I update to 4.1.0.3 x265 videos doesn't work on any device (chromecast,shield, android phone) I tried to downgrade to latest stable that was working but not anymore.

I got some error in the log like this :

ld-elf.so.1: Shared object "libva-x11.so.2" not found, required by "libavutil.so.56" ( at emby start)

and

System.Exception: System.Exception: No video encoder found for 'h264' (when trying to play hevc file)

 

Trailer wasn't working work too

 

I finally get iall things works as expected modifying libavutil.so.56 coming with emby package

mv /usr/local/lib/emby-server/lib/libavutil.so.56 /usr/local/lib/emby-server/lib/libavutil.so.56.bak && ln -s /usr/local/lib/libavutil.so.56 /usr/local/lib/emby-server/lib/libavutil.so.56

if needed I could join embyserver.txt

 

Maybe it can help someone

 

I may open an other topic for trouble with user account without pin code on local network

Link to comment
Share on other sites

makarai

@@makarai have you run into this?

 

I have plenty of x265 videos, and they work if the processing power is sufficient for the device, however, i have not ventured into FreeBSD 12 so i am not sure what the issue is. I might advice to just install a freebsd 11.2 jail in freebsd 12 to circumvent this issue.

Edited by makarai
Link to comment
Share on other sites

makarai

it's an headless server nothing related to X installed on it.

 

can you install on your headless freebsd12 a freebsd 11.2 jail, and try from there?

Link to comment
Share on other sites

Not before several day, I already got some important jail running and not a lot of time when back from job, so I don't want to break something and spend my night to repair ;-)

And I still have to debug the other trouble with code pin which must be set (if not it says user or passwork invalid) for connection on local network

Link to comment
Share on other sites

unhooked

FWIW, I'm not having any issues here.

 

<get 5:13pm> pkg which /usr/local/lib/libva-x11.so
/usr/local/lib/libva-x11.so was installed by package libva-2.4.0
 

I would pkg update/upgrade as that file was bumped on Friday.

Link to comment
Share on other sites

metsuke

I had a similar error, and I installed libva-utils to fix it.

 

Can you post a pkg info to compare your package set?

For reference these are the packages in my emby jail 12.0-RELEASE:

# pkg info | awk '{print $1}'
ca_root_nss-3.41.1
cairo-1.15.12,2
cmocka-1.1.1_1
curl-7.63.0_1
dialog4ports-0.1.6
emby-server-4.0.0.2_1
expat-2.2.6_1
fontconfig-2.12.6,1
freetype2-2.9.1
fribidi-0.19.7
gamin-0.1.10_10
gettext-runtime-0.19.8.1_2
giflib-5.1.4
glib-2.56.3_2,1
gmp-6.1.2_1
gnutls-3.6.6
graphite2-1.3.13
harfbuzz-2.3.0
iconv-2.0_4
indexinfo-0.3.1
jansson-2.12
jbigkit-2.1_1
jpeg-turbo-2.0.1
lcms2-2.9
libX11-1.6.7,1
libXau-1.0.8_5
libXdamage-1.1.4_5
libXdmcp-1.1.2_2
libXext-1.3.3_3,1
libXfixes-5.0.3_2
libXxf86vm-1.1.4_3
libarchive-3.3.3,1
libass-0.14.0
libdrm-2.4.96,1
libffi-3.2.1_3
libiconv-1.14_11
libidn2-2.1.0
libinotify-20180201_1
liblz4-1.8.3,1
libnghttp2-1.36.0
libogg-1.3.3,4
libpciaccess-0.13.5
libpthread-stubs-0.4
libraw-0.18.13_2
libressl-2.8.3
libsunacl-1.0.1
libtasn1-4.13_1
libtheora-1.1.1_7
libunicode-0.4_11
libunistring-0.9.10_1
libunwind-20170615
libva-2.4.0
libva-utils-2.3.0_2
libvorbis-1.3.6,3
libx264-0.155.2917
libxcb-1.13.1
libxml2-2.9.8
libxshmfence-1.2_4
libzvbi-0.2.35_3
lzo2-2.10_1
mesa-libs-18.3.2
mono-5.10.1.57_1
nettle-3.4.1_1
opus-1.3
p11-kit-0.23.15
pciids-20190120
pcre-8.42_1
perl5-5.28.1
pixman-0.34.0_1
pkg-1.10.5_5
png-1.6.36
popt-1.16_2
py27-dnspython-1.15.0
py27-iso8601-0.1.11
py27-pillow-5.2.0
py27-setuptools-40.6.3
python27-2.7.15
python36-3.6.8
readline-7.0.5
samba48-4.8.7
sqlite3-3.26.0
talloc-2.1.14
tdb-1.3.16,1
tevent-0.9.37
tiff-4.0.10
tpm-emulator-0.7.4_2
trousers-0.3.14_2
webp-1.0.2
xcb-util-0.4.0_2,1
xcb-util-renderutil-0.3.9_1
xorgproto-2018.4
  • Like 1
Link to comment
Share on other sites

@@makarai I think it works for you because you installed it from package that have dependencies with X or Wayland that's why you have libva-x11.so

I install from ports and always uncheck all options that concern X or Wayland because i don't need it, i don't have any desktop on the server.

Do you think, it will break something if the lib that come with the emby package doesn't have the dependency on X ? (for me all is good)

Link to comment
Share on other sites

metsuke

We may have to see if any of our install instructions require changes with FreeBSD 12.

That could be. I'll try the install from scratch using ports, then packages and diff the results.

Link to comment
Share on other sites

I've tasked this to our build developer to see if any adjustments to our FreeBSD package are needed for FreeBSD 12. Thanks guys.

  • Like 1
Link to comment
Share on other sites

alucryd

@@bernux Our beta packages are built on an unmodified binary freebsd release (currently 11.2) as it it the quickest and most convenient on our environment. Our FreeBSD VM runs on top of an already virtualized Linux server and has no hardware acceleration whatsoever. This means building anything from the ports tree takes hours, if not days for the most hardcore packages (*wink *wink llvm). As such our ffmpeg is built only once and repackaged as is in all the beta packages. Unfortunately this means that you will need all libraries present in the binary packages, including libva-x11.

 

However, our stable package which will soon be merged in the ports tree operates differently and builds everything from source. Once it is merged, you will be able to build it locally and enjoy a completely X-less system.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...