Posted: Sat Mar 24, 2007 1:30 pm
Top notch 
MediaMonkey forum
The Music Manager for Serious Collectors
http://www.mediamonkey.com/forum/
Tagging Inconsistencies 4.0.1 (2014-02-27)
Page 4 of 67
Posted: Sat Mar 24, 2007 4:18 pm
Thanks Bex!
Posted: Sat Mar 24, 2007 4:49 pm
Bex if you wish i can provide you with a place where you can update the vbs files so u don't need to post the code directly into the forum.
Regards,
Red
Regards,
Red
Posted: Sat Mar 24, 2007 10:26 pm
Could you also please under Albums with -> Same TrackTitles make an option to only consider this a mistake if the artist is also the same?
In same albums the tracks have the same name but not the same artist.
And another thing is the too many tracks, i have some compilations, strictly on mp3 that weren't on CD and have more than 99 songs, and eventhough for a cd the max is 99 could you maybe make this an optional criteria for too many tracks?
Thx,
Red
In same albums the tracks have the same name but not the same artist.
And another thing is the too many tracks, i have some compilations, strictly on mp3 that weren't on CD and have more than 99 songs, and eventhough for a cd the max is 99 could you maybe make this an optional criteria for too many tracks?
Thx,
Red
Posted: Sun Mar 25, 2007 1:59 pm
Thanks guys!
@RedX
Thanks for the offer. Very nice of you. But I think I already have a place to store it provided by my ISP but I'm to lazy to figure out how it works.
Same Artist make sense. I'll change the SQL to consider it. (plus a bugfix with the genre node and perhaps some new nodes.)
The "too many tracks"-node already deals with tracknr's over 99. Doesn't it work for you? (Perhaps I don't understand what you mean exactly?)
@RedX
Thanks for the offer. Very nice of you. But I think I already have a place to store it provided by my ISP but I'm to lazy to figure out how it works.
Same Artist make sense. I'll change the SQL to consider it. (plus a bugfix with the genre node and perhaps some new nodes.)
The "too many tracks"-node already deals with tracknr's over 99. Doesn't it work for you? (Perhaps I don't understand what you mean exactly?)
Posted: Sun Mar 25, 2007 4:24 pm
As i seem to experience it as soon as an album tracks get over 100 it considers that album as having too many tracks. What i'd like is that this limit is configurable to let's say 200 or whatever or so that i could disable it. Because i kind of don't care how many tracks an album has as long as none of the # are double in the album.
Hop that explains it
Hop that explains it
Posted: Sun Mar 25, 2007 4:45 pm
Small update
Version 2.1 (2007-03-25)
Bugfix release:
- Fixed bug in Genre node
- Changed logic in "Same TrackTitle"-node to also consider the artist of the track
- Minor code changes
Enjoy!
/Bex
Version 2.1 (2007-03-25)
Bugfix release:
- Fixed bug in Genre node
- Changed logic in "Same TrackTitle"-node to also consider the artist of the track
- Minor code changes
Enjoy!
/Bex
Posted: Sun Mar 25, 2007 4:47 pm
Is the code in the first two posts this update?
Posted: Sun Mar 25, 2007 4:48 pm
@Vyper.
Yes!
Yes!
Posted: Sun Mar 25, 2007 4:50 pm
Thanks. You da man! 
Posted: Sun Mar 25, 2007 4:54 pm
The logic of the SQL should cater for this. Meaning that if the albums get listed it actually has to many tracks. But I'll recheck the logic to see if its something wrong with it.RedX wrote:As i seem to experience it as soon as an album tracks get over 100 it considers that album as having too many tracks. What i'd like is that this limit is configurable to let's say 200 or whatever or so that i could disable it. Because i kind of don't care how many tracks an album has as long as none of the # are double in the album.
Hop that explains it
Posted: Sun Mar 25, 2007 4:59 pm
Thanks Vyper!
@RedX
Yes, it seems to be an error in the logic of the code. I'll see what I can do to correct it. It could actually be a bit tricky...
@RedX
Yes, it seems to be an error in the logic of the code. I'll see what I can do to correct it. It could actually be a bit tricky...
Posted: Fri Mar 30, 2007 8:21 pm
Script is updated:
Version 2.1 (2007-03-31)
- Change logic in "Missing tracks" node
- Change logic in and renamed "To Many Tracks" node to "Some blank Track#'s"
The Track# nodes works like this
- Missing Tracks
All tracks must have a number and non can be duplicated. The nodes finds Albums with track numbering not in sequence. (It's pretty smart and understands 3 digit numbering like 101-111, 201-212 aso.)
- Some blank Track#'s
Finds Albums with some, but not all, blank track#'s
- Same Track#'s
All tracks must have a number and if any are duplicated this node will find such Albums.
- No Track#'s
Finds all Albums with all its track# blank
Enjoy!
/Bex
Version 2.1 (2007-03-31)
- Change logic in "Missing tracks" node
- Change logic in and renamed "To Many Tracks" node to "Some blank Track#'s"
The Track# nodes works like this
- Missing Tracks
All tracks must have a number and non can be duplicated. The nodes finds Albums with track numbering not in sequence. (It's pretty smart and understands 3 digit numbering like 101-111, 201-212 aso.)
- Some blank Track#'s
Finds Albums with some, but not all, blank track#'s
- Same Track#'s
All tracks must have a number and if any are duplicated this node will find such Albums.
- No Track#'s
Finds all Albums with all its track# blank
Enjoy!
/Bex
Posted: Sat Mar 31, 2007 4:08 am
Cool beans.
Posted: Sun Apr 08, 2007 1:13 pm
excellent work Bex, just one (very) minor typo. under the "Albums With..." node, "To Many Tracks" should of course be "Too Many Tracks".
again, loving this script.
again, loving this script.