Ah ok, I actually mean right-click, "bounce to clip" command not anything like bounce to audio.
MIDI tends to get fragmented over time while you work on it and bouncing all of the bits and pieces of a MIDI
track to a cohesive clip often fixes issues. Just highlight all the pieces of that track, then right click any where on a
clip and choose bounce to clip. It's worth a try.

Thanks for the tips guys. They will be noted for future needs. I was trying to do something kind of fancy in this case that seemed to irritate that clip. Normally that wouldn't happen (I hope) but because of that nasty little thingie I just had to fall back on what worked before. I just hope it doesn't give me a hard time while I bounce all the tracks to audio... which if I can get my arse in gear I will be doing this afternoon.
 
Thanks again for pontificating on such a weird and presumably rare (if not completely isolated) happenstance. I always seem to find the fun stuff, eh? ;-)

And just to clarify the bounce to clip I did a few days ago did indeed behave but that was using multi selection methods and even deleting the lane the offending clip occupied. The bounced clip still caused the issue at that spot when I tried to do my fancy footwork which is what prompted the thread. Somehow even though it was deleted it wormed it's way into the bounce. I even tried deleting the original track (I bounced it all to a new MIDI track to preserve the fragmented one) but it still caused the dropout. Extremely weird behavior. I'd send the project to Cake to see what's up but a) I've got my workaround and b) it would be pointless because this is an X2 project. More of a curiosity than anything.
 
I'm still thinking the padKontrol sent a wonky message. I don't know if that can happen but it's the only explanation I can come up with.
 

weird! definitely post any updates

Transcending Music
weird! definitely post any updates

 
+1

I would look close at the midi data itself, is it at all possible the midi is triggering a hidden note that is not applicable ?
IE-its triggering something that is causing the crash.

Anything in the Event List?

chuckebaby
I would look close at the midi data itself, is it at all possible the midi is triggering a hidden note that is not applicable ?
IE-its triggering something that is causing the crash.

hmm... not sure how it would do that unless, as I was wondering about earlier, the pK sent a bad note. IIRC I had the entire controller mapped (as in all the pads were going to notes used in the project all of which were successfully triggered before and after without causing problems) so anything that got inputted SHOULD have been a valid entry. I guess maybe there is a bad velocity layer in there somewhere but this is the Rock Legends kit for BFD from Platinum Samples. It should be pretty solid.
 
Also... hi, Chuck. Don't see you around much anymore. Hope everything's alright. Cheers. :-)
 

brundlefly
Anything in the Event List?

This is something I hadn't thought of mainly because I've never used the EL before. It confused the heck out of me but I know enough about MIDI now to at least read and understand the data. I'll try this after I safely get what I need to move on to the mixing phase before I fiddle with that though because I don't want to tempt fate and end up with an unusable project because I was curious.
 
But... does the EL show ALL MIDI data in the project or is it clip specific? Will it show archived data? Layered clips (takes)? Will I have to select the problem clip to see what's there or expand it? If the EL doesn't show anything other than currently selected or audible/active data then I doubt it'll show anything because I can't actually get the data displayed. It's just a vertical line left after slip editing it down to nothing and as I said it won't let me near it.
 
Good suggestion though. I should start looking at the Event List in general anyway just to gain a better grasp on MIDI stuff. Cheers.