[Fixed in X3e] Loop recording Bug Still in X3d (Since Sonar 8.5)

Video: http://www.youtube.com/watch?v=orETQsMhf9A
I think this Problem has been in Sonar at least since 8.5, but It might be older. It happens when loop recording MIDI with Input quantize turned on.
 
First problem is that while loop recording, subsequent loops won’t play all of the notes back you played in previous loops. Some of the MIDI notes are not played, but some are. When you stop recording and play back the track, it plays as expected.
Second, after the first pass, if you want to play notes on the beginning of the loop, but are early on your timing, (starting your notes at the end of the loop) then sonar will cut those notes short and place extremely short notes at the beginning of the loop that are often inaudible.
 
I like to build a song while recording, never stopping the transport, like people often do with beat machines. I know Ableton Live can do this, but If this one thing was fixed then I would be happy with X3.
Can others reproduce this? Does this bother anyone else but me? Am I one of the few Sonar users that like to work this way? Please let me know, I am quite curious.
 
Cris.

Yes, I always record Sound on Sound. If I was on overwrite mode, then I would not hear any notes from the past loops on subsequent loops.
 
Cris.

I can reproduce this.
 
STEPS
 
1) New project
2) Add a softsynth + patch
3) Set loop to be around 4 bars
4) Click and hold record and select sound on sound
5) Loop record several times.
 
EXPECTED
 
All MIDI Notes are being displayed.
 
ACTUAL
 
Not all MIDI Note are being displayed, a lot are missing loop after loop.
 
STEPS CONTINUED
 
6) Expand so you can see takelanes.
 
EXPECTED
You can see a new takelane created every time we see a new track.
 
ACTUAL
 
You don't see any takelanes created (maybe one).
 
NOTE
 
The all the tracks and takelanes get displayed one the stop button is pressed
The issue is purely to do whilst performing.
 
Thanks...

Well I've submitted CWBRN-22704
Cheers...

I know about the Comping default. As I said I always use Sound on Sound so that was one of the first things I changed when updating. The problem is the same in X3 as X2 for me. If you are getting it to work on your setup, I am quite curious as to what you did. Remember that the problem only occurs when you turn on Input Quantize for the track you are loop recording on. If you didn't turn on IQ, then it would work without missing any of the notes during loop recording.
 
Cris.

CakeAlexS
Craig I didn't just need MIDI quantise on....
 
Anyway to be specific I could reproduce all the issues in the video (there is more than one issue being explained), and for a change I'll make a comment (normally I try to say nothing after I've understood an issue and reproduced it, as it generally leads me into trouble, trolls start wailing in as I'm not allowed to have an opinion), but this is a bit of a dogs dinner and surprised more people haven't expressed an interest in fixing this, I remember this working in the earliest versions of Cake (maybe I am imagining) ... I'll refrain from saying any more.....

Again, people who don't agree with you. or cannot reproduce your issues are trolls?

.

Yeah, I have not tried loop recording without IQ turned on very much. However Sonar didn't always have IQ. I can't remember when they first put it in, but ever since, it has not worked as it should during loop recording. I remember petitioning Cake to put it in some years ago, and they didn't think it was necessary because of the quantize Midi effect plug-in. I guess I and others convinced them that the plug-in could not perform in the way we wanted to use the program so they made the quasi input quantize we have now, that is undo-able. True input quantize cannot be undone because it reduces the recording resolution (at least not without some parallel recording trickery).
Interestingly, IQ worked perfectly in Project 5, so Cake engineers have done this right before.
 
Cris.

CWBRN-22704 as been closed as reproducible but as intended (for what was reported see #5) - For the record this was what Cakewalk problem reporter says:
 
"Lanes are not generated until the stopping"
 
I guess what that means is that lanes existing inside some invisible buffer until you stop them and then they get generated.... which is weird... ? Really this is appropriate behaviour?

Mine was confirmed by CW and submitted to development today (CWBRN-22238). It's just about previous takes muting some notes while recording takes. Below are the steps and results I submitted:
 
1. Load the Normal project template.
2. Drag a soft synth, say, SI-Electric Piano, from the Browser to the blank space of the Track View (selecting either a simple instrument track or audio/midi tracks).
3. Go to Edit -> Preferences -> Project -> Record, and select "Sound on Sound."
4. Enable Input Quantize ("1/16").
5. Set a loop between, say, Bar 1 and Bar 8.
6. Start recording three different takes in the same section, say, between Bar 2 and Bar 7.
 
[Expected Results]
During loop-recording, you hear every note you recorded in the previous take(s).
 
[Actual Results]
During loop-recording, you only hear some of the notes you recorded in the previous take(s).

Jlien X, what is your BounceBufSizeMsec set to in Preferences->Audio->Configuration File? This is more my curiosity so I understand your setup better.
 
I have been leaving mine at 250 lately, but admittedly not been doing MIDI much these days. When I tested the OP above I had someone sitting here watching as I did, and didn't drop any notes (I did 5 passes on a 4 bar loop twice). I am also curious how much the interface drivers play into this equation, since I have been looking out for dropped notes lately and am not seeing this.

Input Quantize was the issue when I tested this. Although I had adjusted the value in that first test I do not recall the "Q" on the record button, which I got this go round, so I must have had input quantize off earlier.
 
I just ran this again quick to verify and with the input quantize on I get dropped notes regardless of BounceBufSizeMsec value. With it off, nothing dropped.

you would think that sync issues like this would take some type of priority in the 'to do' list. I am hoping to see some sync fixes in the X3E patch.

cris_core
Did you ever get any reply back from Cakewalk about the Bug report you submitted?

Not exactly sure who you are referring to but there were a number of bugs submitted and info is on those posts. #17 #18 and #19.
 
Cheers...

The notes dropping issue (post #19) is now fixed by X3e. Thank you bakers!