/etc/minidlna.conf format for media_dir directive

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Edit manually /etc/minidlna.conf
2. Add media directories in format: "media_dir=V,/mnt/md0/Videos" where "V" is 
to specify this folder contains videos.
3. Save the file and try to restart MiniDLNA

What is the expected output? What do you see instead?

Even thought the ALT-F Web ui does not let specify which media type each 
directory is, I would expect the init.d script to recognize the format is 
conform and to still be able to start the daemon.

Instead, I get error message:

minidlna: Share V,/mnt/md0/Videos does not exists, disabling it.
minidlna: can't be started, no shares are configured.

What version of the product are you using? On what operating system?

ALT-F B7 with minidlna 1.0.19 

Please provide any additional information below.

It is just in my view an incorrect parsing and verification of the media_dir 
value. It takes the "V," as part of the path which it should not.

Original issue reported on code.google.com by baril...@gmail.com on 27 Apr 2011 at 10:33

[GoogleCodeExporter]

Is there any advantage to minidlna to specify the media type? It is optional.

Before launching minidlna, media directories are checked for existence, because 
minidlna (or at least the version I first test with) freezes if a specified 
directory does not exists.

Original comment by whoami.j...@gmail.com on 28 May 2011 at 3:02

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Well, I cannot say for sure because I'm new to dlna server and as such never 
saw how it should work when properly configured.

But, what I think I understand and see is that in a dlna *player* wheter you 
choose video, audio, or pictures in the menus, you are not really entering that 
specific media directory, you are entering the "root" of the dlna server, so 
you are again presented the choice of video, audio or pictures because the type 
of media in those directories could not be detected and mapped correctly to the 
menu associated to a specific media.

What I think is if we can specify in the dlna server which directory contains 
which type of media, then in the player, when choosing video in the menus, you 
will directly enter the video directory because the server knows that this 
directory contains video.

So, what I think is the problem/solution is that the lauching script should 
have a regular expression that permits V, or A, or P, just before the path and 
then sends the appropriate command when lauching the server.

Original comment by baril...@gmail.com on 28 May 2011 at 3:34

[GoogleCodeExporter]

Can you add the media information to the /etc/minidlna.conf configuration file 
and invoke minidlna directly, just typing 'minidlna' on the command line 
(without the quotes) and see if you notice any differences in the players you 
have?

Thanks

Original comment by whoami.j...@gmail.com on 31 May 2011 at 1:39

[GoogleCodeExporter]

fixed in my sources, thanks

Original comment by whoami.j...@gmail.com on 16 Jan 2012 at 5:42

• Changed state: Fixed