Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
→DLNA Configuration File
Working page for [http://www.amahi.org/apps/dlna Amahi DLNA], the Amahi port of [http://sourceforge.net/projects/minidlna/ MiniDLNA]. It makes your Amahi HDA the best media server for all your clients.
What is DLNA? '''[http://www.dlna.org/ Digital Living Network Alliance ]''' (DLNA) is a non-profit organization responsible for defining interoperability guidelines to enable sharing of digital media between multimedia devices. The guidelines are built upon existing public standards.
__TOC__
=== Tips ===
<blockquote><u>Fedora 19:</u></blockquote> /etc/minidlna.conf <blockquote><u>Ubuntu:</u></blockquote>
/etc/minidlna.conf
friendly_name=Amahi Media Server '''<============================================ set DLNA server name'''
* It has some Some Tivo supportcan be enabled.* It picks up new files added automatically (as opposed to uShare).<br>* Check the '''log file''' for the app at:
<blockquote><u>UbuntuFedora 19:</u></blockquote> systemctl restart minidlna.service ==== DLNA Log File ==== Check the '''log file''' for the app at: <br><br><blockquote><u>Fedora 19:</u></blockquote>
/var/log/minidlna.log
<blockquote><u>Ubuntu:</u></blockquote>
/var/log/minidlna.log
==== New Media Files ====
DLNA picks up new media files added automatically (as opposed to uShare).
<!--* <del>You need the two RPMFusion apps installed before this one for things to work.</del> not needed any more-->
=== Troubleshooting ===
==== Ownership/Permissions Issues ====
* If you have problems where DLNA cannot see some files, it may be due to some ownership/permissions issues. You can do this (change the path and USERNAME accordingly):
'''NOTE:'''<br> Some Amahi applications that share the same media files require specific ownership/permissions to media directories and files.
In the case of Fedora the following could apply:
==== DLNA Not Running After Boot-Up ====
This problem may occur on "some" systems after Amahi 7 starts ( see Amahi Dashboard: Setup > Settings > Servers).
* As a "root" user start a "Terminal Session", at the command-line enter:
<blockquote><u>Fedora 19:</u></blockquote>
systemctl status minidlna.service
<blockquote>Response:
<pre>minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Sat 2013-08-10 08:46:45 MDT; 16min ago
Process: 527 ExecStart=/usr/sbin/minidlna -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid (code=exited,
status=255)</pre>
* Also somewhere in the "messages" log reveals:
Aug 10 09:20:28 localhost minidlna[526]: [2013/08/10 09:20:28] minidlna.c:753: fatal: No IP address automatically detected!
* What does all this mean? When DLNA starts it automatically expects to retrieve the Amahi servers' IP address. DLNA could not get the address as the network services on the server had not yet completed start-up and configuration.
* A "systemctl" command can be entered based on the following description:
Enable NetworkManager Wait Online
If you have services which fail if they are started before the network is up, you have to use
NetworkManager-wait-online.service in addition to the NetworkManager service. This is however
hardly ever necessary since most network daemons start up fine, even if the network has not been
configured yet.
* To enable NetworkManager Wait Online at startup with the following command:
<blockquote><u>Fedora 19:</u></blockquote>
systemctl enable NetworkManager-wait-online
* Enter the following to ensure that DLNA is enabled to start at each system boot:
<blockquote><u>Fedora 19:</u></blockquote>
systemctl enable minidlna.service
* If this was the problem encountered, on the next system boot DLNA should be running.
==== Other Stuff ====
* If you installed too early, uninstall DLNA, uninstall RPM Fusion (Non-free) and RPM Fusion, in that order, refreshing each time the available apps page in your HDA.
* If you suddenly realize that ONLY a part of your library is delivered by your amahi-dlna server to your clients you (most probably) have add added a file to the library that forces dlna daemon parser to crash. Check [http://forums.amahi.org/viewtopic.php?f=19&t=3816 this] out if this is the case.
=== DLNA Players ===
Working, no changes are needed, by default a server called Amahi appears in the list of the home menu.
==== Roku ====
The Roku Media Player (RMP) is a Roku Device app that can be installed easily via smartphone. There is no server side installation. The sole installation is of the app on the Roku device. Once installed, the RMP appears as just another "channel" on the Roku device, and, once invoked, the RMP makes all HDA shares visible. Any suitably formatted videos contained therein are playable via the Roku device. No real difficulty in getting all this to work quickly. (One proviso: I already had miniDLNA installed and I did not try confirm whether the RMP is somehow piggy backing off of the existing MiniDLNA setup (including the settings in the miniDLNA configuration file), or, whether the RMP's functioning is not dependent on the miniDLNA setup.)
=== FAQs ===
* Q: Does it transcode on the fly while streaming?: Nope
* Q: I added additional share locations into the config file but they do not appear!: try removing files.db under /tmp/minidlna/ and restarting the amahi-dlna service
