Step sequencer, bounce to clip very strange behaviour

I've noticed this 'bug' for a while now but have finally got round to investigating it a little further. Does any one else see this bizarre behaviour? I can re-create this consistently.

First my work flow for drums:

I create my basic drum patterns using the step sequencer which will involve creating one or more sequences usually about 8 beats long but sometimes 4. I then copy one or more sequences several times, dragging a few out for a few bars, unlinking them and making a few minor changes, etc. Then when I'm happy with the basic feel I select 'bounce to clip' to turn them into midi clips for fine tuning, velocities, timing, etc for the 'real drummer' feel.

This is where the strange behaviour comes in. BTW all of these numbers in this example are arbitrary it doesn't seem to make any difference I could just as easily select the length of the song. If I select say 4 step sequencer clips that covers say 8 bars and select 'bounce to clip', the resulting clip is one or more bars shorter than it should be. Midi data seems to 'go missing' - Stranger still is if I 'undo' the bounce and then repeat the exact same "Select clips - bounce to clip - undo "sequence on the third time it works correctly i.e. no missing bars.

Am I crazy or does anyone else see this behaviour?

brundlefly


I don't use SS a lot, but have been experimenting with it lately. I cannot reproduce this in either 8.3.1 or 8.5.3 x64. You can consistently reproduce this in any project with any bounce of multiple SS clips?

I can't swear it's every project but I've seen it so often I'm pretty sure it is. It may also have something to do with the fact I'm working on linked/duplicate clips that are dragged out. There's so many variables it's difficult to try and eliminate them all. Today didn't seem to make any difference whether I selected the whole song 4 clips, 6, etc. Less than 4 doesn't seem to do it though.

The only consistent thing I've found so far is that it bounces correctly every 3rd attempt. I went through a project this afternoon 8 - 10 bars at a time and had the same behaviour every bounce. I was thinking WTF?

I'm going to start keeping notes and see if I can work out the exact cause. Twice this afternoon even the number of bars missing changed  I was really careful to make sure I was selecting in exactly the same method and selection length etc. Bizarre doesn't work first on second time but does on the third.

Only other thing I can think of is I have my drum track output to a drum map - mapped to an external drum machine. I can't see why that would make a difference though. Very odd..........

It should be easy to give CW a demonstration project. Next time you observe the behavior, undo the bounce and save the project. Then re-do the bounce, and if the behavior really does occur, zip up the saved project and send it to CW support. If it's a SONAR bug (and it does sound like it is) they should have no problem duplicating the error. If they can duplicate the behavior, they'll be able to easily determine what's causing it.

Sonar X3 STILL has this same issue. Im not buying any new version until I hear this is fixed.