henkejs

Other people know much more about this than I do, but a quick search tells me FL Studio uses ASIO4ALL, a driver known to cause issues with Cakewalk. Try removing or disabling ASIO4ALL. Also your Sync and Caching screen shows a Record Latency Adjustment value for FL Studio. The device selected there should be the Focusrite. Finally, you might experiment with the buffer size settings. Sometimes a value more in the mid-range works better. But try to take care of the other issues first. Hope this helps.

Yes, it's working now. Thanks to everyone involved!

We are being told in this thread that local help can be installed via Product Updates, but for some of us it simply doesn't show up there. Does everyone who wants to use local help have to contact Cakewalk Support?

As an experiment, I copied the sonar.chm file from Platinum (dated 2017) into the directory with the new Sonar executable. That help file displays in new Sonar even though it's out of date. Still no sign that Sonar recognizes this file needs to be updated.

That's the problem -- local help doesn't appear on the update tab.

I've been hoping for this, but not seeing it here in spite of having the option set. Update: When I set the local help option, it is unset the next time I open Sonar.

Here too. It's not that it's unusable now, but it does slow you down.

Same problem here. No installer, no reference in the Product Center. The only sonar.chm file anywhere on my system is one for Platinum from 2017.

I don't use it, but it still shows as a regional effect for me.

If this has been explained in another thread, I couldn't find it. Why does the Cakewalk Product Center show these add-ons as not installed? I got all these years ago with earlier versions of Sonar, and they've been working fine in CbB and new Sonar. I used the Product Center to install the Drum Replacer just to see what would happen, and that one now shows as installed. As far as I can tell these add-ons are not updated versions, so is there any reason to re-install them other than to see them recognized by the Product Center?

Are you stopping to listen to the first couple of takes and then starting to record again to the same track? That might cause a take from the previous recording to play when you start recording again. Just speculating here -- I haven't explicitly tested this.

Yes, I understand the concept. I have such a simple approach to recording this just doesn't seem to be much of a problem for me. I don't play drums, so I use AD2 and EZD3 most of the time. No added samples. No double kicks. I almost never mix an amped and a DI signal for guitar or bass. However, I do watch (listen) for instruments that are competing for sonic space in the mix, and I always check my mixes in mono before exporting. For me personally, phase alignment is pretty far down the list of problems with my recordings. 😄

I don't track drums, so multiple microphones are rarely an issue for me. If I use two microphones on an acoustic guitar, I'll adjust the positions by ear.

Does anyone know if we have to leave Scaler 2 installed for compatibility with old projects?

Right era for me. But, no, I never recorded it.