Problem with duplicate DB entries when ripping CDs

by **Purkolator** » Sun Aug 15, 2004 4:49 am

Ok, I was wrong about that last point about when the db entries are created. I watched a few more songs get ripped and they seem to get entered at different times for each song.

as Emily Litella used to say... "never mind"

-Brad

by **Purkolator** » Sun Aug 15, 2004 4:42 am

Rusty,
Ok, you seem to be on the right track. I turned off file monitor, shut down MM, ripped a CD, opened MM, scanned my music folder for the CD I had just ripped and voila! no duplicate entries. So it does seem to be some issue with the file monitor.

I turned file monitor back on a tried ripping another CD and noticed that the duplicate filename (the one that looks like it has gotten truncated by DOS) does not get created until after the entire song has been ripped. The "correct" db entry is entered as soon as the file starts ripping.

Hmmm....

-Brad

by **purkolator** » Fri Aug 13, 2004 2:52 pm

purkolator wrote:well, I have to show my relative naivete here. I think I am on a TCP/IP network, but am not really sure. It is a simple home network with DSL modem running into a Soyo router. Just set up a home network with Windows.

Does that sound right for TCP/IP

I will give that a try tonight. Thanks!

Brad

by **Peke** » Thu Aug 12, 2004 7:15 pm

There is another way

The manual way. Start scanning newly formated Disk Stop it after few tracks. Opem MDB in Access Copy Serial From Newly added (Last one in medias Table) over desired Disk serial number. Load MM and delete newly added from Lib. All Songs that are rewritan in exact place before qFormat will be available and you will preserve statistic in MM.

by **jiri** » Thu Aug 12, 2004 5:23 pm

Yes, that's a good thing to do. Another way is to change SN back to the previous one using some tool (there are some free available).

Jiri

by **Lowlander** » Thu Aug 12, 2004 4:35 pm

Oh that is an interesting thing.

So after formating a drive one should do a locate moved/missing tracks (in case files were moved back)?

by **jiri** » Thu Aug 12, 2004 3:30 pm

MM works with drive's serial numbers, not labels. Serial number is newly generated when drive is formatted.

Jiri

by **munman** » Thu Aug 12, 2004 3:08 pm

Even though the Volume label of the disk is still 'USB160'?

I'm not sure what a quick format would have to do with that.

by **jiri** » Thu Aug 12, 2004 3:04 pm

It's clear then - quickformat caused a change in disk serial number. It's considered to be another device then and thus the old scanned tracks seems to be unavailable.

Jiri

by **munman** » Thu Aug 12, 2004 1:42 pm

Hi Rusty,

No, this is one external HD, and I had nothing on another HD.

Here's how it went:
- I copied my collection to the USB external HD. As I said, the Volume name for the external disk is USB160.
- I transported the external disk to work, and plugged it into my work computer (for a little listening music)

, and did and Add/Rescan of the external disk. Everything was fine at that point.
- Sometime later, I shut down the disk, took it home, and did a quick format of the external disk (I did not change the USB160 volume name). I then copied my latest (with many more tracks) collection back to the disk.
- I then reconnected the external disk again at work, and did a Add/Rescan of the new collection. That is when I began seeing the duplicates as mentioned above.

To remedy the situation, I did a Clear Library, and did a fresh Add/Rescan of the drive. This doesn't seem like it would be necessary though, if Add/Rescan worked like is is intended to.

I have only recently purchased MM, and have only used 2.2.2 version, so I can't say for sure about 2.2.

Hope this clarifies. Thanks for the help.

by **rusty** » Thu Aug 12, 2004 7:26 am

Munman,

From your post I was unclear on one thing:
-Do you have 2 harddrives attached to your system (i.e. did you at one time have the tracks on your internal HD, and then at a later time scan them from your external hard drive? If so the change in drive serial# would account for the duplicates.
-If not, is this problem new to the 2.2.2 series? or did it exist in MM 2.2 as well?

Thx.

-Rusty

by **Peke** » Thu Aug 12, 2004 5:25 am

Maybe You can try to add IPX/SPX protocol in network Connection and try again I'm almost sure that IPX/SPX is safer.

by **rusty** » Wed Aug 11, 2004 11:49 pm

purkolator,

Sounds like you're running TCP/IP. One other test that might be helpful:
-Whan happens if close MM completely, and then do exactly as you indicated (copy tracks to the PC), and then run MediaMonkey and perform the scan (no filemonitor)? Does the bug still occur?

-Rusty

by **Lowlander** » Wed Aug 11, 2004 8:59 pm

Does MM show to locations in the location node? (E and E[160]).

You could delete one entry and keep the other, just make sure you delete entries in DB only and not files on computer.

In the Add/Rescan dialog do you have the two options (E and E[160]) listed?

by **purkolator** » Wed Aug 11, 2004 2:20 pm

well, I have to show my relative naivete here. I think I am on a TCP/IP network, but am not really sure. It is a simple home network with DSL modem running into a Soyo router. Just set up a home network with Windows.

Does that sound right for TCP/IP

Problem with duplicate DB entries when ripping CDs

Post a reply

Expand view Topic review: Problem with duplicate DB entries when ripping CDs

Question for Munman

duplicate entries