Step Sequencer issue (was: More Addictive Drums strangeness)

I created a step sequencer pattern that I was using with Addictive Drums. When I first created it, I had added AD with only one stereo output. I realized that I wanted individual outs so I create a new project with individual outs, renamed all the tracks and saved it as a track template. Then I started a new project, inserted my newly create track template. I added a step sequencer then loaded my pattern. However, the pattern would not play correctly.
 
I looked at this for 1/2 hour or so, looking at every setting to see what was wrong. I could not find anything wrong. Some drum hits just would not play. I could not figure it out.
 
After messing with it for a while, Sonar X3a crashed. I can't remember my last crash in Sonar X1/X2 so it was a surprise to me. I sent the crash report to Cakewalk. When Sonar started back up, I started over but this time, the pattern played fine. I then opened a new project and did the same steps and it played fine. I opened another new project and did the same steps, except, this one didn't play correctly.
 
I posted earlier about a strange issue with the Synth Property Page causing issues with the knobs and sliders in the console view. Perhaps, you can't (or at least, I can't) have more than a couple projects open at a time with AD. By the way, these were all new projects that had nothing but AD added to the project and a step sequencer pattern loaded. And I only have a total of 116 plugins :-(
 
I guess the workaround is to only have one project open. This is fine with me but I am wondering if this is a bug or something I am doing wrong or more importantly something that is going to happen once I add more instruments and tracks to my project?
 
Thanks

Thank you for the help!
 
I set the MIDI Prepare Using buffer to 500ms but this time it failed to play the pattern correctly the very first time. That is, the first project I loaded.
 
However, I think I have solved this. There was an extra step I was doing to get it to work. Sometimes I would do that extra step and sometimes not. I just wasn't remembering from one time to the next. To get it to work I have to setup the number of steps and such before loading my pattern. This seems like a bug to me. I will report it unless you guys think this is normal. It doesn't seem normal because I would have to know the beats and steps of a pattern before I load it.
 
For example, my pattern is 4 beats and 8 steps. The Step Sequencer defaults to 4 beats and 4 steps. When I load my pattern, it changed the number of step to 8, but it doesn't play the notes that fall in the second 4 steps of a beat. That is how it appears anyway. If I set the number of steps to 8, then load the pattern, everything looks exactly the same but now it plays correctly.
 
I will change the title of the thread since it doesn't seem related to Addictive Drums. I haven't proven that yet but it certainly seems like it isn't.

So as I think you can tell, this is not my forte.
 
When you say MIDI pattern... What I am doing is using the Step Sequencer to create a pattern (I would call it a Step Sequencer pattern), then I save it. Close the project, start a new one, start the Step Sequencer then load that same pattern back. It will not play correctly for me.
 
I would like to ask you more about the piano roll but I should go off and read about the piano roll first.
 
Thanks for the help!

When I was trying your suggestion to go to 500, I also tried 1000 but I still had the same issue. Since you do not have this issue, it does not appear to be a bug but something in the way I am doing things or some other setup issue. I am calling tech support right now (currently in the wait queue) about another issue I am having that they are saying is a setup issue. Perhaps they are related? We'll see. Either way, thank you for your help and I will report back if TS gives me some guidance that helps me or not.
 
 
--Update--
Just got off the phone with support and they were unable to reproduce this issue. Nor could they reproduce the issue I submitted about AD causing the sliders and knobs move with high acceleration. I however can reproduce both issues in Sonar X3a and Sonar X2a. I moved my buffers back up to 500 and then tried 1000 again but still have the issue with the Step Sequencer.
 
An interesting piece of info, if I convert the clip, bounce to clip, then convert it back to a Step Sequencer clip, I lose the drums that are not playing. It is as if they really aren't there. 
 
I am downloading X3b and will give that a shot.

I am resurrecting this thread because I am having the same Step Sequencer issues with Addictive even in X3e!
I use Step Sequencer exclusively to create patterns for the project's drum parts in conjunction with Addictive Drums.
 
What I am finding from X2a onward, is that patterns created and then stretched out beyond their original  length will occasionally just stop playing during the song. When the next pattern starts, then Addictive will wake back up.
This problem did not exist in the X1 system builds using the same process.
 
I have experimented with the  "MIDI Prepare Using buffer" using everything from the default 250 all the way up to 1000 with no effect on the strange behavior. This is not just in playback but also mix down as well.
 
From what I can tell and this may just be my perspective, the less midi related tracks or fewer softsynths in the project, the better the performance but start adding softsynths and the problem rears its ugly head again and again. The ONLY workaround I have found from X2a up till now ( X3e ) has been to " Bounce To Clip" the Addictive Drums Step Sequencer Pattern when it is stretched out beyond its original length ( from a 4 bar loop to 16 bars for example ).
 
Something about bouncing the stretched loop to a consolidated clip solves the problem for the time being. But then you loose the ability to edit/copy/paste the loop at its 4 bar size, which is very helpful when you are doing lots of patterns, followed by fills.
Repro:
Add Addictive Drums as a softsynth to the project track from the Browser and choose the regular stereo out config in the synth properties dialog box.
Load the kit of choice.
Go to the 'Views" and choose 'Step Sequencer" and create a fairly complex pattern ( 16th note hats with varying velocities ) over a kick and snare pattern.
Save the Step Sequencer Pattern and return to the track view and drag the newly created pattern out for 16 or more bars. In big projects, this wont take anywhere near 16 bars to fail.
Now add more softsynth parts ( Dim Pro keys parts, SI Bass parts, ect )
 
This is in the context of a 3-4 minute pop/county song so keep in mind that short 8 bar examples will not produce the same results. Also, we have owned Addictive before it was offered as a X3 add on and yes, its the 64 bit version. We don't use session drummer for this purpose so I cant comment on rather it affects that softsynth as well. Also, no other softsynth in the project drops out no matter how big the project gets so I'm assuming this issue is specific to Addictive Drums alone.
 
Any one else experiencing this and have a solution, please chime in as it is pretty frustrating considering that the combination of Addictive Drums and the Step Sequencer is our main process for creating drum grooves and patterns.

Heh brundlefly,
 
Sorry, should have specified that this only seems to happen from step Sequencer clips that are 'created inside' of Step sequencer. Ive never had it happen to a clip that was converted from a regular midi clip or a clip created in Piano Roll, then converted to SS. Weird thing is that bouncing to clip always seems to fix it.
 
Yeah, I know this is one of those things that I wish would happen consistently so I could say beyond a doubt that its this or that. Intermittent problems are the worst of all I think. Thank you for trying this out!