More > JRiver Media Center 25 for Mac

Excluding data folders from auto library imports

<< < (5/5)

kane2:

--- Quote from: kane2 on June 25, 2019, 01:31:18 pm ---I saw this was asked for MC23, but never really addressed.

There needs to be a way to exclude specifically named data folders that can appear within the directory for a specific album. Many other programs create these folders, usually with specific names, and they purposely contain files that look like music but aren't.  The best way would be for MC to have a grep like exclude in the auto import list for a library.
So if the Music Directory is structured something like

~/Music/Artist 1/Album 1/

          Song 1
          Song 2
          Song 3
          Song 4
          Song 5
          Song 6
          data_folder/
          Pure Music Bookmarks/

~/Music/Artist 2/Album 2/

          Song 1
          Song 2
          Song 3
          Song 4
          Song 5
          Song 6
          data_folder/
          Pure Music Bookmarks/

Your auto import list could look like

~/Music/
--exclude "*/Pure Music Bookmark/*"
--exclude "data_folder"

so MC would ignore anything it finds in folders with these names (kind of how "rsync" works). On my computer EVERY ONE of hundreds of albums contain this kind of information. Unfortunately there is no scripting interface on the Mac and the Web Services Interface doesn't offer a way to remove a file from the library, just playlists.

Any ideas or help would be appreciated. Right now MC25 thinks every other track it found is a song, and it simply stops when it gets the fake data in these folders.

         Jeffrey

--- End quote ---

This same problem has come up again, this time with multiple versions of the same song. I would be happy to write a plug-in that allowed you to select whether or not a file was imported into the library, say importing only the high res version for one library and the lower if it wasn't available.  As I said below, there seems to be some kind of mechanism for this already within the program.  The API can be VERY simple. If anyone from JRiver can comment on this, I would be appreciative.

I also appreciate that RoderickGI proposed and thinks he has come up with a solution that works long term, but it doesn't, so please don't keep reiterating that particular solution. I program apps for a living, so I fully understand the amount of work that is required. This is a solution to a LARGE NAS storage that constantly has new music added; his solution requires continued ongoing manual maintenance, where a simple filter would take care of it once and for all.

Thanks for any help

Navigation

[0] Message Index

[*] Previous page