How to remove duplicate midi notes with Undupe CAL?

After editing a midi bassline, I have discovered double overlaying notes.
Done some searching and the solution apparently is the "undupe" cal script.
 
I cannot get it to work.
 
At the start, it asks for "Window for time identity", which is 0 by default.
No matter what I enter, it returns with "deleted 0 duplicate events".
 
It does not even find a double pair of notes I put in manually.

Anyone know how it is supposed to work?
 
I have Sonar X3e.

This is getting disheartening.
 
So often when I try out something in Sonar, it's outdated, buggy or doesn't work properly anymore.
 
Are new features being piled on top of a crumbling core?
 
I found a 101 page document from 2010 called Cakewalk Application Language Programming Guide,
so I'm teaching myself CAL now so I can get to the bottom of this problem.

I can also confirm that Undupe no longer works. I don't know when it got broken, but I was planning to use it on many projects in the near future, so this is very bad news for me.
 

twelvetone
This is getting disheartening.
 
So often when I try out something in Sonar, it's outdated, buggy or doesn't work properly anymore.
 
Are new features being piled on top of a crumbling core?

 
I think so. There are a number of bugs that haven't been fixed for more than 1-2 years after they were found and reported. CW gave higher priority to redesigning the start page, which nobody really asked for, over fixing a bug that 40+ users wanted fixed.
 
I often wonder if it's the same in the other old daws like PT, DP, and Cubase.

It does not work in Splat.

Maybe it's not working properly? (Just tried it in the Normal project template)
 

icontakt
In other words, it's better to merge all MIDI clips in the track before using this script.

Keep in mind CAL predates lanes and layers. Only MIDI tracks existed when CAL was developed.

I am working through the Cakewalk Application Language Programming Guide.pdf
I made some test scripts which successfully change Now, track titles, get the event kind, etc.
So fundamentally, CAL is there and still works.
 
The scripts seem to be divided into 2 types:
1) Ones with author details inside. These have filenames that conform to the DOS 8.3 all-caps format and appear to to originate from a competition held in 1991. Each author has an ID and seems keen to publish personal details. All of these have a 3-part structure comprising 3 do-blocks which, in some file comments, are identified as Prolog, Body and Epilog. UNDUPE.CAL is one of these, the attribution is however a bit vague. It only states "Maybe Miguel Ratton".
 
2) Ones with no author in the comments. These have mixed-case long names. None have originator or  author info.
These are also structurally different in that they have a single do block and most have looping statements such as while and, significantly, forEachEvent.
 
There is one from this group that stands out: Split Note to Tracks.cal in that it has in the comments:
Courtesy Red Nile Productions 1993
Modified Greg Hendershott at user's request 12/10/93
 
There is also a script called need20.cal which is called up by many other scripts. All it does is check whether the CAL engine is version 2.0 or higher. (X3 is 100 = v10.0)
 
I am not deep enough into CAL yet but my guess is that the older scripts conform to this 3-block Prolog-Body-Epilog idiom which carries with it an implied looping and that this is now superseded by explicit looping statements, which may explain why icontakt finds only one note is being deleted from a selected range in UNDUPE.CAL. (Although I am not getting it to delete ANY yet...)
 
Having said that, I am finding that I can play with the 3-block idiom and it does seem to work to some degree.
 
I have found no mention of the 3-block idiom in the document so far, so this is all speculation at this point.
 

I downloaded the CAL Editor years ago not for editor but for the "CAL Reference.chm"
No worked examples but a nice concise reference.

I am still on Win7

Yeah it's just the first duplicated pair undupe misses for some reason.

scook
Here is a different take on removing duplicate notes. Did not test it much. Functionally similar to UNDUPE.CAL

 
Thanks for that, scook. But.....am I right in understanding that this CAL (I tried both the original Undupe and your rmdupes) only removes duplicate notes where no other note events exist (vertically)?
If so, it's not usable for, say, hard quantized drum tracks, is it?
 

icontakt
this CAL (I tried both the original Undupe and your rmdupes) only removes duplicate notes where no other note events exist (vertically)?
If so, it's not usable for, say, hard quantized drum tracks, is it?

 
no, nor for hard quantized chords.