saxatron

Never had issues with the headphone out (the one on the back of the device, not USB right?). The physical knob on the Pod Go (the one upper left of the pedal) controls that output, you have that turned all the way to the right and it is still quiet? If so seems like a hardware issue.

Good info @ElPuni, hopefully helps some people. Unfortunately even that didn't work for me. @voxman55 to answer your question, I completely reformatted the entire computer multiple times hoping it was a software or registry corruption issue, no luck. Drivers are how software talks to the hardware, so completely possible different versions of hardware could be the issue. But it's standard, they just need to keep it updated to support the latest (e.g., USB3.1 which is fairly new). I unfortunately returned the computer that had the issues because I literally bought it to do music recording and it didn't work so I can't test on the latest one that just got released. Works on all my other computers though. To be fair, the new M1 Macs are having similar driver issues, so I think Line 6 is just a little behind.

They are the same drivers. I tried installing them both ways (directly from the device and as the separate driver install), neither works. You are welcome to try this yourself. Plugin your Pod Go, go to drivers (Device Manager) and uninstall driver. Then you can either plug in the device again or install the driver that comes with the Pod Go Edit software, and the driver will be the same (you can check the versions and the logs, they are identical using either installation method). If it already works on your computer, it is going to install properly, it seems to be a hardware related issue with the drivers they currently support (I know this because I installed it on 2 identical Surface Books, one older hardware, the older hardware worked, new hardware did not work, exactly the same software on both computers). When you have the hardware incompatibility, you get the following error which is due to a hardware combability with the driver. ! dvi: Device 'USB\VID_0E41&PID_4247&MI_01\8&17BA1CFE&1&0001' not started: Device has problem: 0x27 (CM_PROB_DRIVER_FAILED_LOAD), problem status: 0xc000007b.

Not sure you have read the entire post? This is specifically about audio drivers (I have posted detailed screen shots and logs on the audio driver installs). This is not about connectivity between the Pod Go and the Pod Go Edit software. IIRC that worked. What doesn't work is 1. Recording (because the computer doesn't recognize it as an audio device) 2. Playing audio from your computer through USB into your Pod Go Monitor

The above is a screen shot from the Pod Go Edit installer. Pod Go also automatically installs drivers when you plug in the USB, but it is the same drivers as the ones you install using the installer (I guess they are bundled).

Hey @voxman55, This has nothing to do with Pod Go Edit or the Firmware on the device itself. When you use the installer, you install the drivers along with it. This is what is failing (though I have returned the computer it didn't work on and haven't tried the v1.96 drivers to see if that fixed it). This driver is the audio driver which allows the Pod Go to communicate to DAWs, etc... So basically recording doesn't work.

I tried many many things, support is not helpful at all unfortunately. In my case I think it was because my computer was newer and had USB 3.1 ports (worked on my wife's 3.0) and the driver didn't support it yet. Might have to just wait for updates to the drivers. I didn't try it, but you might want to try a USB hub with older USB support.

Yes, still the solution I use. I honestly don't notice it any more. I usually record via garageband and when I export as wav the audio seems to be full volume (but doesn't show that way in garageband).

Ok. I gave up and am returning my laptop, I literally tried everything I could think of. I had bought the laptop basically to exclusively do music with my Pod Go, so makes me sad. The only real difference between my wife's Surface Book and mine was I was on Windows Pro (which it looks like you are) and I had usb 3.1 instead of usb 3.0. I had read somewhere that the Hypervisor security may be the cause of similar errors, so maybe look into that. Sorry I can't be of more help but I think my journey with this issue ends here.

Sadly, I'm out of ideas. It appears to be a driver issue on more recent hardware. I full factory reset my computer this time to clean the registry, so that isn't the problem. 2 questions @weitzhandler, are you running Windows Pro? And how new is your desktop? Thanks.

Sadly, still no luck. This is the latest attempt, I seemed to have missed a few on my last cleanup so i am going to try once more. I also didn't touch the registry for this attempt. flq: {FILE_QUEUE_COMMIT} 12:45:53.474 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo_AvsFilter.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo_AvsFilter.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer_x64.dll' to 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer.dll' to 'C:\WINDOWS\SysWOW64\L6PodGoAsio_OnInterposer.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend64.dll' to 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\System32\L6ConfigPodGo.xml'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend.dll' to 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml'. cpy: Existing file 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6Driver2PodGoControlPanel.cpl' to 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01009.dll'. idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\drmk.sys' to 'C:\WINDOWS\System32\drivers\drmk.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\drmk.sys' remains unchanged. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\portcls.sys' to 'C:\WINDOWS\System32\drivers\portcls.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\portcls.sys' remains unchanged. flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 12:45:53.538 This line is concerning idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. As this did not show up on my wife's computer. Also this error code: ! dvi: Device 'USB\VID_0E41&PID_4247&MI_01\8&17BA1CFE&1&0001' not started: Device has problem: 0x27 (CM_PROB_DRIVER_FAILED_LOAD), problem status: 0xc000007b. Means that it is trying to use a driver compiled on x86 instead of x64, so that is where my focus is right now. Would be great if you could check you `C:\Windows\INF\setupapi.dev.log` and see if you see something similar. Thanks.

Sorry for spamming the thread, but want to make sure I keep it up to date with my progress on this. The uninstaller doesn't work properly, its leaving residual files, here is the file list flq: {FILE_QUEUE_COMMIT} 00:14:18.011 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo_AvsFilter.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo_AvsFilter.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer_x64.dll' to 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll'. cpy: Existing file 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer.dll' to 'C:\WINDOWS\SysWOW64\L6PodGoAsio_OnInterposer.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend64.dll' to 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll'. cpy: Existing file 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\System32\L6ConfigPodGo.xml'. cpy: Existing file 'C:\WINDOWS\System32\L6ConfigPodGo.xml' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend.dll' to 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll'. cpy: Existing file 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6Driver2PodGoControlPanel.cpl' to 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl'. cpy: Existing file 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01009.dll'. idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\drmk.sys' to 'C:\WINDOWS\System32\drivers\drmk.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\drmk.sys' remains unchanged. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\portcls.sys' to 'C:\WINDOWS\System32\drivers\portcls.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\portcls.sys' remains unchanged. flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 00:14:18.256 This is after a clean install, so there shouldn't be any "existing file" flags here. I was able to go through and clean these up by hand. I haven't tried to see if this fixes it yet, I have a feeling no because here is the other issue. dvi: {Configure Device - USB\VID_0E41&PID_4247&MI_01\8&17ba1cfe&1&0001} 00:14:17.768 dvi: Device Status: 0x01802400 [0x12 - 0xc0000493] dvi: Config Flags: 0x00000020 dvi: Parent Device: USB\VID_0E41&PID_4247\___3198677 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6podgo.inf} sto: Source Filter = USB\VID_0E41&PID_4247&MI_01 inf: Class GUID = {4d36e96c-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable inf: {Configure Driver: Line 6 POD Go} inf: Section Name = l6PodGo.NTamd64 inf: {Add Service: l6PodGo} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\Drivers\l6PodGo.sys inf: Display Name = Service Line 6 POD Go inf: Group = Base inf: Updated service 'l6PodGo'. inf: {Add Service: exit(0x00000000)} inf: {Add Service: l6podgo_AvsFilter} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\drivers\l6PodGo_AvsFilter.sys inf: Display Name = Line 6 POD Go AVStream Mini Driver inf: Group = PNP Filter inf: Updated service 'l6podgo_AvsFilter'. inf: {Add Service: exit(0x00000000)} inf: Hardware Id = USB\VID_0e41&PID_4247&MI_01 inf: {Configure Driver Configuration: l6PodGo.NTamd64} inf: Service Name = l6PodGo inf: Upper Filters = l6podgo_AvsFilter inf: Included INFs = ks.inf inf: wdmaudio.inf inf: Include Scope = Services inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} You can see it says "Updated service" 'l6PodGo' and 'l6podgo_AvsFilter' (the bane). I am still trying to find the reference to this because even after remove the .sys files it still sys updated service. I found them left over in the registry, so I am guessing it has something to do with that, a task for tomorrow: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo_AvsFilter.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo_AvsFilter.sys These logs are in the C:\Windows\INF\setupapi.dev.log file if you are looking.

I made a little bit of progress, still getting errors but they are different now, so maybe will help you @weitzhandler. Turns out the driver installer installs both L6 USB and the Pod Go drivers, but the uninstaller only uninstalls the Pod Go drivers. The L6 USB drivers, no matter how many times i installed, were always on the march version instead of june. Windows + I -> Add or remove programs -> Uninstall from here both the Line 6 Pod Go and the Line 6 WinUsb driver. Now I am getting migration issues instead of the previous error, which I am researching now.

I just upgrade to 20H2, did not help :(. Here is what a good install looks like, (way different)

I just installed it on my wife's Surface Book and it works flawless. If you `winver` what version do you get? My wife and I are currently on different Win 10s vers (I am on 1909 and she is on 2004), so looking to see if that helps.

They are at least sort of similar. Support got back with a cop-out answer that they don't support tablet PCs (I don't see that stated anywhere). Also my Scarlett works flawless, so I don't really think it's a good answer. Maybe you can try to submit a ticket? Maybe you will get further since you are on Desktop. I'm going to try to submit a ticket to Microsoft, my last resort.

@weitzhandler, what kind of computer are you running on? Does it happen to be a Surface Book?

I've been trying to debug this myself since this is the only thread I can find with this issue. It seems to be either a newer Windows update driver issue or a corrupted registry value, but I am not sure how to fix it. I found details on the error. I have a ticket submitted, hopefully can get more info, I'll share back if I hear anything.

This is happening to me on my new computer. Works fine on all my other computers. Windows10 64bit. I even factory reset my computer, issue still persists.

Yeah, seems to be the norm, my solution was to decrease the USB in to -14dB in the global settings.

Probably looking for this? https://line6.com/customtone/browse/pod_go/6

Thanks for the input, I'm definitely starting to think it may be an issue with me and not the Go. It is recorded Channel 1/2, not 3/4. I was told on my guitar to set my low/mid/high knobs to the middle and let the amp handle the rest, but messing around with those yesterday I was getting a better signal even not at max volume (not too track level, but I think I agree with you, it shouldnt look like that).

Not sure what that means, sorry, I am very new to this. I googled ASIO and looks to be Windows related. This happens on iPad, Mac, and Windows. Are you referring to a setting on the Pod Go by chance?

Are you on the v1.1 firmware? I may try to factory reset if possible (instead of factory reseting just the global settings) and see if the v1.0 firmware has the same issue. I upgrade immediately out of the box, so never tested on the old one.

Thank you for the chat. I have opened a ticket. Out of curiosity, do have one? Just curious if it is for all units or just mine.