usedbyanr

I have a new Pod Go purchased in late January. I mostly edit through the software but I noticed that when I turn the "Upper" knob counter-clockwise it sometimes doesn't react to every step in the turn. It doesn't behave that way when I turn it the other way. It's annoying when I'm switching presets or moving between effects. I didn't think anything of it at first because I thought it was a bit of lag between preset changes. It's more noticeable when moving slowly between effects in edit view. I'm worried the knob is just going to get worse over time. Is this normal on every unit or just mine? Thanks.

My post from Sept. 21st might help. I know it's in the Helix forum but I mention Pod Go Edit there as well.

My post from Sept. 21st might help. I know it's in the Helix forum but I mention Pod Go Edit there as well.

I mentioned this in my second post. First I will assume you meant SD card rather than SSD drive (you said SD card in your first post) but if it is actually an SSD you could probably do the same. You can eject the SD card which will remove it from the list. You can then start your DAW and open Helix Native to let it initialize. After it has initialized I don't believe it will attempt to read the drive serial numbers again. You can then push your SD card back in to access the audio files. I don't have enough experience with Helix Native and a DAW to know what happens if you attach the plugin to multiple tracks or add it to a new track after pushing the SD card back in.

Based on what I suggested the issue is likely to be in my first post, I would say they need to fix the bug. You can open a command prompt and type in "wmic diskdrive get serialnumber". If you see a blank line below the SerialNumber header then it's likely to crash. I can't remember if the disk order can change on reboot but that could help. You might want to try ejecting, reboot then push it back in to see where it lands.

See my two posts above on Sept. 21st and Oct. 10th. The exact same thing happened to me in Reaper and I explained why. I also explained how to see your list of drives and what drive is likely causing the problem. I hope it helps.

You may need to remove/eject the flash every time you start the software depending where the drive is initialized. Sometimes the microSD is first in my wmic list and sometimes it is not. I suppose it depends on what windows decides to do at boot.

For those of you who are still having problems... (Skip to the bottom paragraph if you like) I'm a beginner and I'm interested in Line6 products. I don't currently own any but I have started the Helix Native trial on 1.92 (mistaken download even though 1.93 was available). It worked fine. I upgraded to 1.93 and it would crash in Reaper with an "executed illegal instruction" error. I googled it and ended up in this thread. I also installed PodGo Edit a couple of weeks ago and it would crash immediately before showing the interface leaving an application error in the windows event log. I just wanted to see the interface but had no idea the PodGo had to be connected to see that. I have a ThinkPad with a Samsung EVO SSD (boot and OS drive), a 16 GB M.2 (formatted and used as backup, not bootable) and a Samsung 256 GB MicroSD. After reading this thread I took a look at my drive order and the SSD is 0, the M.2 is 1 and the MicroSD is 2 so not the same problem described in this thread. I decided to eject the MicroSD and try Helix Native again. It worked. This got me thinking that maybe PodGo Edit suffered from the same problem. I ran it and it worked as well. (That's when I found out that it just shows a device not connected screen.) I believe Line6 uses the serial number of your boot drive as the encryption key (this is common) but the software seems to choke on drives that don't have a serial number like a removable MicroSD (They do have one but Windows won't show it to you). You can tell by entering "wmic diskdrive get serialnumber" at a command prompt. You will see all of your drive serial numbers listed below the header "SerialNumber". In my case I have a blank line as the first entry because the MicroSD doesn't have a serial number. When I eject it, I don't have a blank line and see only the serial numbers from the other two drives. It seems like it's probably a NULL pointer crash. The other odd thing is that it may only fail for people that have that drive first in their wmic list even though it's not disk 0. You can probably plug the MicroSD back in after the software is running and authenticated.