Bug 4490 - handling of tagging
: handling of tagging
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: unspecified
: All Windows XP
: -- enhancement (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-08 07:14 UTC by Max
Modified: 2011-11-06 23:24 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 Max 2006-11-08 07:14:31 UTC
Hi,

I would like to see an option to select the types of tags that are read by slimserver during scanning. As an example I have a few songs (borrowed from someone) that have ape tagging, and even some album art inside the files which I do not use. Removing all tags then, syncing back to idv1 and 2 is cumbersome. It might also improve performance when only one type of tag is actually read?

I personally also do not use tags such as lyrics, composer, comments, etc. Having the option of NOT scanning for this type of info might also improve scanning speed?
Comment 1 Chris Owens 2006-11-22 16:16:05 UTC
A good idea, although it seems unlikely it would improve scanning speed very much.
Comment 2 KDF 2006-11-22 20:00:18 UTC
is this not what this is for in 6.5.1: ?

DISABLED AUDIO FILE EXTENSIONS
SlimServer will look in the Music Folder for all supported file types (audio files and cue sheets). To disable specific file types from being processed when scanning the Music Folder, enter a comma separated list of file extensions below. E.g.: cue, mp4, aac

It is found under server settings->file types.

Please given 6.5.1 a try and let us know if that does what you need.
Comment 3 Max 2006-11-24 01:19:04 UTC
No this is not what I meant by this. If 'tweaking' the scan engine by adding user customization to which tags and fields are and aren't scanned does NOT improve scan speed or decrease database sise or whatever, so if there is no significant 'win' in this feature, then probably this request can be closed.
Comment 4 KDF 2006-11-24 01:38:46 UTC
yes, sorry.  the overhead is mostly in the access of the files, as opposed to the amount of tags being stored.  The server would still be stuck parsing all tags in order to differentiate the wanted and not wanted info. of course, there is some possible saving in memory use, and the time to add each tag.  Hard to say offhand how much that is without profiling. 

In all probability, simply using a good tag editor to clear out any tags that you don't want will offer the same benefits and maybe more as it doesn't require the overhead of new complexity of checking prefs in slimserver during the scan.  if tags aren't there, nothing is done.
Comment 5 Alan Young 2011-11-06 23:24:28 UTC
Unassigned bugs cannot have a priority.