Bizzare panning inside Trilian mixer due to certain Midi Clips - X2

I'd say that the problem needs deeper inspection, because there's just so much that needs to be eliminated before it can be said it's X2.

I'd start of with no automation lanes at all, so that automation can be immediately counted out as a source of the problem. Then, I'd try muting all tracks except the the one that's *supposed* to be going to channel one, play that and observe if the pan moves. If that works ok, enable the other tracks one at a time to see which one causes the pan.

-Gene-

Sounds like corrupt MIDI data, although one would expect the corruption to a) show up in the event list and b) be propagated to the new clip after bouncing. I hope you'll report CW's findings when you've heard back from them.

Did the problem go away when you disabled automation?

bitflipper


Sounds like corrupt MIDI data, although one would expect the corruption to a) show up in the event list and b) be propagated to the new clip after bouncing. I hope you'll report CW's findings when you've heard back from them.

Did the problem go away when you disabled automation?

Bit - I had no automation for trilian on this track.  But I deleted every other track in the project so at the end it was just the midi track and trilian audio track - no automation at all, but the problem still persisted.  


There are a couple really weird things:  1) there were two points in the project where if I started exactly on those points or after them the pan would change.  But if I started before the first point with the pan centered, once it reached theses points the pan would stay centered.  

2) the first point seems to be tied to a clip where if I deleted the clip the problem would go away.  The second point was in an area in the track where there was no midi clip at all.


3) the first point changed the pan left  about a quarter turn.  The second point changed the pan to the right.


I agree - must be corrupt midi data.  There was a point during the X1 madness where all sorts of weird things were happening.  One thing was this: some FX chains would crash Sonar if I tried to delete them.  I eventually just turned these chains off and left them in the project because I couldn't delete them.  I still have some of these corrupted FX chains today and to this day they crash X2 when i try to delete.  What I'm thinking is that something like this occurred with the midi data.

 When I looked at the PRV there were two controller lanes cc:1 and cc:10.  But they were both totally empty.

I discovered through trial and error that Sonar will not display codes before the first note (in some cases?). I cannot say whether this is all the time or what certain conditions are necessary - I didn't bother to parameterize the issue any further.. Specifically, I noticed the same thing - the track NOTES view indicates a couple of CC's that you could choose to display and that appear to be in use, but nothing shows up in the event lists for that track. On a hunch, I opened the same midi file in Acid and looked at its event list there. Sure enough, there were those suspect CC's lurking in the event list, plain as day.