Remove duplicate MIDI notes?

I have a MIDI track that, for some unknown reason, has a lot of duplicate notes. Is there any way to filter these out, or do I have to go through and manually delete every one?

Thanks for your time.

Larry

I could've sworn there was a "DUPES.CAL", but I can't locate it right now. Aargh! Maybe someone will come up with it...

-Susan

hi bluz!

You have to Downloald the zip-file mentioned above, unzip it, and put the File "UNDUPE.CAL" in your CAL-Folder...

best
Tosch;)

Hey, thanks for all your help! I've never gotten into CAL (I'm a newcomer to Sonar from another DAW), so now's the time. I'll let you know how it works out.

Larry

Hmmm! Now THIS is interesting. There should be an option under Process called Run CAL. However, although it is clearly indicated in the help file under CAL, it does not show up in my Process menu at all. So the question remains, how do I access CAL under S6.01? I've not had a need to use it so far but thought I'd check it out so I could reply within this thread. Ideas, anyone?

Thanks.

When I try to run undupe I get a dialogue "windows for time identity"....what does this mean?
Whether I leave it at the default of 0 or enter 100 I get "deleted 0 duplicate events".
I know I have hundreds of duplicated events in the track...what am I missing here?
Thanks very much,
Randy

It identifies the span of time that defines a duplicated note.
So if two notes are very close to each other, are they to be handled as duplicates?
 
But having said that, I have never managed to get the dupe cal script to work.
Others have had more success, I followed the steps they mentioned, no luck.
 

I also have had mixed luck with UNDUPE.
 
What I've done in the past is to open the track with the duplicates in Staff View.
Any duplicated notes are clearly visible as they will be on both sides of the stalk.
 
It's then a question of identifying them and deleting them. One word of caution, if you do decide to pursue this, when you delete a duplicated it initially removes both notes, but a quick Undo (ctrl + z) will restore just ONE of the notes to it's previous position, which is exactly what you want.
 
It's a very long winded workaround but also guaranteed to work.

Well, I spent a few hours studying the rare and still existing materials about CAL scripts on the web.
I did some tests and I discovered the cause of UNDUPE.CAL (and other scripts) do not work:
This is a bug in CAL language.
Basically events (notes, controls, etc.) should be read sequentially (by commands like forEachEvent), ie, the events should be read in chronological order.
However, events are read from a TOTALLY RANDOM way.
Thus, it is IMPOSSIBLE to compare a previous note with a later note, because the script simply NOT BRING EVENTS IN CHRONOLOGICAL ORDER.
Certainly these old scripts worked in some older version of Sonar, but after that CAL was abandoned, Cakewalk still managed to spoil it.
As I said, it's a shame Cakewalk still provide CAL if it is no longer supported. Or they correct the CAL or remove it once and for all.

tparker24
As I recall, the problem occurs if processing multiple clips at one time.  If you work on a single clip, all is well.  So, you'll need to bounce multiple clips into a single clip (or process the clips one at a time).  

I'm not 100% positive on this, but at least, it's something to try.

Yeah, try this:

1. Open a new project, 1 midi track
2. Open PRV and create, for example, 10 identical notes, one after another.
3. Select all
4. Set all velocities of notes to 10 (Process -> Scale Velocity), so you'll have 10 identical, consecutive notes, all with the velocity 10
5. Run the following script, which adds 1 to 1 increment each note position, i.e., theoretically the first note should be with the velocity 11, the second note should be 12, and so forth (save the code below into a new file any CAL and run it (Ctrl + F1)

 

(int x 0)

(forEachEvent
    (if (&& (== Event.Kind NOTE) (< Note.Vel 127)) 
        (do
            (+= x 1)
   (pause x)
            (+= Note.Vel x)
        )
    )
)

 

• The first thing you'll notice is that the loop (forEachEvent) runs more than the number of events (notes). This is shown by the command (pause x) that shows the value being added to each note.
• After running the script finished, you will see that all velocities were changed, however randomly.
• And there is only one clip, one track, only 10 events (10 notes), nothing more.

tparker24
As I recall, the problem occurs if processing multiple clips at one time.  If you work on a single clip, all is well.  So, you'll need to bounce multiple clips into a single clip (or process the clips one at a time).  

I'm not 100% positive on this, but at least, it's something to try.

i just tried on a single clip and it still didn't work.  then again, nothing works right for me :(