INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Ripping with MC causes duplicate entries, ripping with external program does not  (Read 1673 times)

greg.smalter

  • World Citizen
  • ***
  • Posts: 153

I have MC set up to use \\Ruby\Music for both its music file location and its auto import location. To my knowledge, MC doesn't know about the E:\Music physical path of the music.

If I rip a CD using Windows Media Center, auto import picks up the files in MC and everything works perfectly. If I rip the CD using MC, however, I get two library entries for every file. One \\Ruby\Music version and one E:\Music version. Why is this? What more can I do to make MC not know/care about the physical local path?
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.

Its not clear, but have you checked the folders listed under Tools > Auto-Import?
Logged
The opinions I express represent my own folly.

greg.smalter

  • World Citizen
  • ***
  • Posts: 153

All of the folders in auto-import begin with \\RUBY.
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.

Do you have Windows Media Center configured to auto-rip?
Logged
The opinions I express represent my own folly.

greg.smalter

  • World Citizen
  • ***
  • Posts: 153

Do you have Windows Media Center configured to auto-rip?
Yes, and it works great. After the rip, MC auto-import picks up the files automatically and there's only one library entry per file.
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.

I'm not sure I have any answers for you.

In quick testing I don't find a problem ripping to a network drive.  I do find that if I have WMC set to auto-rip, and then have MC rip, both will rip at the same time.  MC places its files in the network share as I've configured (like your settings), and WMC places its files where it is configured (don't know where yours are configured).

So I suppose the question is... where is WMC placing its auto-ripped files?  And is MC importing those files too?
Logged
The opinions I express represent my own folly.

greg.smalter

  • World Citizen
  • ***
  • Posts: 153

WMC is placing its ripped files in the same location that MC would put them if it ripped them (but I never have MC rip them because of the above problem). This workflow works fine. I'd like to be able to use MC to rip, though.

Also, the destination for MC, even though it is \\RUBY\Music, is actually local. But, I specify it using the network path because it helps out in a lot of other ways.

Another way of putting this is - how is it possible for a file added via MC to ever have its Filename field start with "E:\Music" if MC doesn't even know about that path? That's the real problem - it's true I happen to get two copies (one for \\RUBY and one for E:), but even if I just got one, and it was the E: one, it would be very bad.
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.

Dunno.  I think its clear *what* the problem is, but not *why* it is occurring.  What needs to be determined is how others can replicate it.  Otherwise, this will likely go unresolved.

Somewhere, there is a reference to the drive.
Logged
The opinions I express represent my own folly.
Pages: [1]   Go Up