Sonar Doesn't Recognize Line 6 POD Go -- Solved

[henkejs]

There are many threads here about interfaces not being recognized, but none of the solutions I've seen in those other threads have worked in my situation. I installed the Line 6 ASIO driver for the POD Go, then connected the POD Go to a USB port. Windows recognizes the POD Go and plays the audio test jingle properly, but the POD Go does not show up in the device preferences in Sonar or CbB. 

I've tried renaming the AUD.INI files before starting Sonar and CbB. I've tried shutting off my regular Focusrite interface and then rebooting the PC with only the POD Go powered up. Again it shows up in Windows, but Sonar says there are no audio devices available.  You're supposed to be able to record the POD Go guitar outputs directly through USB. You're also supposed to be able to use the POD Go as a reamp device for previously recorded tracks. That is the main reason I'm trying to get this to work. 

Any ideas?

[Wookiee]

@henkejs do you have any other audio devices or drivers active? Try disabling them all, HDMI, Realtek etc. and trying again. 

[David Baay]

2 hours ago, henkejs said:

installed the Line 6 ASIO driver for the POD Go, then connected the POD Go to a USB port. Windows recognizes the POD Go and plays the audio test jingle properly, but the POD Go does not show up in the device preferences in Sonar or CbB. 

Did you download the latest ASIO driver from Line6? I Googled and saw some posts saying the ASIO driver didn't load properly in Win11 until updated last March. My guess is Windows is using it as a WASAPI device so it doesn't matter that the ASIO driver is not loading. If all else fails, try changing CbB to WASAPI mode.

Edited February 23 by David Baay

[henkejs]

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.

[Chaps]

7 hours ago, henkejs said:

Any ideas?

If it were me, I would run Cakewalk in a different driver mode, like WASAPI Shared. If the device shows up in your Cakewalk Audio Devices, and you are able to play and record from it, that would suggest that an ASIO driver was the problem. It is possible that your problem is caused by an ASIO driver that is installed but you are not using. I had this problem when a Steinberg Low-Latency driver was interfering with the Yamaha Steinberg driver I needed to use for ASIO. I suggest you search your registry for HKEY_LOCAL_MACHINE\SOFTWARE\ASIO to see what other ASIO drivers are installed in that folder and delete them.

You can search the Internet for HKEY_LOCAL_MACHINE\SOFTWARE\ASIO and you will find many examples of people solving ASIO problems by deleting unneeded ASIO drivers from that folder.

[henkejs]

5 hours ago, Chaps said:

If it were me, I would run Cakewalk in a different driver mode, like WASAPI Shared. If the device shows up in your Cakewalk Audio Devices, and you are able to play and record from it, that would suggest that an ASIO driver was the problem. It is possible that your problem is caused by an ASIO driver that is installed but you are not using. I had this problem when a Steinberg Low-Latency driver was interfering with the Yamaha Steinberg driver I needed to use for ASIO. I suggest you search your registry for HKEY_LOCAL_MACHINE\SOFTWARE\ASIO to see what other ASIO drivers are installed in that folder and delete them.

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.

[Starship Krupa]

14 hours ago, henkejs said:

The POD Go ASIO driver shows up in the registry. Is there a way to verify if Windows 10 is actually using it?

At this time, ASIO isn't something that Windows "uses." It's a proprietary technology that Microsoft are working on integrating into Windows, but haven't yet done so.

That said, if you can play sounds through the POD Go, Windows is at least recognizing it as a class-compliant audio device, which means that it should be showing up in Sonar as an available WASAPI device.

Do you have other audio software that uses ASIO that you can run to see whether the POD is recognized by it? That would help avoid finger pointing when trying to get help from Line 6. Cantabile Lite is one freebie that you could try.

[henkejs]

2 hours ago, Starship Krupa said:

Do you have other audio software that uses ASIO that you can run to see whether the POD is recognized by it? That would help avoid finger pointing when trying to get help from Line 6. Cantabile Lite is one freebie that you could try.

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.

[57Gregy]

Try it with the POD plugged in /Focusrite unplugged before you turn on the computer.

[henkejs]

24 minutes ago, 57Gregy said:

Try it with the POD plugged in /Focusrite unplugged before you turn on the computer.

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.

[Starship Krupa]

So it works in WASAPI mode, but when you try to switch to ASIO, the POD vanishes. Yet Cantabile does show the POD when it is configured to use ASIO.

This is unusual. I don't know that I can remember someone having this problem. Usually if one program can run the interface in audio, they all can.

Interested to see what the solution turns out to be.

[henkejs]

9 hours ago, Starship Krupa said:

So it works in WASAPI mode, but when you try to switch to ASIO, the POD vanishes. Yet Cantabile does show the POD when it is configured to use ASIO.

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.

Edited February 25 by henkejs
Additional information

[mettelus]

1 minute ago, henkejs said:

but the options for selecting sample rate and bit depth are grayed out.

Check your Windows Sound Settings for this quick (Sound Settings->Sound Control Panel in the upper right). Be sure the POD Go is not set as your default device, and also that Windows does not let apps get exclusive control of it (right click->Properties->Advanced tab at the top). The first app that touches an interface gets control of it (why sample rate and bit depth will lock), but if exclusive mode is enabled, that may be taking it out of the loop for use by other apps in ASIO mode.

[henkejs]

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.

[David Baay]

1 hour ago, henkejs said:

core isolation

Had to Google that one. Sounds distinctly like not a good thing to have enabled on a DAW in General. In case you haven't already, and just to be sure, you should check the security setting mentioned in this decription (probably a bunch of AI misinformation, but FWIW):

How it works

Core isolation runs core processes in a virtualized environment that's isolated from the rest of the system 

It protects against malware and other attacks by isolating computer processes from the operating system and device 

It prevents malware from hijacking high-security processes 

How to enable or disable 

Open the Windows Security app

Select Device security

Click Core isolation details

Click the toggle under Memory integrity to turn core isolation on or off

Restart your device for the changes to take effect

Known issues 

Some devices or software may have trouble running with Core Isolation enabled

 

Edited Thursday at 05:29 PM by David Baay

[Starship Krupa]

2 hours ago, henkejs said:

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.

Hmm.

My guess is that the "core isolation" driver may have some fixes applied to it that have nothing to do with core isolation.

Really strange that Cantabile could use the other one and Sonar could not.

Thanks for posting the solution.