jEmplode bugger - v47

Posted by: loren

jEmplode bugger - v47 - 16/12/2003 00:12

Another import bug. It won't import a song because it says it's a dupe, when it most definitely isn't. The file names are as follows:

14 - Refusing to Be a Man.mp3
13 - Refusing to Be a Man (Different Studio Version).mp3

and the ID3 tags reflect those names in the title tag. It's not importing the second track... #13. Any idea why? I think the dupe checking isn't smart enough, if the tracks are similar, the last check should be file length or size. If they are different, they aren't dupes. This has happened on another album, i just didn't whine about it. =]

Thanks!
Posted by: mschrag

Re: jEmplode bugger - v47 - 16/12/2003 09:13

Can you put those somewhere where I can grab them? Deduping only looks at the musical content (tags are ignored) ... Is it possible that the tune is the same but it just differs in tags, or are you saying the actual content of the song is different too? If they just have different tags, then this is behaving "correctly". However, it is a known issue (and sort of tricky to resolve) that if you have the identical song in two albums that it will detect the second as a dupe.

ms
Posted by: loren

Re: jEmplode bugger - v47 - 16/12/2003 12:31

I'll double check tonight, but i'm pretty sure they were of a different length. Thanks Mike.
Posted by: mschrag

Re: jEmplode bugger - v47 - 16/12/2003 12:36

It would be important to know if they are different lengths because of tag differences only or different sizes because of music content. I can tell pretty fast by running them through some testcases I have, I think.

ms
Posted by: matthew_k

Re: jEmplode bugger - v47 - 16/12/2003 19:25

Is there any way to handle duplicates automatically, so that when a duplicate is encountered a link is just made to the tune that's already on the empeg?

Matthew
Posted by: mschrag

Re: jEmplode bugger - v47 - 16/12/2003 20:00

It should do that if you're importing into normal playlists (as opposed to soups, where it couldn't really make a link anywhere). The problem Loren's talking about is that the same song is in two different albums, which would mean the same tune would have to have two different source tags.

ms
Posted by: wfaulk

Re: jEmplode bugger - v47 - 17/12/2003 09:12

Actually, he's got two different tracks (different recordings of the same song, albeit) with similar names on the same album that are being seen as duplicates.
Posted by: peter

Re: jEmplode bugger - v47 - 17/12/2003 09:23

Actually, he's got two different tracks (different recordings of the same song, albeit) with similar names on the same album that are being seen as duplicates.
Does Jemplode tell you which song it's found a duplicate of, or are we all just assuming it's track 14 of that album which causes track 13 to be described as a duplicate? Loren, could it be that you have exactly that version of the song already elsewhere, as a B-side or something?

Peter
Posted by: mschrag

Re: jEmplode bugger - v47 - 17/12/2003 09:42

Unfortunately it doesn't say in the UI, but it MAY say that in the debug output if the debuglevel is high enough ... I'll check and if it doesn't, I'll add that in and do a new build.

ms
Posted by: loren

Re: jEmplode bugger - v47 - 17/12/2003 11:06

Bitt, actually they are on different albums.

Peter, good question... but those are the only two songs of that name in my entire mp3 collection. Unless it's renamed elsewhere and has the same file length or something strange. Which is why it would be helpful for emplode to report the duplicates locations.

Mike, i'm sending you the songs... they are different version of the same song and while they sound the same, they have different production quality.
Posted by: mschrag

Re: jEmplode bugger - v47 - 17/12/2003 11:10

If you're emailing, my main mail account will probably bounce it back ... You can use my spamful [email protected] which doesn't have a size limit (that i know of).
Posted by: wfaulk

Re: jEmplode bugger - v47 - 17/12/2003 12:30

Sorry. Bad assumption.