Bug 1700 - Per-directory config file.
: Per-directory config file.
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: unspecified
: All All
: -- enhancement with 1 vote (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-21 07:04 UTC by Stuart
Modified: 2011-11-06 23:22 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart 2005-06-21 07:04:18 UTC
As the number of playback options increases (Shuffle play, Crossfading etc), the
need to default the settings for different types of media becomes all the more
important.

For example: An audio book, with Shuffle & Crossfading on, would be pointless. 
Likewise, with a live concert that has been indexed into separate tracks.

I propose we have an Apache style (.htaccess) config file that can be dropped
into a directory, that informs slimserver how the files, in that directory
branch are to be played.
Comment 1 KDF 2005-06-22 01:08:34 UTC
in principle, I like this idea.  But it needs to actually work, not just
functionally but actually be useful.

what I fear is yet another config file that the majority of users dont
understand, don't want to touch, but will be always upset about the wrong choice
of defaults.

to my mind, this is probably a great outside project that has a default of doing
nothing, but hooks in slimserver to use something if its there.  The implied
contract of dealing with features and update requests is a dangerous burden when
there is already a large demand on existing resources.

This might even be able to include the features requested in bug 479 or bug 541
Comment 2 Vidur Apparao 2005-06-30 13:52:32 UTC
Getting this one off the 6.1 radar.
Comment 3 Bjorn Ruud 2009-04-02 05:33:07 UTC
Per-directory config files is a good idea, and would be perfect for what I need. I keep new music in its own directory until I've had a chance to listen to it and have done cleanup on tags and filenames. This directory should be accessible by SqueezeCenter, but not scanned since I prefer to listen to these files by using the Browse Music Folder feature on my SqueezeBox until they are ready to be moved to the main archive.

I can think of several use cases for per-directory config files:
- Avoid scanning and inclusion in database, but leave files browsable.
- Exclude specific file types (from scan, browsing or both).
- Enable or disable playback options (like crossfade).
- Exclusion from playback options (shuffle).

Having this feature shouldn't confuse users since it's automatic, so those who don't need it won't have to deal with it.

The config file syntax should be kept simple, maybe something like this:

/Music/audiobook/.slim

# SqueezeCenter directory config file
[directory]
scan = False
exclude = *.cue

[playback]
crossfade = False
Comment 4 Alan Young 2011-11-06 23:22:47 UTC
Unassigned bugs cannot have a priority.