Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fallsroad]

I'm running Media Center 19, upgraded from 18.

After adding files to my watched folders and running the import function, the total number of files available to play does not increase.

Example. Add 200 new flac files to my main music directory, open MC, run import, then try to play all the files in random playback. Selecting all in the playlist window reveals a count identical to the number of tracks prior to import. A search for the specific music files turns up nothing, though the import details tell me 200 new files were successfully imported.

[MrC]

Go to the Recently Import playlist.  Determine if the Media Type is Audio (it should be).  From there, also, check that the Album name and Artist names are as you expect.

[fallsroad]

Go to the Recently Import playlist.  Determine if the Media Type is Audio (it should be).  From there, also, check that the Album name and Artist names are as you expect.

Weird. The new files display and play if I go to the Recently Imported playlist. Artist and album names appear as expected. I tag everything new the same way before moving the files into the music directory and importing to MC.

But if I clear Playing Now, then double click to play all files in the library, those recent ones are not found and the overall file count remains what it was prior to import.

[MrC]

The views organize the files according to the tags.  If the files imported, and were not determined to be bad, you'll find the files under the appropriate place, depending upon the views.

In the Audio > Panes, sort the files in the file list below by Filename (click the Filename column, and select the Temporarily remove grouping option).  Scan the Filename column for those files.  Alternatively, enter enough of the full path into the Search box (or Search Wizard) to distinguish the files from others.

Do you find the files?  Is it possible you had added the files previously?

[fallsroad]

The views organize the files according to the tags.  If the files imported, and were not determined to be bad, you'll find the files under the appropriate place, depending upon the views.

In the Audio > Panes, sort the files in the file list below by Filename (click the Filename column, and select the Temporarily remove grouping option).  Scan the Filename column for those files.  Alternatively, enter enough of the full path into the Search box (or Search Wizard) to distinguish the files from others.

Do you find the files?  Is it possible you had added the files previously?

Files were newly ripped so they could not have been imported previously. I removed and added them several times, and the total files count remained the same, and searching by Artist or Album Artist did not return any of the files in question. I sorted them as you suggested and also could not find them listed.

I cleared the entire library and reset the import locations and options. The "analyzing audio" part will take another day to complete, but the files count is now correct and the files in question are readily found by any relevant search term.

Perhaps some sort of database error?

[MrC]

I doubt this was a database error.

You say they were newly ripped so they could not have been already imported.  This may not be true.  If you ripped the tracks to an auto-import directory, they would have been imported.  And when you rip with MC, they are always imported.  Since I don't know exactly what you did, I can't say what happened.

You also say you remove and added them several times.  This is telling, as MC maintains a list of files that you've removed, so that a) MC doesn't try to re-auto-import them, and b) so that when you manually re-import them, MC doesn't have to read all the tags, but instead can just pull the entries from the Removed database.  Auto-import won't re-import files, by default, that you've manually removed.

If you want to work manually the way you are, you're probably going to want to learn some things work, such as Auto-Import and how it differs from manual imports, what happens when you remove files, and how MC goes about updating its database of tags when tags externally are changed.

You might just consider ripping in MC, tagging in MC, and living in MC unless there is a very good reason otherwise (and you understand the interactions of your external processes and MC).

[fallsroad]

I doubt this was a database error.

You say they were newly ripped so they could not have been already imported.  This may not be true.  If you ripped the tracks to an auto-import directory, they would have been imported.  And when you rip with MC, they are always imported.  Since I don't know exactly what you did, I can't say what happened.

You also say you remove and added them several times.  This is telling, as MC maintains a list of files that you've removed, so that a) MC doesn't try to re-auto-import them, and b) so that when you manually re-import them, MC doesn't have to read all the tags, but instead can just pull the entries from the Removed database.  Auto-import won't re-import files, by default, that you've manually removed.

If you want to work manually the way you are, you're probably going to want to learn some things work, such as Auto-Import and how it differs from manual imports, what happens when you remove files, and how MC goes about updating its database of tags when tags externally are changed.

You might just consider ripping in MC, tagging in MC, and living in MC unless there is a very good reason otherwise (and you understand the interactions of your external processes and MC).

The tracks were ripped by dbpoweramp to a separate drive. I have a solid grip on how it interacts with MC - it doesn't directly, and I rip and tag the same way most times.

I've always used auto import and understand how it functions. Something went wrong while adding these albums to the auto import directory, so I resorted to trying to import them manually. I've been using MC for a while and never experienced this issue before, and it certainly could be user error. I have two other libraries I use in MC and neither of them experienced this issue.

In any case, it appears that clearing the library and resetting the import parameters has solved it. And you are probably right about using MC to rip and tag everything. I've been using dbpoweramp for years, but only came to MC in version 17. Old habits die hard.