[SOLVED] DLNA server on Slackware-current

I need to install DLNA server on a Slackware-current.

Searching for existent solutions, all are pretty old. AlienBobs for instance 7 yeaars, readymedia 3 years..

Any suggestions? I need to serve media files to new SmartTV.
It must be Slackware box, as I use it as a video surveillance and data server for family.

I use Universal Media Server for this. Java based.

Plex Media Server has a DLNA server option.

I've tried both UMS and Plex out and stuck with the latter, which has been running on my media server (slackware, of course) for the last 5 years or so. Both are accessible over DLNA but you can also install the free plex app on a SmartTV which has a nicer interface for sorting, and looking through content with metadata as well. Just takes an overnight scan of the files to index and gather metadata and then it runs smoothly after that.

I run Kodi which has UPnP(aka DLNA) and I like it. Have you thought about a Raspberry Pi type device as a media server? This thread discusses using slackware arm and kodi: LQ_4175647585

Thanks all for the suggestions.

I've compiled/installed minidlna-1.2.1 and my new smart TV found it and show all media files.
Very minimalistic and simple to install.

FYI the main reason for picking UMS over something like minidlna is that UMS is able to mux the movie file together with a separate subtitle file and stream that combo to the television.
I am not a native english speaker so I want a subtitle with the movies I watch. This is easy when you stream a movie off a local disk but is otherwise impossible when your source is a DLNA (UPnP) server.

TIL people actually use DLNA...

Originally Posted by rkelsen TIL people actually use DLNA...

I used it about 8-10 years back. At the time, I didn't have a dedicated media center computer, so I shared my media on my computer to my xbox via Serviio. It wasn't too bad except the 360 was pretty limited on what formats it could play back and to transcode to wmv, it was limited to 1 core (I only had a dual core at the time).

Now I have all my media shared via NFS (started with samba, and that protocol is not very efficient for streaming) and I have a dedicated media center on an AMD Ryzen APU running about a year old version of -current (needed -current for hardware support) and kodi as the frontend. I'd hate to go back to DLNA again after getting used to the smooth interface of kodi. #FirstWorldProblems

Originally Posted by 0XBF I've tried both UMS and Plex out and stuck with the latter, which has been running on my media server (slackware, of course) for the last 5 years or so. Both are accessible over DLNA but you can also install the free plex app on a SmartTV which has a nicer interface for sorting, and looking through content with metadata as well. Just takes an overnight scan of the files to index and gather metadata and then it runs smoothly after that.

Also have Plex running on my Slackware server.
As we have plex Pass, my son did an auto update tool for plex : https://www.linuxquestions.org/quest...-a-4175671357/

I just saw he wrote AMD64, will ask him why as it's an Intel processor ^^"

hth,

Originally Posted by Patrick59 I just saw he wrote AMD64, will ask him why as it's an Intel processor ^^"

Maybe he's referencing that it's AMD's 64bit instruction set architecture (ISA), called AMD64. This is now commonly called x86_64, but it's what AMD introduced back in the early 2000s for 64bit computing in the consumer realm. You will frequently see amd64 used in reference to the 64bit/x86_64 instruction set. Debian uses amd64 to reference 64bit packages (Slackware uses x86_64), so if your son has a Debian/Ubuntu background, that could be the reason for the reference.

History lesson time...

Back when 64bit processors were getting ready to come to the market AMD and Intel were each pushing their own architecture. AMD was developing AMD64, which was an extension of the x86 architecture (which was originally developed by Intel and had 16bit and 32bit support -- some of the 32bit versions have familiar names like i586 and i686) while Intel was developing IA-64, which was a completely new architecture (and was ultimately deployed on their Itanium products, which had their last chip ship in 2017 and is now discontinued). Both required different support from the various OSes and Microsoft eventually chose to support AMD64 in the consumer versions of Windows. Intel eventually decided to abandon their IA-64 in the consumer market and implemented x86_64/AMD64 under various codenames, most notably EM64T and Intel 64.

Little late post..
There is a new version of ReadyMedia miniDLNA 1.3.0 from 25th nov. 2020, with a patch it compiles on a current Slackware64-current.

The main huge difference to UMP and others is in a name "mini":
minidlna-1.3.0-x86_64-1.txz - size 150K (kilobytes)
UMS-10.2.0-x86_64.tgz - size 144.5M (megabytes)
This is thousand times more!

So I'm very happy with tiny miniDLNA installed on my router (capable, serves also as a family movie server) and on slackware64-current.
Both deliver media to my Samsung smart TV.

I use jellyfin (just got a new version this week) and love it.
It has an app for android-tv (I have a xiaomi mi box 4s) and it is great.
Does trans-coding on the fly so it will always play in a format the android-box accepts.

EDIT: sorry, didn't notice thread age

miniDLNA , because it is well.. minimal, no java bullshit https://slackbuilds.org/repository/1...earch=minidlna