I know my first comment was probably over looked and it wasn't much help (for that I apologize).
But I will go back to something I said in my first comment...
 

Chuckebaby
I check my velocity's, dupe notes, all by hand working in sections to make sure one part is correct before moving on.

SilverBlueMedallion
 
 
#1.  I have tried selecting the entire track (but why should I have to?)
#2.  It was already bounced to clips.  The entire track had one clip
#3.  Why can't I select the notes I want the CAL to look at?
 
I appreciate it, but what I did do was, well I chose a windows of "1" this time and it worked, but the notes were on the same tick!

You do not actually need to select the entire track, this was just a suggestion to make sure all the notes would be selected.
Can you post your project, or just this project track, for me to help test?

File is here:
 
https://www.dropbox.com/s/bk7e8dye57eq1u8/Retroheart.cwp?dl=0
 
 
here are the duplicate events:
 

SilverBlueMedallion
File is here:
 
https://www.dropbox.com/s/bk7e8dye57eq1u8/Retroheart.cwp?dl=0
 
 
here are the duplicate events:
 

Okay, I opened your project.
If I select the entire track, undupe deletes 10 duplicate events.
If I select ONLY these two duplicate notes (F#4), undupe does not delete anything. This is because, as I said in my second post of this topic, there is a bug in the undupe, which needs to have at least one selected note BEFORE the desired selection.
So, if I select (at least) the previous note (F#3), in addition to the two desired (F#4), undupe will correctly detect and remove the duplicate second note (F#4).
 
So I could sentence two conditions for undupe.cal to work properly:

1. Make sure all selected notes are in the same clip (or make a bounce to turn everything into a single clip);
2. Make sure that at least one note (which is not duplicated) is selected before the desired selection range.

I think if you can get by with this little bug, you will not have any more problems.

rogeriodec

SilverBlueMedallion
File is here:
 
https://www.dropbox.com/s/bk7e8dye57eq1u8/Retroheart.cwp?dl=0
 
 
here are the duplicate events:
 

Okay, I opened your project.
If I select the entire track, undupe deletes 10 duplicate events.
If I select ONLY these two duplicate notes (F#4), undupe does not delete anything. This is because, as I said in my second post of this topic, there is a bug in the undupe, which needs to have at least one selected note BEFORE the desired selection.
So, if I select (at least) the previous note (F#3), in addition to the two desired (F#4), undupe will correctly detect and remove the duplicate second note (F#4).
 
So I could sentence two conditions for undupe.cal to work properly:

1. Make sure all selected notes are in the same clip (or make a bounce to turn everything into a single clip);
2. Make sure that at least one note (which is not duplicated) is selected before the desired selection range.

I think if you can get by with this little bug, you will not have any more problems.

 
hmmm.. you chose a window of "zero"?

thanks for checking this by the way!

I just ran UNDUPE.CAL on your midi track and the duplicate notes were deleted. This is with a window setting of 0

SilverBlueMedallion
 
hmmm.. you chose a window of "zero"?

thanks for checking this by the way!

Sorry for my ignorance, but what do you mean by "window of zero"?

When you run Undupe you should get a dialog box to enter, to give it it's correct name, Window for time identity.
 
I think larger values will open up a larger "window" to look for otherwise identical events but with slightly different time settings. There's nothing documented about this so I couldn't tell you what the parameter describes - could be ticks, could be anything.
 
Setting window of 0 means only completely identical events will be deleted

Bristol_Jonesey
When you run Undupe you should get a dialog box to enter, to give it it's correct name, Window for time identity.
 
I think larger values will open up a larger "window" to look for otherwise identical events but with slightly different time settings. There's nothing documented about this so I couldn't tell you what the parameter describes - could be ticks, could be anything.
 
Setting window of 0 means only completely identical events will be deleted

Ah, yes, of course, he was referring to the initial parameter of the undupe.
Yes, I always use zero.

so it STILL wasnt working, even given all these parameters....  BUT what does work.... is selecting only ONE pitch at a time in the drum map.  So i selected ALL the closed hi-hats.... and THEN it works!

If you select different drum sounds, it doesn't work at all.   What a crappy solution.