silverhead

I suggest you open a support ticket to report this bug.

What exactly do you mean by ‘erases the destination preset’? What do you see in the preset after the import fails? In HX Edit are you using the Import function or drag/drop?

The latest version of HX Edit is 3.10. That's what you should be using with firmware version 3.11.

Nothing unusual here. Line 6 uses colour coding with their amp/FX blocks and footswitch LED rings. Red indicates amps, green is for delays, orange for reverbs, blue for modulation, purple for filters, .etc... Makes it easier to distinguish at a glance which type of FX is associated with any icon or footswitch. ... and there’s no such thing as a stupid question....

There is a feature request site called Ideascale where users can post, review, and vote on their collective ideas. It mostly deals with new feature requests but there's nothing stopping users from using it to report and prioritize bugs. Just not being used that way at the moment. Currently the way to report bugs is to open a support ticket. Line 6 prioritizes bugs based on their severity and also frequency as reported by the ticket system. Essentially a reported bug is a vote for it to be fixed. That's why it's important for users to report any bugs they find, even if they know it's already been reported. The number of times a bug has been reported (i.e. the number of users bothered enough by the bug to report it) is considered by Line 6 in their prioritization.

There’s no set schedule. They are continually fixing bugs and bundle them into the next feature release. Sometimes there is a release that is exclusively bug fixes. This usually happens soon after a major feature release when new high priority bugs have been identified and need to be fixed quickly. This happened most recently with release v3.11. It contains nothing but priority bug fixes from release v3.10. Now it’s back to usual practice; the next set of bug fixes will be included in the next feature update, v3.20 or whatever. And there’s no predicting when that may happen. There’s no guarantee that this particular bug will be fixed in the next release but that’s likely the earliest that it can be anticipated.

Perhaps it’s a permissions thing. Are you using a user account with administrator privileges? What about security settings? Perhaps your computer is perceiving an uncertified file in some way?

Aarrgghhhh..... I should have waited a few more minutes before beginning my troubleshooting directions...... Glad you got it sorted out.

Here’s a rather tedious but likely effective troubleshooting strategy.... 1. Perform the factory reset as you described above, which restores your device so that it works fine after reboot. Use HX Edit to individually export setlists named Factory1, Factory 2, UserX (any one of them), and Templates. This gives you individual copies of all factory setlists. Restart your device to ensure that no presets are rebuilt. 2. Rather than perform a full restoration from you backup file, be selective about what you restore and perform a restart (twice!) after each partial restoration. I suggest you proceed in this order: 2a. Using HX Edit, select Restore Backup. In the dialog box, select everything EXCEPT presets. Uncheck the Setlists box. After the restoration restart and observe whether any presets are rebuilt. There shouldn’t be any because at this point your device holds only the factory presets which weren’t rebuilt in Step 1. Your Global Settings, IRs, Favourites, and User Models have been restored but this should not trigger any preset rebuilding. 2b. Use HX Edit again to restore one setlist at a time. Note that Setlists #1, 2, and 8 should not be restored since they are the latest factory presets installed as part of Step 1. Leave their boxes unchecked. Begin with only Setlist #3; uncheck all other Setlist boxes. After restarting the device you will see the presets in Setlist #3 being rebuilt. This will begin with preset #257 (2*128 + 1). This rebuild is normal since you added new presets since the last power up. Immediately restart the device again. There should be no further rebuilding since you did not add presets during the last session. If you do observe the presets in Setlist #3 being built again that indicates that this Setlist contains one or more corrupt presets. If you take careful note you can even identify the offending preset(s) by their number. The displayed number, offset by 256, then divided by 4 (number of presets in each of Banks 1-32) leaves a remainder between 0 and 3 indicating preset D in the given bank (remainder 0) or preset A to C in the next bank. 2c. Repeat Step 2b restoring setlists #4 through 7 one at a time. Identify all setlists that contain corrupt presets. 2d. Replace all identified corrupt setlists with the factory UserX Setlist that you created in Step 1. 3. Restart your device again to ensure that there are no presets being rebuilt. This may require two startups. At this point your device should be back in good working order, but you may have some corrupt setlists and presets that you’d like to use again. 4. If you deem it worthwhile you can dive into figuring out which presets are corrupt by doing the numeric analysis I described in Step 2b. Do this for every Setlist you had to replace in Step 2d. Retain the good presets and discard the corrupt ones until you get a clean startup again. I understand that this is extremely tedious and may not be worth your time. You can always open a support ticket and get Line 6 to help.

I find it's always helpful to read the manual before purchasing a product like this. Helps you understand the details and prevents unpleasant post-purchase surprises. https://line6.com/data/6/0a020a401270c5f5262b29e68c/application/pdf/POD Go 1.10 Owner's Manual - English .pdf

Yes, assuming the sort of amp model parameters you're talking about are Drive, Tone controls, mic/cab selections, etc. Or are you meaning something more obscure?

There’s more to it. The two devices use different DSP management strategies as illustrated by the POD Go’s fixed vs. Flex blocks. Regardless of why, the presets are simply not compatible.

That’s not normal unless you have imported one or more presets from older firmware since the previous startup. If it’s happening at every startup, even with no preset imports during the last session, that indicates the presence of one or more corrupt presets. To narrow things down take note of the number of the first preset being rebuilt. Divide that number by 128 to determine the number of the associated setlist. Export that setlist, replace it by importing a User setlist full of New Presets, and restart your Helix. It may start rebuilding presets again due to the setlist you just imported. If so shut down and start up again immediately. If you no longer observe any rebuilding it means you have identified the suspect setlist. If you want to pursue it further to identify the corrupt preset(s) we can discuss further at that time.

If you began the update by downloading and installing the HX Edit v3.10 package you will have installed a program called Line 6 Updater. Run that program while your device is displaying the error message. If you did not begin with HX Edit v3.10 do so now.

From the Bypass/Control screen select the FX Loop block and press ACTION. Use knob 1 to clear the footswitch bypass assignment. (see manual for more detail. Too bad you hadn’t seen this earlier, since it’s been a serious issue for you. Maybe there’s other useful stuff in there?)

Check the Global Settings. There are several different options that allow you to control the display and operation of the footswitches. These settings are reset to their default values during a firmware update. The update process created a backup of your device's pre-update state. Run HX Edit. Under the File menu, select Restore Backup. Choose to restore the Global Settings. This should give you the display you had previously. P.S. This is handled well if you follow the firmware update instructions, which include a factory reset followed by a restoration of your backup file.

I believe one of the artist presets in Factory 1 (the artist presets are the ones whose names are in full CAPS) is based on the US Princess but I forget which one it is. If you scroll thru them you’ll find it. However, I personally don’t think the tone is designed to reflect the US princess tone. More of a heavy driven, FX tone.

No need to apologize for adhering to your NDA, imho. There are things you know that you can’t share publicly. Not difficult to understand.

My money was on the Speedo, but fig leaf is also good.....

The Factory 1 setlist has the amp model presets. If you can’t find it there it probably doesn’t exist. Make sure you are using the latest factory presets, which requires a factory reset after the firmware update. But it’s simple to make your own. Start with a New Preset and add the US Princess amp model. Twiddle with the amp parameters until you find the settings you like for your environment, which is what you’d do with the factory preset anyway. Then add you favourite FX. Or..... Start with Factory 1 preset 1A and replace the US Dbl Nrm amp with the US Princess. Tweak to taste and SAVE in a New Preset slot.

I haven't tested this but a quick manual solution might be just to rotate the Variax tuning knob from Standard back to Standard as desired. Means you don't have to edit every preset, but you do have to be aware of when the manual solution is necessary (preferably before you start the next song during your gig!). So maybe just not very practical.

As of yesterday you don't need to wear pants in public if you've been fully vassectinated.

The backup is forced so that you have access to the pre-update state of the device in case something goes wrong with the update. In some cases recovery of the device can only be achieved by wiping out all data on the device with a full factory reset. That’s when the backup is handy. You’re right that under normal circumstances a firmware update leaves most data intact on the device and the backup is really only useful for restoring global settings and for restoring data if you choose to follow the recommendation to perform a factory reset after updating.

Yes, that’s an available option. I’m not concerned that Line 6 has stopped supporting the StageScape. Every product reaches its end-of-life and updates stop. My concern is that they are still selling it new and advertising that it can be used with an iPad. They don’t say that the iPad can’t run the current iOS. Unsuspecting new buyers, if any, will be justifiably irate. I just don’t understand why it’s still being sold at full price with no plans to update. Seems to me an inventory clearance EOL sale at a significant discount, with an acknowledgement of iOS 14 incompatibility, would be a good idea.

Just want to provide an update on the support ticket I raised. The first response pointed me to Ideascale to provide customer feedback. To that I replied: "I know about Ideascale. I am not requesting a new feature or providing feedback. I am reporting a technical problem as well as a customer support issue and requesting a solution. The product you are selling does not perform as advertised. The lack of support for iOS 14 is a technical deficiency that should be corrected; it’s not a feature idea or negative feedback. It’s a deficiency, as indicated by your marketing materials." Here's the disappointing response: "I'm afraid that you may have elevated expectations about how product software development works in cases of products that are nearing the end of their lifecycle. We don't have any updates for you at this time." So it seems StageScape users should not expect an update to support iOS 14. Anyone who buys this new right now will be justifiably upset.