Hello Everyone,

I've had this issue now on my tracks.  If I have a bunch of different step sequence patterns in a track along with some additional manually played parts in another take in a single midi track, then I go bounce to clips, it cuts parts of the drum track.  Please see the screen shots below.  
 
This is my drum track in gold, it consists of step sequencer patterns and also some manual clips I played on top (if you opened the take lanes, you would see 2 lanes, 1 for step sequence patterns and 1 manually played track (for fills and things like that)
 

 
 
I then wanted to bounce them to clips, which I do, but this is the end result:
 

 
as you can see, the 2nd half of the song now has NO DRUMS!
 
The reason I do this is also a Sonar flaw.  I notice if I export the file with step sequencer patterns, sometimes they dont play in the export (but thats for another thread I guess).
 
Any help would be greatly appreciated.
 
Thank you,
Adam

Hmmm, that's curious.  I don't usually do it that way, myself.  I usually have the step sequencer clips on one track (usually an instrument track), and then if I want to add fills etc, I'll create a new MIDI track, route it to the soft synth track, and add my manual MIDI stuff.  Never had a problem.

Anything muted when you bounced? Muted MIDI gets thrown away on bounce to clips. It might help to see the track with lanes showing.

nope, nothing muted.  sometimes i export and it works great, other times it doesnt... sometimes right after one another.  seems like a resource issue but my machine is a beast.

in my experience, step sequencer is broken, and will stop playing randomly whether during playback or bouncing. I just write patterns with it then convert it to midi, no problems then.

Spencer
in my experience, step sequencer is broken, and will stop playing randomly whether during playback or bouncing. I just write patterns with it then convert it to midi, no problems then.

YES!  I have this same problem when playing tracks too!  you are correct.   I am buying Sonar 2015... if it still exists there, I will make a problem report.

I'm waiting to know if the step sequencer is fixed before upgrading myself, I've had my share of buying broken features. Same for the MIDI effects actually.

Yea I've been upgrading no matter what, simply because I KNOW Sonar... I want to make music, not learn another DAW... but I know im probably wrong there.   

alewgro
Yea I've been upgrading no matter what, simply because I KNOW Sonar... I want to make music, not learn another DAW... but I know im probably wrong there.   

I don't think that's wrong at all.  The focus should always be on making music, not obtaining/learning the latest gizmo.  Last year I considered moving to Reaper, downloaded the demo, and couldn't get it to do much of anything.  That, and Sonar coincidently started giving me all sorts of strange problems which didn't get fixed until I re-installed Windows and started again.  Bottom line, I'm sticking with Sonar - I know it well enough that it allows me to focus on making music.

Oh yeah, Groove Quantize is also broken. It literally doesn't do anything. Like, zero effect.
 
So we have:
-Step Sequencer
-MIDI effects
-Groove Quantize
 
anything else? let's compile a list of features that we paid for that straight up don't work at all, just for fun
 
I mean, I'm well aware that Sonar is the best daw (theoretically anyway, if it worked), that's why I use it, I'm an exceptional producer and I'm gonna be well known one day, and boy am I gonna have a field day using my reach to expose in great detail to the music community how sonar doesn't ****ing work