WHY does Sonar Record in the wrong place???

[chamlin]

In my project, I set my loop, then within the loop, I set the record punch section. Record. Works fine. Then, without touching any settings, I hit record again, but this time, my recorded tracks are offset 7 measures forward, which results in the recording being misaligned, and 7 measures not recording. This is a persistent bug which has f'd up several great takes. Been using Sonar since day 1 and this has been happening ever since I "upgraded" from the free legacy Cakewalk to Sonar. Help?

[57Gregy]

I don't know but have you tried 'loop recording' instead?

[chamlin]

1 minute ago, 57Gregy said:

I don't know but have you tried 'loop recording' instead?

Thx, Greg. That is exactly what I'm doing!

[Wookiee]

9 minutes ago, chamlin said:

Thx, Greg. That is exactly what I'm doing!

You said set the punch in, that is not required if you are using the loop/comp recording that @57Gregy suggested. 

1. You set a loop points.

2. You enabled/arm the track for recording with the comp method selected, which is the default method.

3. Press the R to start recording each loop is recorded in its own take lane. No punch in needs to set.

[chamlin]

12 minutes ago, Wookiee said:

You said set the punch in, that is not required if you are using the loop/comp recording that @57Gregy suggested. 

1. You set a loop points.

2. You enabled/arm the track for recording with the comp method selected, which is the default method.

3. Press the R to start recording each loop is recorded in its own take lane. No punch in needs to set.

Thx, Wookie. I set the punch in / out because I want the loop to play a wider range than I'm recording to give me runway to be ready. That shouldn't cause this issue, should it?

[57Gregy]

38 minutes ago, chamlin said:

Thx, Wookie. I set the punch in / out because I want the loop to play a wider range than I'm recording to give me runway to be ready. That shouldn't cause this issue, should it?

I think setting 2 loops, basically, is messing something up.

[chamlin]

14 minutes ago, 57Gregy said:

I think setting 2 loops, basically, is messing something up.

If that's the case, then how does one do punch comp recording with enough lead in to best time when to come in... without recording on top of the existing track?

 

[Wookiee]

@chamlin punching in is an old method used with tape machines, it was used to literally punching in over the top of pre recorded takes overwriting , destroying, what was there.

With a modern DAW, there is no need to punch in. Just set your loop points as wide as you need. Then use comp recording mode to record as many takes as you need. Then using the comp function described on page 454 of the Sonar reference guide, you can not only pick the best take but pick the best bits of all the takes.

[msmcleod]

@chamlin - not seeing any issues with that workflow here.

I set an 8 measure loop, with a 4 measure punch in/out in the middle, and it's correctly recording the 4 measures every time.

What might be the issue, is:

"Then, without touching any settings, I hit record again, but this time, my recorded tracks are offset 7 measures forward, which results in the recording being misaligned, and 7 measures not recording"

Check your "On Stop, Rewind to Now Marker" setting in TV Options.  If this is unchecked, and you don't touch anything before pressing record again, then recording will start where you left off (assuming that's between the punch points).

I'd recommend either:

- Making sure  "On Stop, Rewind to Now Marker" is checked, and ensuring the now time is at the beginning of the loop before you start recording (pressing W once or twice will ensure this).  Then when you stop, it'll automatically rewind back to the beginning of the loop for you, so you can immediately press R.

OR
 
- Get into the habit of pressing W before pressing R again so you start at the beginning of the loop.

If neither of these solves your problem, please post a video of what is happening ( Screen2Gif  is a free and easy to use utility for grabbing screen videos).  Be sure to record the whole screen, as the state of other options in the control bar may give us a clue to your setup and what could be causing the issue.

[chamlin]

7 hours ago, msmcleod said:

- Get into the habit of pressing W before pressing R again so you start at the beginning of the loop.

Thank you. Yes, I always press W prior to R... AND, if I didn't, the playback in my headphones would be playing in the middle of the section and I'd definitely know it so I would stop and hit W. So I don't see how this will ultimately be the issue. Good input though.

I would do the screen recording but the issue "appears to be" random. I can't make it happen. But if there is a next time, I'll do a full screenshot. Thanks!

[David Baay]

In the past mis-located recordings have sometimes been related to metronome count-in and/or specific interfaces. Try disabling count-in and let us know your interface and driver mode.

[chamlin]

15 minutes ago, David Baay said:

In the past mis-located recordings have sometimes been related to metronome count-in and/or specific interfaces. Try disabling count-in and let us know your interface and driver mode.

Thx, David. Not using a count in. The tracks have the drummer counting us in over his Room Mic.

[reginaldStjohn]

Are there any tempo changes in the song? I have seen issue like this at times when tempo changes are in the same area as I am recording.

[chamlin]

1 hour ago, reginaldStjohn said:

Are there any tempo changes in the song? I have seen issue like this at times when tempo changes are in the same area as I am recording.

No tempo changes, but thanks for responding!

[chamlin]

This happened again. I've taken a snapshot of the screen with the control bar to see if that offers any info. Please see the attached note in the image.

1. Loop was set, then punch record was set within the boundaries of the loop.

2. Made sure the NOW time was set to the beginning of the loop

3. Looped 6 times (6 takes)

4. But instead of the vocal sitting where it was sung, SONAR has again offset the vocal.
     A. The beginning of the vocal is cut off
     B. The vocal in the clip should sit later in the clip than it does

NOTE: I have been using this exact same process flawlessly all day... until SONAR killed a good take just now. 😭

• There are situations when punching is easier in my workflow. I do often just loop record, but when there are lots of clips around where I'm recording, it's irritating to keep having the clips disabled by the new recording. Thus, punching suits the situation.
• Staff confirmed that having both loop and punch enabled should work
• No tempo changes
• Now time is always at the beginning of the loop prior to hitting record
• No metronome count-in being used

[John Vere]

What is interesting is this was a bug I reported but it was with Cakewalk Next? Punch ins were about 2 measures late. They fixed it eventually but it took submitting 3 videos over a few months to finally get attention. This was When it was first released as a beta version. 

[chamlin]

13 minutes ago, John Vere said:

What is interesting is this was a bug I reported but it was with Cakewalk Next? Punch ins were about 2 measures late. They fixed it eventually but it took submitting 3 videos over a few months to finally get attention. This was When it was first released as a beta version. 

Well, it's in my paid version of Sonar and very flow-breaking, for sure.

[sjoens]

Curious if it's a buffer or latency issue with the interface...

[chamlin]

2 hours ago, sjoens said:

Curious if it's a buffer or latency issue with the interface...

Is it possible that that is the reason that it does in sporadically?

[sjoens]

I've learned anything is possible anymore.