Once you have that functionality as per Studio One you will never go back.  It can do it either way.  Into one clip or multiple clips.  I do a lot of midi recording and being able to add midi data to just one clip is very good indeed.  As many other DAW's do it too.  In fact Studio One takes it further.  You can set up multiple tracks and switch to them on the fly with the Up/Down arrows and add midi data into any of them.  You get the new sound/instrument the moment you land on that track.  All while in record.  Gapless of course.  Sonar could really improve this situation. 
 

The only complaint I think is justified is that you don't see the notes of all clips in the parent track; Bounce to Clip or Flatten Comp takes care of that in pretty short order, and pretty much everything else you described happening in SONAR just isn't accurate.
 
SONAR won't record a clip if no notes are played, so the 6 passes with a 'rest' in between each take will only produce 3 take lanes. If you play extra notes in the 7th pass as he did, it's easy enough to delete the 4th take lane, which I assume you would also have to do in Studio One. But if it were me, I would just avoid playing the extra notes in the first place.
 
And if you're recording in Sound on Sound mode as suggested earlier in this thread, there won't be any 'comping' to do.

brundlefly
The only complaint I think is justified is that you don't see the notes of all clips in the parent track; Bounce to Clip or Flatten Comp takes care of that in pretty short order, and pretty much everything else you described happening in SONAR just isn't accurate.
 
SONAR won't record a clip if no notes are played, so the 6 passes with a 'rest' in between each take will only produce 3 take lanes. If you play extra notes in the 7th pass as he did, it's easy enough to delete the 4th take lane, which I assume you would also have to do in Studio One. But if it were me, I would just avoid playing the extra notes in the first place.
 
And if you're recording in Sound on Sound mode as suggested earlier in this thread, there won't be any 'comping' to do.

You're wrong about the having to delete a take lane in Studio One.  If you watched the video,  you would see that there are no take lanes at all.  Any over lapping notes are not recorded,  just as it would be on a drum machine.  In Sonar,  you would still have to comp the hi hats,  or as you said,  delete them.  Also,  you admitted that to see one consolidated clip in the arrangement that contains all of the midi data would still require you to bounce to clips or flatten.  Any way you look at it,  Sonar requires several additional steps that aren't required by most other sequencers or DAWs that have the ability to turn off take lanes.  Those extra steps make composing simple midi loops in Sonar very cumbersome IMHO.

Jeff Evans
Once you have that functionality as per Studio One you will never go back.  It can do it either way.  Into one clip or multiple clips.  I do a lot of midi recording and being able to add midi data to just one clip is very good indeed.  As many other DAW's do it too.  In fact Studio One takes it further.  You can set up multiple tracks and switch to them on the fly with the Up/Down arrows and add midi data into any of them.  You get the new sound/instrument the moment you land on that track.  All while in record.  Gapless of course.  Sonar could really improve this situation. 
 

That's my point entirely.  Sonar started out recording everything in to one clip,  and that approach definitely has it's advantages in certain situations,  enough so to justify the ability to at least have it as an option,  even though take lanes have been added to the program.

Comping mode has its uses.  One of my major frustrations was that Sonar forced me to use comping mode regardless of what settings I put in the preferences.  If I recall correctly, it forced me to create new Take Lanes and to use comping mode.  It seems to only respect the settings for audio and not MIDI. 
 
After that experience, I decided to change my workflow and never try loop recording MIDI again.  I've pretty much completely eliminated using comping with virtual instruments. . . I just record each take to a new track now. :D

rlared
Comping mode has its uses.  One of my major frustrations was that Sonar forced me to use comping mode regardless of what settings I put in the preferences.  If I recall correctly, it forced me to create new Take Lanes and to use comping mode.  It seems to only respect the settings for audio and not MIDI. 
 
After that experience, I decided to change my workflow and never try loop recording MIDI again.  I've pretty much completely eliminated using comping with virtual instruments. . . I just record each take to a new track now. :D

If you are going to use Sonar,  you don't have a choice.  I'm glad that you were able to adjust your workflow and it's not really an issue for you anymore.  I still think it should be an option in Sonar,  and I really just don't understand why it isn't.

kb420
Any over lapping notes are not recorded,  just as it would be on a drum machine.

 
I hope that's optional. What if you want to record a deliberate flam or a grace note.
 

In Sonar,  you would still have to comp the hi hats,  or as you said,  delete them.  Also,  you admitted that to see one consolidated clip in the arrangement that contains all of the midi data would still require you to bounce to clips or flatten.  Any way you look at it,  Sonar requires several additional steps that aren't required by most other sequencers or DAWs that have the ability to turn off take lanes.  Those extra steps make composing simple midi loops in Sonar very cumbersome IMHO.

 
I don't dispute that 'merge' or 'drum-machine-style' would be convenient for some purposes, workflows, and compositional styles. I just think the necessity of it is overblown, and the many advantages of keeping SoS parts in lanes is being overlooked. I guarantee there are lane- and clip-based procedures that I use routinely to arrange parts that would take significantly longer working in a PRV due to having to constantly re-define selections that aren't already isolated. And I'd rather find out later that I need to take a moment to consolidate separate parts than that I need to separate consolidated parts to use with another synth/channel or that I lost unison notes while recording horn section harmonies.
 
 
 

brundleflyI hope that's optional. What if you want to record a deliberate flam or a grace note.

 
It is optional in Cubase and Studio One 3.   That's the beauty of having options.
 

brundlefly
I don't dispute that 'merge' or 'drum-machine-style' would be convenient for some purposes, workflows, and compositional styles. I just think the necessity of it is overblown, and the many advantages of keeping SoS parts in lanes is being overlooked. I guarantee there are lane- and clip-based procedures that I use routinely to arrange parts that would take significantly longer working in a PRV due to having to constantly re-define selections that aren't already isolated. And I'd rather find out later that I need to take a moment to consolidate separate parts than that I need to separate consolidated parts to use with another synth/channel or that I lost unison notes while recording horn section harmonies.

 
There are advantages,  and I'm not overlooking anything, especially when it comes to audio as I've said before.  I just think there should be an option to chose how you want to work, especially with midi.
 
You think the necessity of it is overblown.  That's your opinion,  and you're certainly entitled to you're opinion.  Obviously,  Cakewalk agrees with your opinion since they don't give you an option at all.  Personally I disagree,  and obviously many of the other DAW makers out there share my opinion because they actually give you a choice of whether you want to use take lanes or not.  

brundlefly
The 'comp clip' in the parent track behaves like a single 'merged' clip, and it's so easy to bounce to clips or flatten comp, I really don't see how this is such a showstopper for anyone. I wouldn't object to having the option, but personally, I would almost never choose to overdub to the same clip; editing and arranging MIDI drums is much easier with different kit pieces in different lanes.
 
Here are a few quick examples of things you can't do with a merged clip:
 
- Slip-edit and then groove clip different parts to start/end/repeat at different intervals.
- Split, copy, cut, paste, drag and mute chunks of individual parts in the track view to build an arrangement.
- Try out different patterns of the same part.
- Have all hi-hat or hand drum articulations kept together but easily isolated from other parts.
- Apply MIDI FX to individual parts as Clip FX.

I totally get that and indeed there have been instances when I have actually chosen to have different drums in different lanes, however that's just one way of working. I guess it depends on where you came from and perhaps even the genre as well. Many people approach drum programming from a drum machine perspective where you would leave it looping and layer the parts, ending up with everything visible in one clip. Some would say it's just easier and "tidier" to work with and see everything in one clip, and for the most part I agree with them. I guess there's a reason why other DAW's have this functionality, and that's because it's popular. I agree that it's not a showstopper, but it does contribute to a niggling sense of user unfriendliness. 

sharke

brundlefly
The 'comp clip' in the parent track behaves like a single 'merged' clip, and it's so easy to bounce to clips or flatten comp, I really don't see how this is such a showstopper for anyone. I wouldn't object to having the option, but personally, I would almost never choose to overdub to the same clip; editing and arranging MIDI drums is much easier with different kit pieces in different lanes.
 
Here are a few quick examples of things you can't do with a merged clip:
 
- Slip-edit and then groove clip different parts to start/end/repeat at different intervals.
- Split, copy, cut, paste, drag and mute chunks of individual parts in the track view to build an arrangement.
- Try out different patterns of the same part.
- Have all hi-hat or hand drum articulations kept together but easily isolated from other parts.
- Apply MIDI FX to individual parts as Clip FX.

I totally get that and indeed there have been instances when I have actually chosen to have different drums in different lanes, however that's just one way of working. I guess it depends on where you came from and perhaps even the genre as well. Many people approach drum programming from a drum machine perspective where you would leave it looping and layer the parts, ending up with everything visible in one clip. Some would say it's just easier and "tidier" to work with and see everything in one clip, and for the most part I agree with them. I guess there's a reason why other DAW's have this functionality, and that's because it's popular. I agree that it's not a showstopper, but it does contribute to a niggling sense of user unfriendliness. 

the video I posted on the previous page (though I know its not what most want) shows me doing just that.
Looping a drum part over and over adding in each kit piece one at a time. I still do the same thing now and then fine tune edit my drum parts in the PRV.
 
All that is need is to select the region after looping/recording is complete and select "Bounce to clips" and it all remains one clip. I don't know maybe im misunderstanding something. At any rate it would be nice to have an option for those who need it, myself I don't but I still understand we all work differently.