[Feature Request] Independent Scanning of Folders

[jfmus]

Hakko,

Was wondering if there was a way to set which folders are scanned and how often. Here is my basic problem. I have multiple folders that are scanned under Media Folders. Singles, Albums, New Albums, and Bootleg Recordings. Where I run into a problem, is that I do not want the Live Bootleg Recordings to be added into the playlists created from Last.FM. I only want studio releases to show up in the Genres, Radio, Top Tracks, Etc. In order to update the Newly Added Albums with Last.FM data, I have to do a full scan, remove the Boolegs, and add the New Albums. Then remove the New Albums, then do a local scan of the Bootlegs, then a local scan of the New Albums. This puts the newest albums into the Recently Added screen and removes the Bootleg Recordings from the playlists. Is there a better way, maybe a query that removes the entire folder from being used in the playlists? What would be perfect is the ability to check or uncheck a box next to each folder. Then when you do a scan it just scans the checked folder/folders. The auto scan would be nice if it did the same...being able to check which folders were auto scanned.

Also, is there a possibility of being able to add a dropdown with the Year in the left hand Artist column, the same way that the Last.FM genres are listed. This would be a simple way to see newly released Albums by Artists, or simply see Albums/Artists from any particular year.

Thanks again for the awesome mod. Been using it from the beginning, and have never looked back. Wish I had the right skills to help you out with the interface. Would volunteer in a heartbeat.

jfmus

[hakko]

There is a feature request from maxxh which I imagine would sort this out, mostly: viewtopic.php?f=11&t=10648

When last.fm returns top tracks, we only get names of songs, not albums. These names are matched against songs found in your local library and the first match is picked. The idea of maxxh is to try and choose the oldest available song in your library, which is then more likely the studio album. Also, I'm working on MusicBrainz integration right now, maybe that could be used too to identify studio albums over live albums, depending on how it works out.


I wish there was reliable information on which date all albums were published, but we normally only have year available. That means we cannot create a nice list of albums by release date. It's possible to get reports of "all albums released a certain year" (I did that recently from the database: )

Code: Select all

select a.artist_name_capitalization, ma.album_name_capitalization from library.album la inner join music.album ma on la.album_id = ma.id inner join music.artist a on ma.artist_id = a.id where year = 2012 order by a.artist_name;

But such lists are only useful at the end of the year (in January you're still interested in late releases from 2011). So I think that the "Recently added" view still fits the purpose of finding new albums better than grouping them by year (if you didn't have to add and remove folders, that is).

[jfmus]

Hakko....This is not exactly what maxxh is requesting. I agree that the oldest track will most likely be the studio release and should be pulled first. In dealing with my bootleg recordings, I want them to be scanned and available in the library, but not use the Last.FM data and therefore be included in the genre, radio, and top track playlists. I have my studio releases and my live recordings in different folders. I do a full scan of the studio releases first, and a local scan of the live recordings second. Here is where the problem arises. When I add new studio albums, I want to be able to add new studio recordings, but not add the Last.FM data to the live bootleg recordings. Once the folder is added, all folders are scanned. Un-checking the Enable check box does not seem to do anything. The only way to not scan a folder once it is added, is to delete it. What would be nice is if you could check or uncheck the box of the folder you want to scan or don't want to scan, save it, then select the depth of the scan (offline, normal, full). This would allow for shorter scan times as well, since you are only scanning part of a collection, instead of the entire thing. Prior to the tag based structure, if my memory is correct, this is how it acted. You could disable a folder, do a scan, then re-enable the folder. This is definitely not high priority, but I am trying to figure out the easiest way to have the best of both worlds, Live Bootleg Recordings and Studio Recordings existing in the same database.

As far as the year issue goes, pulling actual year data from Last.FM would definitely be a mess. I was referring to using the actual ID3 YEAR tag that is embedded in the files. Not sure this is possible based on the structure of the database, but wanted to clarify.

Thanks again,

jfmus