Noel Borthwick [Cakewalk]

skinnybones lampshade
I would also be very grateful if loop and punch were fixed in X3e; it suits the way I work very well.
 
One question about comping: When I'm listening back to what I've recorded and hear a clip or two that make me say, "Yuck!", I'd like to immediately be able to make a mark on that clip as it's playing (like a red X or something similar). That way, I'll be alerted later that, even though 9/10ths of the clip may sound better than in any other take, there's at least one little thing on that clip that I caught as very wrong and that needs to be addressed. I don't necessarily want to have to stop to correct it at the time, but to remind myself to do so later.
 
Would anyone know if such a thing is possible? Thanks!
LJ

 
You can dynamically drop in a marker at that point so you can return to that point later. There is a hotkey to add a marker at the now time (don't remember what it is)

Hit "m" to add a marker at the now time.

Noel Borthwick [Cakewalk]

DeeringAmps
Just don't set Sonar to "loop" and "punch" at the same time!
Still my biggest gripe to date.
Fix Loop & Punch for Cris Sake!
 

This is fixed in X3E. We spent a lot of time addressing testing and various permutations of loop recording and autopunch.
Properly the boundary cases with latency compensation under these scenarios especially when dealing with loopback is a lot harder than it may appear on the surface.

But Noel - it's just a few lines of code

Noel Borthwick, you rock! Thank you for answering my question about marking a clip with a hot key on the fly, and for the great news that loop and punch is fixed in X3e. Very happy here.

LJ

jb101

Noel Borthwick [Cakewalk]

skinnybones lampshade
I would also be very grateful if loop and punch were fixed in X3e; it suits the way I work very well.
 
One question about comping: When I'm listening back to what I've recorded and hear a clip or two that make me say, "Yuck!", I'd like to immediately be able to make a mark on that clip as it's playing (like a red X or something similar). That way, I'll be alerted later that, even though 9/10ths of the clip may sound better than in any other take, there's at least one little thing on that clip that I caught as very wrong and that needs to be addressed. I don't necessarily want to have to stop to correct it at the time, but to remind myself to do so later.
 
Would anyone know if such a thing is possible? Thanks!
LJ

 
You can dynamically drop in a marker at that point so you can return to that point later. There is a hotkey to add a marker at the now time (don't remember what it is)

Hit "m" to add a marker at the now time.

That doesn't help if you're checking 5 takes. I also like the suggestion of marking a clip positively or negatively during playback. Like I do with my photos in Lightroom.

Thank you, jb101, for telling me that the hot key I need to use is "m". "M" stands for Much appreciated!

LJ

Yes, Sanderxpander, you said it much better than I did, but what you said is what I really was looking for: to be able to mark clips positively or negatively or even as a "maybe" on the fly during comping involving many takes.
Thanks,
LJ

I often do this with colors now but it takes way too long. Would love to be able to hit 1 through 5 for "stars" like in Lightroom photo grading!

I use comping for vocals a lot but I still punch in most of all my stringed instruments.
been doing it this way for years, old habits are hard to break. but for me its more about flow.
get it right, get it done, finished.
 
creating too many comp tracks for me I seem to lose something in there, the groove, sure but more importantly, the flow, the main idea, the reason I wrote the song, comping can turn that in to an over produced version sometimes.
 
 
less we forget, sometimes mistakes make a song more realistic.
jimmy page will testify to that, as he is one of my favorite song writers, producers.

Anderton
 
But Noel - it's just a few lines of code

Yep but lines written in blood :) Between the record code, looping, autopunch and delay compensation you have 4 of the most complicated areas of code in SONAR. The number of permutations of cases of things to test there is huge. Keith made a spreadsheet to enumerate just the normal use cases! The tricky part (and root of the original problem) was dealing with buffers that don't perfectly line up with the loop region. This is why this bug could appear to be intermittent. Depending on the latency, position of the loop end and the asio device latency, you may or may not have even seen the problem. It took several weeks of fixes and regression testing to get to the bottom of this one.
 

Noel Borthwick [Cakewalk]
Between the record code, looping, autopunch and delay compensation you have 4 of the most complicated areas of code in SONAR. The number of permutations of cases of things to test there is huge. Keith made a spreadsheet to enumerate just the normal use cases! The tricky part (and root of the original problem) was dealing with buffers that don't perfectly line up with the loop region. This is why this bug could appear to be intermittent. Depending on the latency, position of the loop end and the asio device latency, you may or may not have even seen the problem. It took several weeks of fixes and regression testing to get to the bottom of this one.

I guess this reveals me as a total geek, but that was really very interesting. It's not often us mortals get to peer behind the curtain and get a glimpse of what life is like in code-land.
 
It's great that you'll willing to come in here from time to time and help explain what makes SONAR tick. Just don't do it too much, or my head will explode. I had a hard enough time getting a pixel to bounce around on the screen of a Commodore-64.