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?

Bang on schedule.... ;)

.

Cris,
 
Thanks we'll check it out, but be sure to go through support channels.
For dropped notes...  
Try increasing the value you have for Prefs-> MIDI -> Playback and Recording -> Prepare using nnn millisecond buffers.
In terms of playing notes early, yeah the logic there could probably be better.
 

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.

Keith,
Thanks for your reply. I tried as you suggested and got fewer dropped notes, but the problem was still there even with a setting of 1000ms. Does it make any sense to try an even higher setting?
 
Is this the sort of thing I should send to Tech support, or should I file a bug report.
 
Thanks,
Kevin.
 

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?

However CWBRN-22705 has been confirmed by Cakewalk (pasted below)..
 
Hello Playing looping MIDI is really buggy in X3D. Here are the steps to reproduce (a video can speak a 1000 words): http://www.youtube.com/watch?v=orETQsMhf9A I've already logged CWBRN-22704 which is demonstrated in this video, BUT that isn't what this particular issue is about, this is about where the MIDI notes land. Please note I've managed to reproduce this issue without MIDI quantize as well. 

Actual Results:  
Provided Specs: Hello Playing looping MIDI is really buggy in X3D. Here are the steps to reproduce (a video can speak a 1000 words): http://www.youtube.com/watch?v=orETQsMhf9A I've already logged CWBRN-22704 which is demonstrated in this video, but that isn't what this particular issue is about, this is about where the MIDI notes land. Please note I've managed to reproduce this issue without MIDI quantize as well. Discussion about MIDI looping bugs here: http://forum.cakewalk.com...85-m2955605.aspx 

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).

Noted...