Problem With Bouncing Step Sequencers

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.

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.

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.

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.   

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

yeah they really need to hire testers that actually use the program to make music. no idea what the testers actually do tbh

Not saying this will work in your case, but many step sequencer oddities (and some other MIDI malfunctions, particularly missing notes on playback) are caused by the MIDI playback buffer being too small. If you've not already done so, try going into preferences/MIDI/playback and recording and if theMIDI playback buffer is anything less tham 500 (the default is 250) set it to 500 and try that. If there are still problems try 750. The buffer tells SOnar how far ahaed to read the MIDI data so there's time to processit. If the buffer is too small then it overflows and missed notes, sections missing on bounces and similar odd things happen.
 
For what it's worth I find the step sequencer very stable, and I use it a great deal.

bounce the step sequencer to a clip, and all is good.  doubt its a MIDI buffering thing.
 

Spencer
yeah they really need to hire testers that actually use the program to make music. no idea what the testers actually do tbh

I'm  assuming they test. I'm  also pragmatic enough to realize that with a program so vast, some scenarios are going to get missed during testing. I know when the 1st version of the step sequencer was released, I made tests for myself using what I thought were good common uses. It seemed to work great. After having attempted to use it for years, little quirks surfaced for me that altered intial asessment. Most of these things I am not sure I would call bugs. Even still, it was usable in a limited capacity in that I could make simple patterns and then bounce midi pattern to edit in prv, so I never thought step sequencer was broken...I just didn't  like it. Like Mettelus, I went with Geist for step sequencing drums and have not looked back.  I strongly suspect that in the test cycles, features like this that are lackluster but not screaming broken fall through the cracks because the issues are not on the radar. Look at the list of new features. None of them scream "run the step sequencer through every possibility". Changes to midi editing were made and probably were focused on more during testing. I don't  know if Cakewalk gets enough feedback from people regarding step sequencer to make it priority.