justinmlsaw

Anyway did a workaround which was to import the IR to another slot and configure the patches to point to the new IR slot #. Unnecessarily concerned with the initial issue to have thought about this earlier :(

Hi grdGo33, from other patches I've tried, I believe it only validates the slot # unless version 1.30 actually requires to validate both. I learned this from buying other patches where you can always load the patch first if you don't know which slot to place the IR, then the cabinet settings will show you the exact slot #. But weird thing is that this issue doesn't happen in other patches I purchased, only this new one that I recently purchased. And yes I did manually save each one just to be sure, but the error message still pops up. Hi chugzilla, I loaded the first patch before the IR as the creator did not specify which slot the IR is supposed to be in, but the other 10 patches were imported after I saved the IR in the correct slot. And from checking all other patches, they seem to be using the same slot #. Hi voxman55, yes I have the IR saved in the folder already. Ok will try this out, thanks!

Hi silverhead, thanks for your reply. Yes I tried restarting my Pod Go and also my laptop, but the message kept appearing whenever I switch to the affected patches. And oddly enough, a few of them do not have this issue even though this group of patches use the same IR.

Hi guys, want to know if anyone else ran into a similar issue. I recently purchased a patch that comes with a custom IR, and initially didn't know which slot the IR should be installed in until after I loaded one of the patches (it wasn't stated in the manual). After that, I tried loading the other patches which uses the same IR from the same slot, but almost every patch kept displaying this error although there is sound coming out from these patches. Only about 2-3 patches worked fine. My firmware is up to date (version 1.30 on both) and tried replacing the patches but it still shows this error message. Am I missing anything?

Hi Voxman, thanks for the info! Just installed POD Go Edit 1.22 and realized that my POD Go suddenly showed v1.22 from the pedal and also POD Go Edit software. Very odd. Anyway at least both are already updated. Thanks Voxman and Phil!

Hey Phil, thanks for the reply! Honestly I didn't think much about the POD Go Edit. I thought the POD Go edit would have also been updated automatically. My POD Go still shows 1.21.

Hi guys, I have an issue where I have updated my Pod Go several times and although it says successful every time, it still prompts me about the new 1.22 version whenever I reconnect my POD Go to my laptop and asks if I would want to upgrade. And I noticed recently that when I go to Help -> About POD Go Edit, it shows that the POD Go firmware is 0.00 (Build 00000), whereas the POD Go Edit firmware is 1.11. Did this happen to anyone here as well and any resolution for this? Thanks!