Two "control" questions - One on MUTE and one on M
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Two "control" questions - One on MUTE and one on M
I have a midi track that is mysteriously muting itself at measure 22. I can't figure out how to stop it. I looked in the midi event edit section of track edit and there's no control data in that measure. I'm guessing that "mute" isn't a midi control since it's more of an internal sequencer thing? But for the life of me, I can't figure out how to make my track stop muting at measure 22, or how on earth I got it to start doing that in the first place? Any help would be appreciated.
Also, as a follow-up, is there any easy way to overwrite midi control data on a midi track? For example, if I want to overwrite some volume automation I did on a midi track. Right now the way I figured out is to go into the track edit, delete control data for that particular midi control, and then go in and record in "Overdub" mode and control the volume. Is there an easier way? It would be nice to simply be able to record and move the appropriate controls and have it write over the previous control data without overwriting the MIDI notes.
Also, as a follow-up, is there any easy way to overwrite midi control data on a midi track? For example, if I want to overwrite some volume automation I did on a midi track. Right now the way I figured out is to go into the track edit, delete control data for that particular midi control, and then go in and record in "Overdub" mode and control the volume. Is there an easier way? It would be nice to simply be able to record and move the appropriate controls and have it write over the previous control data without overwriting the MIDI notes.
Current Gear: Korg Kronos 2 88, Focusrite 18i8, Sonar Platinum, Win 10 64-bit, 8-gig ram
"The graveyards are full of indispensable men" - General Charles De Gaulle
"The graveyards are full of indispensable men" - General Charles De Gaulle
-
- Platinum Member
- Posts: 1225
- Joined: Mon Jun 01, 2009 4:32 pm
- Location: Northern California, USA
Re: Two "control" questions - One on MUTE and one
[quote="RlaRed"]I have a midi track that is mysteriously muting itself at measure 22. I can't figure out how to stop it. I looked in the midi event edit section of track edit and there's no control data in that measure. I'm guessing that "mute" isn't a midi control since it's more of an internal sequencer thing? But for the life of me, I can't figure out how to make my track stop muting at measure 22, or how on earth I got it to start doing that in the first place? Any help would be appreciated.
Is it in fact muting or have you perhaps forgot to loop it? Or set it to play just one time?
Is it in fact muting or have you perhaps forgot to loop it? Or set it to play just one time?
No it is definitely muting. The icon goes from the green "Play" to the yellow "Mute" at exactly the same time each time I play it through. The track is like 80 measures long and there is MIDI data for the whole thing. It just mysteriously mutes itself for some reason at measure 22. My original thought was I accidentally put that in the automation, but there's no MIDI control data in the midi event log to that effect.
Current Gear: Korg Kronos 2 88, Focusrite 18i8, Sonar Platinum, Win 10 64-bit, 8-gig ram
"The graveyards are full of indispensable men" - General Charles De Gaulle
"The graveyards are full of indispensable men" - General Charles De Gaulle
-
- Platinum Member
- Posts: 1225
- Joined: Mon Jun 01, 2009 4:32 pm
- Location: Northern California, USA
Have you tried copying to another track?RlaRed wrote:No it is definitely muting. The icon goes from the green "Play" to the yellow "Mute" at exactly the same time each time I play it through. The track is like 80 measures long and there is MIDI data for the whole thing. It just mysteriously mutes itself for some reason at measure 22. My original thought was I accidentally put that in the automation, but there's no MIDI control data in the midi event log to that effect.
Copying it to another track fixed it on the new track. . . it's not doing it anymore. I'd still like to figure out why it was doing it though and how to fix it. . .
Current Gear: Korg Kronos 2 88, Focusrite 18i8, Sonar Platinum, Win 10 64-bit, 8-gig ram
"The graveyards are full of indispensable men" - General Charles De Gaulle
"The graveyards are full of indispensable men" - General Charles De Gaulle
- runningman67
- Platinum Member
- Posts: 1663
- Joined: Sat Aug 06, 2011 6:13 pm
- Location: Manchester UK
Bingo! That was it. The track being affected was Track 2. I looked on track 1 and sure enough at measure 22 there was a SYSEX message. I must have accidentally muted track 2 when recording on track 1 or something. Anyway, thanks everyone for the help.Shakil wrote:In event edit view, are you filtering out sysex data? mute switch sysex data can be on any track..... so check all tracks.
Any responses for the second paragraph in my original post?
Current Gear: Korg Kronos 2 88, Focusrite 18i8, Sonar Platinum, Win 10 64-bit, 8-gig ram
"The graveyards are full of indispensable men" - General Charles De Gaulle
"The graveyards are full of indispensable men" - General Charles De Gaulle
Yeah I believe that's what happened. Seems like a bug to me, unless there's some good reason it should do this. . .runningman67 wrote:Is it possible that you muted a track at that measure, whilst recording another track. It happens and remembers, for some strange reason and its frustrating, no idea why it should remember a mute on a midi track that is not being recorded.
RM67
Current Gear: Korg Kronos 2 88, Focusrite 18i8, Sonar Platinum, Win 10 64-bit, 8-gig ram
"The graveyards are full of indispensable men" - General Charles De Gaulle
"The graveyards are full of indispensable men" - General Charles De Gaulle
mute error during sequence play Korg Kronos
I have a similar problem only pressing "play" in sequence mode mutes TWO tracks just after the FIRST note of each is struck. I used the workaround of copying to a different track and that solves the problem for both tracks. What is different is that there was nothing showing up with the midi event "exclusive" filter ticked. This ticks me off. Am I missing something - is sys-ex the same as "exclusive" when editing midi events?
Tim