Hi, So I build computers for a living and I built my best friend a kickazz computer.
Solid State Hard Drive, Intel i7 Cpu... 2 - 1Tb WD Caviar HD's for storage etc. 16 gigs of ram.
 
He has Sonar x2 installed on the Solid state hard drive. He plays bass and I play guitar.
Yesterday, he used punch in record for me and looped it over the verse and I recorded about 25 different takes...Different styles, different melodies etc. Well....when he stopped it. The takes were WAY off timing. Not even close. But when we do one single take its fine.
 
Any suggestions? Any tweaks I can help him make? The computer is a beast and should have no problem handling that.
Thanks
J

Looping & punching at the same time should work PROVIDED your loop & punch start/stop points are exactly the same.

I've had this myself.

Why set "Punch" points and "Loop" points?
You can "Punch In" on a single pass.
IF you loop and punch, each successive "Punch" will get placed later and later.
Just set your loop points with enough "pre-roll" and "post-roll".
Slip edit the results; PITA, but that's how it works in the X series.
Basic function every DAW should have (loop & punch), but somehow Cake let it slip by.

Tom

DeeringAmps : "IF you loop and punch, each successive "Punch" will get placed later and later. "

Is this a bug (wouldn't be the only looping bug) or is there a logical reason for it ?

I don't see why multiple passes should be any different than a single pass ?

It would be "interesting", to say the least, to hear someone "explain" why its "acceptable" or "intended" behavior.
Let's be honest, X1 was rushed to market.
"Hot fixes", "Patches" followed in rapid succession.
The Tech boys (and girls?) broke for the Xmas Holidays (2010) with X1 in total chaos.
Somehow we ALL missed it, the "punch" issues I mean.
Evidently most just "Loop" a section and record multiple passes until we get it right.
And you're right, looping has some other issues.
Sometimes my VSTi's just "fall apart" when looping; its random (maybe I had a "Punch" set?)
T

Have effects/ plugin causing latency on the inputs?   I also have all bins turned off while recording  Use the FX button for that

I've personally not had good luck punching in with Sonar. I've had better luck with older technologies, such as my trusty old Yamaha AW4416 when it comes to punching in, so what do is just add another Take Lane and arm it. Then I can just play whenever I want and there's never any latency or compounded latency issues for me. 

THe one thing you did not mention in the computer beast...... what soundcard is being used? 

I have "issues" with the RME and the Tascam.
ASIO drivers, both are set to "Use Reported Latencies".
Its Sonar, not the card; at least in my experience.
First pass, Sonar handles the "Punch" correctly; after that each pass gets later and later.
You CAN NOT "Loop" and "Punch In" with Sonar X1 or X2; in my experience at least...

T

It used to be that loop recording in ASIO was broken (gaps at the loop end) and it's now probably fixed. But now punch-in along with loop is broken, so it can't be used for looping purposes. Haven't heard anyone say it's acceptable or intended.