reg4arz
Posts: 1
Joined: Sun Oct 30, 2016 10:24 am

Minidlna Discovery Problem

Sun Oct 30, 2016 10:27 am

I've installed MiniDLNA on my RaspberryPi2 using the official package.

It gets never detected by DLNA devices. It appears for a really short time and then disappears.
If I am lucky, I can enter the files selection within my app and from there everything works fine... But if I exit from file selection and get into "DLNA server selection" view, the server is present no more.
I looked for error messages but nothing... I hope that somebody can help me.
I can provide all configurations and log files that are needed.

Here's my minidlna.conf file

Code: Select all

# This is the configuration file for the MiniDLNA daemon, a DLNA/UPnP-AV media
# server.
#
# Unless otherwise noted, the commented out options show their default value.
#
# On Debian, you can also refer to the minidlna.conf(5) man page for
# documentation about this file.

# Specify the user name or uid to run as.
user=pi


# Path to the directory you want scanned for media files.
#
# This option can be specified more than once if you want multiple directories
# scanned.
#
# If you want to restrict a media_dir to a specific content type, you can
# prepend the directory name with a letter representing the type (A, P or V),
# followed by a comma, as so:
#   * "A" for audio    (eg. media_dir=A,/var/lib/minidlna/music)
#   * "P" for pictures (eg. media_dir=P,/var/lib/minidlna/pictures)
#   * "V" for video    (eg. media_dir=V,/var/lib/minidlna/videos)

media_dir=/home/pi/share




# Path to the directory that should hold the database and album art cache.
db_dir=/home/pi/.minidlna

# Path to the directory that should hold the log file.
log_dir=/var/log

# Type and minimum level of importance of messages to be logged.
#
# The types are "artwork", "database", "general", "http", "inotify",
# "metadata", "scanner", "ssdp" and "tivo".
#
# The levels are "off", "fatal", "error", "warn", "info" or "debug".
# "off" turns of logging entirely, "fatal" is the highest level of importance
# and "debug" the lowest.
#
# The types are comma-separated, followed by an equal sign ("="), followed by a
# level that applies to the preceding types. This can be repeated, separating
# each of these constructs with a comma.
#
# The default is to log all types of messages at the "warn" level.
log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=debug

# Use a different container as the root of the directory tree presented to
# clients. The possible values are:
#   * "." - standard container
#   * "B" - "Browse Directory"
#   * "M" - "Music"
#   * "P" - "Pictures"
#   * "V" - "Video"
# If you specify "B" and the client device is audio-only then "Music/Folders"
# will be used as root.
#root_container=.

# Network interface(s) to bind to (e.g. eth0), comma delimited.
# This option can be specified more than once.
#network_interface=

# IPv4 address to listen on (e.g. 192.0.2.1/24).
# If omitted, the mask defaults to 24. The IPs are added to those determined
# from the network_interface option above.
# This option can be specified more than once.
#listening_ip=192.168.1.0/24

# Port number for HTTP traffic (descriptions, SOAP, media transfer).
# This option is mandatory (or it must be specified on the command-line using
# "-p").
port=8200

# URL presented to clients (e.g. http://example.com:80).
#presentation_url=/

# Name that the DLNA server presents to clients.
# Defaults to "hostname: username".
friendly_name=RASPBERRYPI

# Serial number the server reports to clients.
# Defaults to 00000000.
serial=681019810597110

# Model name the server reports to clients.
model_name=Windows Media Connect compatible (MiniDLNA)

# Model number the server reports to clients.
# Defaults to the version number of minidlna.
#model_number=

# Automatic discovery of new files in the media_dir directory.
inotify=no

# List of file names to look for when searching for album art.
# Names should be delimited with a forward slash ("/").
# This option can be specified more than once.
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg

# Strictly adhere to DLNA standards.
# This allows server-side downscaling of very large JPEG images, which may
# decrease JPEG serving performance on (at least) Sony DLNA products.
#strict_dlna=no

# Support for streaming .jpg and .mp3 files to a TiVo supporting HMO.
enable_tivo=yes

# Notify interval, in seconds.
notify_interval=30000

# Path to the MiniSSDPd socket, for MiniSSDPd support.
#minissdpdsocket=/run/minissdpd.sock

Thanks in advance.

amilino
Posts: 42
Joined: Fri Feb 05, 2016 6:01 pm

Re: Minidlna Discovery Problem

Sun Jan 13, 2019 10:32 pm

I have the same issue. Maybe it is Android related. I am trying to connect with my Android S9. Any feedback would be great.

User avatar
default_user8
Posts: 599
Joined: Mon Nov 18, 2013 3:11 am

Re: Minidlna Discovery Problem

Sun Jan 13, 2019 11:55 pm

Stop using minidlna and start using plexmedia server with the dlna server enabled.
Two heads are better than one, unless one's a goat head.

amilino
Posts: 42
Joined: Fri Feb 05, 2016 6:01 pm

Re: Minidlna Discovery Problem

Mon Jan 14, 2019 7:04 am

Just tried and Plex also doesn't work. I also have Kodi installed and there is also dlna and it doesn't work. Looks like a hardware issue?

User avatar
default_user8
Posts: 599
Joined: Mon Nov 18, 2013 3:11 am

Re: Minidlna Discovery Problem

Mon Jan 14, 2019 7:16 am

Did you just install plex and kodi or did you start from scratch with a fresh flash of raspbian? If not you might want to try and start all over with a fresh flash of raspbian. I run plex media server from a nextcloudpi image and have no issues.
Two heads are better than one, unless one's a goat head.

amilino
Posts: 42
Joined: Fri Feb 05, 2016 6:01 pm

Re: Minidlna Discovery Problem

Mon Jan 14, 2019 7:21 am

No, I don't want to start from scratch. But last time I did it I installed Raspbian Stretch so it was quite recently.

If I enable dlna on Kodi it will appear on the network but then after few seconds it disappear. If I manage to open it on my Android phone, I can also play videos and everything works from there. The problem is that next time when I want to connect I always have to disable and enable service in Kodi to be able to quickly connect on it. Log files are also looking fine.

Return to “Media centres”