silverhead

Depending on the other blocks in your preset you may be encountering the DSP limitation. To test, copy the preset to a different location and delete one or more of the other FX blocks in the same path. Can you now add your second 1024 IR?

When you run it through the Scarlett and to your monitors .... I presume the monitors are powered? That’s the key; the monitors have an internal amp that needs power. You could also bypass the Scarlett and connect your monitors directly to the Helix outputs.

You should also be able to import presets (multiple simultaneously if you wish) by drag/dropping them into the Helix Native preset slots.

Maybe irrelevant but.... your first screenshot indicates that Helix Native is expecting to import a setlist. The listed files are preset files, not setlist files. Perhaps make sure you are attempting to import presets, not setlists?

Just a guess... perhaps Marketplace stuff is not supported in the trial version? Edit: I think my guess is wrong. I found this in the Helix Native FAQs. Keyword is "fully". Q: Is there a demo version to try out? Yes. You can try before they buy! A free trial is available at http://line6.com/software/ and is fully functional for 15 days.

Have you authorized your computer in Helix Native?

I know it’s a rhetorical question but .... I think you, like me, fell in love with the rich sound and dynamic response of the new Helix modeling technology. That existed in V1.10. The rest has been lots of additional models and very cool bells and whistles.

I think you’re both right. I believe voxmann55 is talking about full dynamic DSP management, rather than partial. The POD Go allocates a certain amount of DSP to the fixed blocks and uses dynamic DSP for the remainder. This is unlike Helix which uses fully dynamic DSP management - you start with a completely empty preset and are in full control of the DSP allocation. So I think you are talking about full vs partial dynamic DSP management.

https://helixhelp.com/release-notes

Maybe try placing a VOL block at the beginning of the chain? By default it is assigned to an EXP pedal as the controller.

Actually it is a bit more restrictive than I said earlier because HX Stomp has a limit of 8 blocks (used to be 6). Sorry for the misinformation. I presume the following statement from the HX Stomp FAQ sheet should be revised upwards as of firmware v3.0: Can HX Stomp load Helix Floor, Helix Rack/Control, Helix LT, or HX Effects presets? As long as the preset has six or fewer blocks, you can use the latest version of HX Edit (2.70, out very soon) to access both devices at once and copy and paste blocks back and forth. Rebuilding a Helix preset in HX Stomp shouldn’t take more than 30 seconds.

Just to clarify, you can import a single path Helix Floor preset into HX Stomp. You’re correct that you can’t use a dual path preset.

Yes, I know. I don't think what you're looking for exists. Hope someone proves me wrong!

I found what I remember seeing before. It is not exactly what I thought but is useful for anyone who wants to inspect a Helix file without their Helix device connected (rendering HX Edit inoperable). Many thanks to user dbagchee. https://dbagchee.github.io/helix-preset-viewer/

No, but sometimes users go to the effort of manually creating such a listing (or a program to generate such a listing from the raw .hlx file which is in JSON format I believe) and sharing it here in some common format such as Excel. I believe an .hlx file reader and interpreter program has been created and posted by a user but I can't find it at the moment and I don't know if it works for HX Stomp.

Other users organize their presets to work around the bug until it’s fixed.

You say there’s no LED on the tuning knob. There should be. Normally there’s a blue light on the tuning knob that indicates whether you are in switch position 1 and 5 (light is off) or 2 and 4 (light is on). The position/light toggles on/off with each press of the tuning knob.

It takes about two minutes using HX Edit to reorganize your presets to avoid this bug. When Line 6 fixes the bug you can go back to your familiar structure. Meantime it’s up to you whether or not you want to continue to be ‘bugged’ by this. Seriously, what difference does the bank number make? Your familiarity is with changing banks using your foot. You know when you are in a general purpose vs. song oriented bank, and you’re very familiar with the Up/Down switch pressing required to navigate back and forth. None of that changes whether the banks you use are numbered 31 to 4, or 14 to 20, or any other of several consecutive banks. What’s important is maintaining consistency with your foot switch sequencing, not the bank numbers.

Of course, you could simply organize your presets differently so that you avoid this 'mission critical' bug. Why not use Banks 1, 2, and 3 instead? Or any 3 banks that do not roll over from 32 to 1. You are choosing to suffer from this bug. Why?

http://line6.ideascale.com/ It’s the official Line 6 method for providing product feedback, suggestions, and ideas. User input here informs Line 6 product decisions.

1. I'm not sure what you mean by 'the actual real ones'. Each amp has a default setting which is the set of amp parameter values that you will see when you add the amp to a preset by selecting it from the list of available amps, rather than by copying it from some other source. I presume these default settings are what you mean. There is no document from Line 6 (or maybe anywhere) that details these default settings. If you want to answer this question in detail you will likely have to do it yourself by brute force, examining each amp's default individually. Having done so it would be a useful service to the community to publish your findings here. That way, the next time someone on the forum asks the same question we will be able to point them to your document! Note that as of firmware 3.0 you can customize the detailed settings of any amp (or other block) and save it as your own personal default, in a User Model, or Favorite.

I don’t find it very useful for exactly this reason. I usually abandon it before I figure out a useful keyword or phrase.

Just a further comment - making a Helix backup is not like creating a system restore point in Windows. Rather, it is like using File History in Windows. It backs up files and settings but does not make changes to the OS.

Restoring the .hxb file does not restore the firmware to an earlier version. It is a system backup that you can use to restore the Global Settings, IRS, and Setlists from their state in the earlier firmware to the new firmware. Your firmware remains at the new version, in this case v3.01. The Restore operation allows you to choose subsets of the entire backup that you want to restore. So, for instance, you can choose to restore only the specific setlists that contain the presets you want.