MIDI recording double notes

[William Higgs]

When I record a bass midi track the notes are getting recorded twice, that is there are two notes superimposed on each other when there should be just one.

I've been trying to figure it out, but so far no luck.

Any help/suggestions sure would be appreciated.

Thanks

[David Baay]

Assuming you mean recording MIDI from a keyboard  through a track driving a Bass synth as opposed to using some kind of pitch-to-MIDI on a real bass...

Two things to check would be that the keyboard might be sending on two channels or the track input is set to Omni and the keyboard is connected by both MIDI DIN and USB MIDI ports. The latter would probably result in truncated notes due to overlapping events being on the same channel. The former can be diagnosed by checking channels of events in the Event List view.

[David Bachtell]

One other thing to check: assuming you're using a keyboard of some sort to input notes, check the "MIDI echo" setting on the keyboard. If MIDI echo is enabled, all data streaming from the out port is being resent to the in port. I believe that, by default, Cakewalk turns the MIDI echo off on startup, but something could be different in your system.

[martsave martin s]

William welcome to the forum

by the time you fix your issue,on your recorded midi-track(if they there is 'double' notes)

there is a .CAL script name is undupe (i'v not try it,but you can give it a try...

[select the midi-track then go to [process]-run CAL-[select=undupe]

 

cheer

martin

 

[David Bachtell]

One correction to my previous post: on my synth (obviously a Kronos) the setting to avoid doubled notes is identified as "local control" in the global settings. If the local control is on, the keyboard plays notes entered from the clavier. This will, however, cause doubled notes to be recorded. If it is turned off, the clavier will not sound played notes, but sounds them as it echoes back through Cakewalk. The "cakewalk.ini" file can be edited to turn the local control on or off during startup. I believe the default setting turns local control off, but your system might not be doing this. Hope this helps.

[David Baay]

29 minutes ago, David Bachtell said:

This will, however, cause doubled notes to be recorded.

Leaving Local Control on while also echoing MIDI back to a keyboard synth's MIDI IN will cause double triggering  of the keyboard's sound module while playing in real time or if you record audio from the keyboard synth, but it won't affect soft synths or generate duplicate MIDI events because Local Control is from the keybed directly to the keyboard's sound module - usually not even using MIDI.

[slartabartfast]

Another potential is that your keyboard is sending the notes twice because the notes are contained in  overlapping "layers." It would be useful to have more information about the MIDI messages that are being received, in particular the channel numbers. The overlapping layer issue will typically send the same note on two different channels. 

[Michael Fogarty]

in my case, I have double notes on the same track. Tried undup cal - doesn't work. So the reason this happens is that I had local control on by accident (cakewalk automatically shuts it off but I may have turned it on to practice on the controller)?

How do you get rid of them outside of re-recording? In my case (edit) I opened the track lane and there was only one track so I thought it was ok. But I deleted it as a test and one remained. So I possibly copied over somehow? Interesting it doesn't go to another lane but doubles the lane that is there. One would never know.  Anyway, I am good here but would love to avoid it happening in the future. 

Edited August 31, 2021 by Michael Fogarty

[Scott Kendrick]

I have a similar issue with TD25 midi capture... but I'm also trying to go the route of just clean up (because i don't want to record). Dedup.cal is the way I want to go, but sometimes it misses dupes, and other times, it is deleting notes that aren't dupes, killing my track. Any one know why it doesn't work? (sorry, hopefully not hijacking the thread - just trying to solve the same issue post capture).

[John Vere]

As I just found out don’t use the input quantization as this also creates double notes. Just in case other read this 

[Keni]

On 1/21/2020 at 7:28 PM, William Higgs said:

When I record a bass midi track the notes are getting recorded twice, that is there are two notes superimposed on each other when there should be just one.

I've been trying to figure it out, but so far no luck.

Any help/suggestions sure would be appreciated.

Thanks

Interesting.

As a longtime MIDI user, I’m very familiar with this type of issue and don't often have such a problem.

But as it happens, I've experienced this a couple of times now since the EA.

I'm still examining the situation in case I overlooked something but....

[Michael Fogarty]

14 hours ago, Scott Kendrick said:

I have a similar issue with TD25 midi capture... but I'm also trying to go the route of just clean up (because i don't want to record). Dedup.cal is the way I want to go, but sometimes it misses dupes, and other times, it is deleting notes that aren't dupes, killing my track. Any one know why it doesn't work? (sorry, hopefully not hijacking the thread - just trying to solve the same issue post capture).

assuming you checked under the VST properties that it is not sending enable midi out. Also, did you try what I mentioned above. The place where there are double notes, try deleting the data and see if there were indeed two performances - this worked for me every time. How it got the two performances I don't know. Linking the tracks when copying wouldn't do that would it? After trying dedup, I looked up if there wer issues and it seems it doesn't work for most people.

 

Edited September 1, 2021 by Michael Fogarty

[Pappa G..]

I seem to have the same... I monitor the stave view to see what' s going on.... during recording I can hit perfect 4/4 notes.. and it jots down the notes as the recording carries on...  as soon as I stop recording it screws it all up....

 

<seems to be fine now again.. ??.. dunno.. >

Edited August 24, 2022 by Pappa G..

[David Baay]

5 minutes ago, Pappa G.. said:

as soon as I stop recording it screws it all up.

Please start a new thread for your specific issue, and clarify the symptoms of "screws it all up".

The Event List view will usually be a better place to see timing/doubling issues. The Staff View is trying to fit MIDI timestamps to musical note values which may or may not give a good result , depending on the timing precision vs. the metronome and the display settings.

[rfssongs]

Didn't read the whole thread but want to throw in:

Sometimes if I record from a keyboard that has a layered sound two notes will be recorded, one for each channel of the layer. Usually chan 1 & 2. You can avoid this by setting the input to one of the two channels rather than using Omni . The downside is that you might loose the layer this way. You could also record to two tracks.

[SonicClang]

On 1/22/2020 at 7:35 AM, martsave martin s said:

there is a .CAL script name is undupe (i'v not try it,but you can give it a try...

[select the midi-track then go to [process]-run CAL-[select=undupe

 

I've been using Cakewalk software since 1998 and I had no idea what the CAL option on the menu was for! I just used this and it saved my midi! Thank you!!!