Eggzin

So far, everything I've tried has failed. The issue is the Asus laptop. I'll continue to look for a solution and if I find one, I'll report back.

Update: Well, I installed Reaper and Pod Go on this, now, clean Windows 10 OS, and I still have the same issue. As I mentioned, I have two laptops, both running OS 10. My music laptop is an Asus, the other is a Lenovo. On the Lenovo, Pod Go and Reaper work together seemlessly. Not so on the Asus. This morning, I went into the registry of both machines to compare them--HKEY Local Machine\Software. There are definitly missing items in the Asus that are present in the Lenovo. I made a list of the differences, and now have some Google searching to do. Before I do that, I'm going to uninstall the native sound card and drivers (Conexant SmartAudio) in the Asus. Then I'll uninstall PG Edit and reinstall to see if there is/was a conflict with drivers. I'll report back.

Update: I spoke with Line 6 support yesterday for an hour and forty-five minutes! He had never seen this issue. We went through everything, a lot of which I'd already tried. I learned a lot working with him. At the end though, still had the same issue. At his suggestion, I did a reset of the Windows OS. I haven't had a chance yet to reinstall Reaper and Pod Go. I'll do that tomorrow, test, and report back. Paul

Thanks Silverhead. ASIO4All is definitly not on the computer. In fact, I deleted all drivers in the registry via this path HKEY_LOCAL_MACHINE\SOFTWARE\ASIO, and in the device manager. There wasn't anything left on my computer, music related, when I was done uninstalling and deleting. I'm off to phone support. I'll report back.

Just an update. I uninstalled everything Line 6 related on my laptop this morning and did a fresh install of Pod Go Edit. No success, same as before. Then I tried my other laptop, with the same Windows 10 OS. I already had PG Edit installed, so I installed Reaper. And lo and be-freaking-hold, Reaper recognized all asio inputs and outputs. So there's something about my first laptop (which is what I use for music stuff), which doesn't allow the linkage. Still plan to phone Line 6 support when they open later today.

Pod Go is the only Line 6 product I have, so I'm okay there. (Did have a Pod 2.0 decades ago.) :>) After I posted to you this morning, I did some more google searching and came across this. It's from a guy on the Cakewalk forum who was having the same trouble I've had. This was suggested to him by another member: https://discuss.cakewalk.com/topic/84097-sonar-doesnt-recognize-line-6-pod-go-solved "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." I'll likely do the same myself--delete Pod Go asio drivers in the registry, make sure I delete drivers in the Device Manager, even un-install PG Edit in the Windows Control Panel >Programs and Features, restart laptop, then install PG Edit again, fresh. Josh Steck at Line 6 support did mention the registry in his initial reply to me.

Wow Silverhead, I'd have completely missed doing this! Thanks--you've been a great help. It looks like I'll have a little time tomorrow morning (EST) to try this.

Thanks for the clarification Silverhead. This is tough stuff to handle in a thread type environment, so every nuance is important. I did open a ticket on Sunday, and heard back on Monday and he (Josh) and I had several exchanges, but ultimately he couldn't help. He suggested I call support. That'll make it difficult because of the limitations, time-wise, that support is available and my work schedule. Just as a matter of interest, I had some thoughts. I realized later, after un-installing Edit, then re-running the Edit .exe, that some of the drivers were not removed during the un-install. I looked at the "details" of the installation process, and saw that the re-installation skipped installing new drivers because they were already existing in the Device Manager from previous installs. So, while I look for a opportunity to phone Line 6, I may delete by hand, any Line 6 drivers that show up in the device manager, and try re-installing Pod Go Edit again. Paul

Thank you for the follow up. I had seen that video already, before you posted it--it actually was the best of all the videos I've watched, working through this. But, no, I don't have the same options as he did. One thing that caught my ear though, is that at 18 seconds in, he says "you want to install 2 things from the Line 6 website. ...the Line 6 Pod Go Edit software and the Line 6 Pod Go drivers". What is he talking about?! According to several Line 6 Experts here in this forum all that's needed is the Pod Go Edit software because everything you'll need is in that software. What additional "drivers" are needed? Besides which, I've already tried to add several drivers from that download page with PG Edit already installed, to no avail. Do you have any idea what he's talking about when he says two things?

Anybody have any thoughts?

I went ahead and uninstalled Pod Go Edit, and then re-installed. Still no joy, Reaper's still not seeing the 4 channels. I then went into my Device Manager on my computer. I saw an option to "show hidden files". When I clicked on it, suddenly 4 "Digital Audio Interface (Line 6 Pod Go)" and 4 "Speakers (Line 6 Pod Go)" showed up. The problem is that 3 of them, in each catagory, were greyed out. Only one of each is not greyed out. I double clicked on one of the greyed out Interface icons to get to "properties" and the Device status says "Currently, this hardware device is not connected to the computer (Code 45)". I thought this added info might help you to help me :>)

Yes, I meant ASIO drivers. Do I need to uninstall Pod Go Edit first, before installing again? Thanks for the help with this!

Thanks for your suggestion. From recent reading on the net, Pod Go is supposed to contain the drivers that Reaper needs to see the four channels. I can try a search for Reaper usb drivers, but I've been down so many rabbit holes so far... :>)

Siverhead, well, I installed Reaper and I'm having the the same problem as with Audacity. In another line 6 post I saw that you and Phil M said, all the needed USB ASIO drivers are inside Pod Go Edit. I already had PG Edit installed before I even started troubleshooting the problem--Reaper still didn't recognize all PG's channels. Since then, I've downloaded and installed two separate drivers from the Line 6 website to no avail. I'm pulling my hair out... So this was the process I followed: In Reaper, I open preferences > Audio device settings, and select ASIO. Under ASIO Driver, it shows ASIO Pod Go, but in the next fields, under Enable Inputs and Output Range, the dropdown's show nothing--just a blank page. Nor can I open the ASIO Configuration button close to the bottom of the page. I have already downloaded and installed two drivers from the Line 6 Pod Go software downloads page. Neither of them solved the issue. The first was “Line 6 POD Go Driver2_5”. The second was “ Line 6 WinUsb”. Do you think it's worth uninstalling Pod Go Edit and then re-loading, or would that be a waste of time? Anything else you can suggest? Paul

I appreciate your time Silverhead. Yea, I've spent the last 2 weekends googling, reading the Audacity manual--which doesn't support ASIO natively, I've looked all throughout the programs and the internet. My last attempt was to reach out here. I think I'm going to forget about Audacity and move to Reaper at this point. Again, I appreciate your effort.

Silverhead, I downloaded this driver from Line 6 this morning and installed. From the list, it looked like the only ASIO choice from the Pod Go driver download page. I still can't get Audacity to recognize all four channels from Pod Go. Was this the correct driver? Line 6 ASIO Driver support for Core Isolation Memory Integrity I'm on the latest version of Audacity, and I'm running Windows 10 on a very robust laptop. I followed all instructions when I ran the driver installer. Any other thoughts?

I responded to this a couple of days ago, but I may have not been signed in. I responded to thank you for the answer. I'm going to load the driver later today and I'll let you know how it goes. Thanks, Paul

I'm using a Windows 10 laptop and the latest version of Audacity software. I have a stereo backing track imported to Audacity, and I'm hoping to record my practice using the Pod Go USB inputs and outputs. I have two issues that may be linked. The first is that, although Audacity shows the PG in both the recording device dropdown menu as well as the output device dropdown menu and I've successfully recorded to a track, I don't see anywhere where I can specify which of the 4 USB channels of the PG I can route to either the input or output in Audacity depending on what I want. The Pod Go manual shows a routing diagram using those 4 channels in different ways for different purposes, but I don't see where I can make those assignments in either Audacity or Pod Go. Is this because I need to install the Line 6 ASIO driver in my laptop or, maybe, Audacity just can't do that at all? Which brings me to the second issue. My recorded track's level is too low--somewhere between -18 and -12 db. I have the recording slider maxed out in Audacity. I was looking for a way raise the output level of the PG without blowing my eardrums when monitoring via the PG. I thought there may be an adjustment in PG where I can raise the USB output without raising the volume of the speakers connected to the PG. Would this be possible if I installed the Line 6 ASIO driver into my laptop? Any help would be very appreciated! Paul