Print

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

[Dmytro]

Searched the forum, but could not find a solution.

Auto-import spends about 4-5 minutes 'Adding files to the library' for c. 2600 files each time I rerun it. Nothing unexpected is imported in the end, and the report shows a list of about 400 files previously deleted from the library.
Has anyone noticed such a thing? Not a problem per se, just annoying to wait each time I need to import 2-3 new albums.

'Ignore files previously deleted from the library' is ticked.
Most of my music has .cue files.

[blgentry]

I would start by moving those 400 files "previously deleted from the library" to a location where MC does not try to auto import them each time.  That should eliminate at least 400 "tries" for each run.    Then see what happens from there.

Brian.

[Dmytro]

Thanks, Brian

I have changed the extension for all the 'previously removed files' to .file (so that MC does not 'see' them anymore) and rerun the AutoImport twice (logged the second one). Same thing - MC was 'importing' c. 2600 files for about 6 minutes each time and imported nothing.

[Well not exactly - each time the report showed 14 duplicated files (with '1' added to the end of the filename), for the cases where albums contained a single track with the same name as the album name. No duplicates actually appear in the library. I assume it is a separate thing.]

Unfortunately, the log is too big to be attached (even compressed) - about 181,000 rows. I have included a random sub-sample (the log looks quite uniform) below:

[blgentry]

Hmm.  I looked at your log.  The Metallica tracks that are shown there appear to be adding to the library in a normal way.  Well... at least as far as I can tell.  But I'm no expert on reading the MC logs.

So... are these tracks in your library?  Does MC add them again each time auto import runs?  I'm not sure why it would show as adding to the library if it was not.  Perhaps someone with more detailed knowledge of the logs could read this and know more about what's really going on.

Let me ask this:  What has changed on your system since you noticed this problem?  Have you moved music files around?  Added a NAS and moved files there?  Changed something else?

Brian.

[marko]

The one's with the "1" at the end will be, I'm almost certain, from the .cue files.

If most of your music has accompanying cue files, I would suggest removing the .cue file extension from your auto import rules (unless of course, you really really need them in your MC library?

-marko.

[blgentry]

I've never quite figured out what MC exactly does with CUE files.  I've read lots and lots of problems with them here, but haven't figured out how it works.  Can CUE files be made to work properly with MC? 

Brian.

[Dmytro]

Thanks both, this has been very helpful.

Hmm.  I looked at your log.  The Metallica tracks that are shown there appear to be adding to the library in a normal way.  Well... at least as far as I can tell.  But I'm no expert on reading the MC logs.

All these files are already in the library, so MC just does some 'empty' steps.

The one's with the "1" at the end will be, I'm almost certain, from the .cue files.

If most of your music has accompanying cue files, I would suggest removing the .cue file extension from your auto import rules (unless of course, you really really need them in your MC library?

This turned out to be correct - after disabling the cue files, MC's Auto Import now works like a charm - runs in seconds. Now I understand where the ~2600 is coming from - this is roughly the number of albums (i.e. .cue files) in my library.
Looks like some bugs/limitations in MC's .cue import implementation.

However...
After testing the outcome I have found a few instances, where cd's were ripped as single image files, not separate tracks. MC now does not 'see' the tracks inside. I believe there are not many such cases in my library (I have sorted everything by duration and spot-checked a few), so maybe it is not a big deal, but not ideal. Often it is hard to split such images when they are non-Red Book PCM (I have a few hi-def vinyl rips and some 24-bit editions etc.).

Do you have any suggestions on the best file splitter? I am normally using CueTools , and it does it perfectly but does not support non-Red Book PCM.

[marko]

Glad we're getting somewhere for you...

Re. cue splitters... I've not needed to do so in a long while now, but Medieval Cue Splitter always worked a treat for me...

http://cue-splitter.medieval.it/

[Awesome Donkey]

I actually would recommend avoiding Medieval Cue Splitter, as it's known to cause sector boundary errors (SBEs) when splitting tracks. I highly recommend CUETools instead, which doesn't cause SBEs.

[Dmytro]

Thanks All - upon closer inspection, it was only two albums which required splitting, so I decided I can live with it.

But.. after disabling *.cue files in the import settings, I got a whole lot of duplicate tracks in my library (about a 100). All of them track #1. Is there any easy way to get rid of these duplicates?