Ghost Movements Pre Halloween Breakout!

[Windsofsoul]

A bizarre item. I was working a group of songs in a sequence and some how.... and I don't know how, the "Solo" button got pressed on then off one track (track during recording, so I figured I could kill it in event editor, but didn't see anything specific there, so I killed it all by erasing the track, yet the Solo button action remained at measure 8, solo going on then off. I then looked in the Master Track but didn't see anything that might resembling Solo on or off in event editor. So I copied a full track over that same track and its STILL THERE! Then out of desperation I copied the whole song to an empty song location with and without events, but lo and behold solo still goes on and off during measure 8 Is it Halloween yet?

Any clues how to fix this. It's ruining some great vocal tracks I put in.
javascript:emoticon('')
Thanks in advance

[HardSync]

Very likely this is a SysEx (System Exclusive) message in one of your tracks, and that message is not necessarily recorded on the affected track. It could be on any track (but definitely not on the Master Track), so...

At the measure(s) where this is happening, go into Event Edit. Uncheck everything except "Exclusive" in the Set Event Filters dialog. You should now only see SysEx messages. If nothing appears, check another track until you find it.

Unfortunately, I don't know what the actual message is, so I can't tell you exactly which SysEx to delete. I believe it will start with F0 42 3g 68 43... In any case, you'll want to trace and delete the SysEx that's causing the Solo/Mute button to be activated.

[Windsofsoul]

Thanks Hardsync, I'll consult the manual to hopefully pick up a sysex name\code. I think it may have happened when I was recording an audio track, so I'll start there. Appreciate the reply, I got down some killer vocal tracks and would hate to lose them and everything else for that matter.