One track records everywhere

[jkoseattle]

I have one pesky Midi track in my project that records and plays just fine. But any time I am recording on any OTHER track, any notes playing in the pesky track get recorded to the new track along with whatever I am actually trying to record. So I have to delete those extra notes every time I'm recording any other track. I don't see anything obviously different about the pesky track. What am I missing?

[David Baay]

First, as a best practice you should set the Input of the new traack to the specific port and channel that you intend to record, not All Inputs. Then check the properties of whatever synth the re-recorded track is driving, and make sure it's not unintentionally echoing MIDI input to a virtual OUT.

[Amberwolf]

3 hours ago, jkoseattle said:

I have one pesky Midi track in my project that records and plays just fine. But any time I am recording on any OTHER track, any notes playing in the pesky track get recorded to the new track along with whatever I am actually trying to record. So I have to delete those extra notes every time I'm recording any other track. I don't see anything obviously different about the pesky track. What am I missing?

At least two things could do it:

 

If the pesky track is still armed for record, then it will also record any inputs.  Disarm the tracks you don't want to record to before starting a recording session to prevent that. 

 

If the setting "allow MIDI recording without an armed track" is enabled, and you have selected that track, then it will record on that track even if it isn't armed (as well as any that are armed).  This will happen even if you have set the port to "none" because Cakewalk will change it to "omni" so that it can record per the setting that's been enabled, during the recording.  Only select or click on tracks you want to record on to prevent that, if you need to use this setting. 

 

Edited November 24 by Amberwolf

[jkoseattle]

OK, I've managed to get this project out the door, so immediate crisis averted, but I want to make sure I'm not going to run into this again.

New weirdness: When I exported to audio, only the pesky track rendered, even though I did it like four times and made SURE I didn't have anything selected, all the export settings were right, etc. I've exported many times so I know what I'm doing. Turned out, when I used File > Export and the big dialog is when the problem occurred. When I used the quickie export function from the module in the top toolbar, it worked.

As for the pesky track, I definitely did not have the track armed, and I always have "allow MIDI recording without an armed track" enabled, which means I'm very familiar with making sure I'm on the correct track before recording. However, the All Inputs thing could be the issue. I don't understand it at all, I've not had this issue in decades of use, and now all of a sudden I'm having to worry about the input settings. What changed?

[Promidi]

4 hours ago, David Baay said:

First, as a best practice you should set the Input of the new traack to the specific port and channel that you intend to record, not All Inputs. Then check the properties of whatever synth the re-recorded track is driving, and make sure it's not unintentionally echoing MIDI input to a virtual OUT.

^^ This! ^^

[jkoseattle]

I get it. You didn't need to tell me again. My question is above.

[David Baay]

On 11/24/2024 at 2:22 PM, jkoseattle said:

What changed?

I would guess using a VSTi that echoes MIDI or installing virtual MIDI cable software with looback enabled. Otherwise the only way MIDI get's into another track is by a physical MIDI loop via having Out=Thru enabled on a keyboard controller or an interface that can loop MIDI internally, if not an actual cable between an OUT and an IN.

That pretty much covers the possibiities other than some sort of project corruption. But given that CW isn't inherently capable of outputting MIDI  to more than one port (much to the chagrin of many users), that seems unlikely.