Sonar Needs Solution For Duplicate Notes (Better Than Undupe.cal)

chuckebaby
Do I literally need to look at EACH note"
that's what I do, or I make sure they are correct the first time.
There is only so much you can ask Sonar to do. I know that sounds impractical but its true.
Sometimes we become so accustomed to the software doing so many things we expect even more out of it.
I do that all the time. truth is, it is time consuming and it takes time.
Imagine what we would do without Cal scripts ? I don't even use them.
I check my velocity's, dupe notes, all by hand working in sections to make sure one part is correct before moving on.
 

SilverBlueMedallion
Undupe.cal only removes exact duplicates.   If the note is different in duration and velocity, even though it is the same note, it will NOT remove the duplicate.
This is very annoying when all the sudden one of my kicks is louder than the rest.

Do I literally need to look at EACH note to make sure there is no duplicate right now?  If so, I hope the bakers can come up with something!

rogeriodec
Undupe does not differentiate note veocities or note durations.
The KEY to UNDUPE.CAL work is: ENSURE THAT ALL EVENTS ARE SELECTED IN ONLY 1 CLIP.
See: http://forum.cakewalk.com...s-m879464.aspx#3444681

SilverBlueMedallion

rogeriodec
Undupe does not differentiate note veocities or note durations.
The KEY to UNDUPE.CAL work is: ENSURE THAT ALL EVENTS ARE SELECTED IN ONLY 1 CLIP.
See: http://forum.cakewalk.com...s-m879464.aspx#3444681

did that, still only finds duplicates if it is the same duration and velocity.

Bristol_Jonesey
I've found the best way to identify duplicate notes is to open up the track in staff view. Any duplicates will display on either side of the note stalk. making it easy to delete.
 

rogeriodec

SilverBlueMedallion
 
well i just tested this myself and no go.   check out the video below showing a drum sound hitting TWICE at the same exact time, duration, velocity and MIDI channel, and STILL undupe won't work!   Everything is in one clip as well:

https://www.youtube.com/watch?v=8xhgnR3FEiE
 
here is the event viewer proving this is a duplicate that UNDUPE.CAL just doesn't find.



This is terrible.  No other way to do this then by hand?    

I saw your video and it looks like you're not selecting correctly.
Have you tried:
1) Select the entire track
2) Bounce to Clips
3) Run the CAL (with all selected)?
 
Also, if you want, send me a link with your project for me to review.

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

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.

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

thanks for checking this by the way!

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