More > JRiver Media Center 29 for Linux
Docker Images for MC29
Hendrik:
It seems like the encoder will need some fixes for newer drivers, I'll get that into the next update.
We support encoding h264 in hardware, and decoding should cover basically all modern consumer codecs. mpeg1/2, h264, hevc, vp9, and av1, availability may depend on your hardware.
max096:
--- Quote from: Hendrik on June 20, 2022, 01:06:36 am ---It seems like the encoder will need some fixes for newer drivers, I'll get that into the next update.
We support encoding h264 in hardware, and decoding should cover basically all modern consumer codecs. mpeg1/2, h264, hevc, vp9, and av1, availability may depend on your hardware.
--- End quote ---
Seems to be working now. I'll come back to this a bit later though. Kinda want to get the new images "workable" first.
I'm a bit confused about the ffmpeg thing. Because the version of ffmpeg that is currently installed from the debian repository does not include any nvidia codecs at all. But it still seems to work without them anyways. Going back to earlier releases of MC there are also patchnotes that note that ffmpeg has been updated to version x.xx. Suggesting that MC ships with it's own ffmpeg. Yet, if I do not install ffmpeg it does not work at all. I guess it might download it like chromium, but misses some dependencies to run it?
Hendrik:
We ship our own FFmpeg, indeed. It has some (common) system-level dependencies like gnutls and libva1, but we should have documented those in the debian package I think. Its likely those get pulled in when you install the system-level FFmpeg.
Ideally you could run "ldd" on our FFmpeg libraries to see if anything system-level is missing that either we need to put into the debian control file, or you need to add to the image.
HaWi:
Just updated my docker MC29 via Portainer, and pulling the "latest" image I got 29.0.64 when I was expecting 29.0.66. Did I do something wrong?
Many thanks for any help
Hans
max096:
--- Quote from: HaWi on July 03, 2022, 12:30:51 pm ---Just updated my docker MC29 via Portainer, and pulling the "latest" image I got 29.0.64 when I was expecting 29.0.66. Did I do something wrong?
Many thanks for any help
Hans
--- End quote ---
Not sure whats up but latest still gives you 29.0.64. Either it's was not in the MC repos (but I don't think so because it ran yesterday). Having similar issues with the new image when I push a new image it still seems to give me an image from 2 days ago when pulling it afterwards.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version