henkejs

@David Baay Thanks for your reply. Yes, I checked the Synth Rack, and AD2 is not there when I insert the edited track template. It's a little annoying to have to re-create an old AD2 template in Sonar, but apparently it's not a universal problem because old templates with other soft synths seem to be editable without issue.

@msmcleod Thanks for the reply. The VST scan didn't help, but I did some more testing. If I create a new AD2 track template in Sonar, it seems to work fine. There's something about the original AD2 template created in Sonar Platinum that goes haywire when edited and re-exported in the new Sonar. Since this is such an odd case and is easy enough to work around, I don't think it's worth exploring any further.

I just tested exporting track templates with a couple of different soft synths. They seem to work OK. There must be something different about AD2.

I have an old track template for Addictive Drums that consists of a folder with a separate track for each AD2 output. It was created in Sonar Platinum. Today I inserted the track template into new Sonar to tweak some settings and then exported the revised template to the default Sonar directory. When I tested the new track template by inserting it in a project, all the tracks came up as I had saved them but AD2 itself didn't load. To make sure I hadn't missed something, I tried reloading the original template and exporting it again. The same thing happened -- AD2 was missing from the new template. Next I opened a project in CbB and inserted the original track template there. After making some changes, I exported a new template and confirmed that it worked properly in CbB. Then I reopened Sonar and tried the new template there -- it worked. I don't know if this is a new problem with the latest Sonar update or if it goes back further than that. Either way, there appears to be a bug in how Sonar exports track templates that contain a soft synth.

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.

Line 6 support suggested trying their driver intended for PCs with Windows core isolation. Even though I don't have the core isolation feature, that driver works for me. The POD Go now appears in ASIO mode and I can record directly into Sonar over a USB connection.

Yes, it's strange that the POD does show up in Cantabile, but the options for selecting sample rate and bit depth are grayed out. By contrast, the sample rate and bit depth options for the Focusrite are available to be set in Cantabile. Edit: I should have added that the POD Go supports a range of sample rates that can be configured in ASIO, so those options should have shown up in Cantabile.

Yup, tried this then got a message from Sonar that there were no audio devices available. That was in ASIO mode. As noted above, the POD Go does show up in WASAPI. As Chaps suggested, this is looking like an ASIO driver issue. I've opened a ticket with Line 6 support and am waiting to see what they suggest.

The POD Go does show up in Sonar in WASAPI mode, though I need to experiment more to see whether it functions properly. When I installed Cantabile, the POD Go ASIO driver showed up as an option, but I couldn't access the configuration settings. I'll play around with WASAPI a bit more before deciding what to do next.

I'll do more sleuthing tomorrow. For now I can confirm there are no ASIO drivers in the registry besides the POD Go and the Focusrite.

Thanks for the replies. @Wookiee Realtek and Intel Display Audio (everything besides the Focusrite) are permanently disabled. When I tried the POD Go with the Focusrite turned off, Sonar told me there were no audio devices available. When I have time, I can try the POD Go again with the Focusrite disabled in Windows settings. @David Baay Yes, I'm using the latest ASIO driver from Line 6. The POD Go ASIO driver shows up in the registry. Is there a way to verify if Windows 10 is actually using it? Line 6 documentation is adamant that their ASIO driver is what you should use for best performance.