silverhead

….. moved topic to Helix forum for greater visibility…..

It’s not only normal but desirable to have your amp’s preamp section become unresponsive sometimes when you use 4CM. This is desired when you disable the FX Loop in your Stomp. That means the signal is not passed from the Stomp’s Send jack to the physical amp’s Guitar In jack (where the preamp and dials/buttons live). Instead, the preset is designed to bypass the amp’s preamp section and instead use one of the Stomp’s amp models. It then passes the signal directly from the Stomp output to the amp’s Return jack where it hits the amp’s power amp section and cab. When using 4CM you need to understand that you want to use EITHER the physical amp’s preamp section OR one of the Stomp’s amp models. You should not use both simultaneously but you should use one or the other. The on/off state of the FX Loop in your Stomp preset reflects your choice of which one to use. With the FX Loop ON you are sending the signal to the physical amp’s preamp section and hence your Stomp preset should not use a Stomp amp model. With the FX Loop OFF you are bypassing the amp’s preamp and your preset should use a Stomp amp model.

No, I certainly did not. Sometimes black and white text can be easily misinterpreted and I appreciate your recognition of that. It’s been a productive and healthy exchange of opinions. I’m glad to hear you are enjoying the Stomp XL despite its limitations.

Are you sure you have all signal levels matching? For instance, cable #2 from the Stomp Send to the amp Guitar Input should be set to Instrument level since that’s what your amp is expecting. Consult your amp manual to determine its levels at the relevant jacks at both ends of each cable and set the Stomp levels accordingly.

I’ll hang in with you a little longer….. I think what you’re proposing would require a significant hardware (memory) upgrade in order to be properly and completely implemented. The current design stores all presets in permanent memory and has a SINGLE edit/audition buffer in RAM where the currently active preset is temporarily loaded and processed by the DSP engine. That’s what happens under the hood when you change presets.That’s also why there’s a brief audio dropout when you switch presets, which is the entire motivation for having snapshots. All edits are made in this temporary RAM buffer and changes are saved back to the permanent storage on user command. When a new preset is loaded it replaces the previous preset in the RAM buffer, meaning any unsaved changes are lost. Where would the fact that SSx was active when you left the preset be saved/stored if not by a Save command from the user? You would need additional RAM space of some size. Granted It would be miniscule for this single usage application, but it makes no sense to limit your design change proposal to keeping track of the active snapshot. If that were possible for the active snapshot it should be made possible for any block or parameter change, shouldn’t it? Or do you just want this capability solely for your own use with snapshots and to heck with the guy who wants his modified delay tempo to be similarly retained while switching among unsaved presets? So the additional edit buffer space you need would be the same size as the edit buffer that is used now - two separate edit buffers, one for each of PS1 and PS2. You see where this leads, right? If you have this for two presets, what about the times when you want to swap among more than two unsaved presets and still retain all changes?. How many edit buffers do you need to satisfy all usage situations for this feature? There are 1024 presets stored in a Helix Floor/Rack/LT. Seems to me a proper and complete implementation of what you are proposing would require a separate edit buffer for every preset, essentially a doubling of RAM for preset editing. Otherwise you would be placing artificial limitations on the use of this feature (speaking of arbitrary assumptions). Makes no sense and ain’t gonna happen.

Open a support ticket and find out where to send it for repair at an authorized service center. Or open it up and risk destroying it beyond repair. Your choice. But I suspect you already know that.

The official feature request mechanism that Line 6 uses is called Ideascale. Submit your request there. Also, if by ‘old school’ you mean analog pedals then there’s no analogous situation because they have no saved states at all. You simply can’t do what Snapshots do using an ‘old school’ pedalboard. You would need to manually adjust all the pedals and parameters you want to change in real time, pushing switches and rotating knobs. Try that in the middle of a song without interrupting your playing. Introducing multiple ’saved’ states within the same preset in the modeling world means you have to decide what to do when recalling the preset. Which of the several saved states is to be active? Line 6 made a design you think is ’terrible’. What do you think it should be? You say the state should be as it was last set to. In fact, that’s what it is if you recognize that ‘set to’ means ‘saved’ in the digital realm. Like most computer programs, unsaved changes are lost when you close the file (leave the preset).

That’s certainly a limitation of the ASIO protocol, which Line 6 uses. It requires that the same device be used for both audio input and output. On Windows machines there are attempted workarounds using pseudo-ASIO protocols like ASIO4ALL which works for some but is known to cause problems in many (most?) cases. As I said I’m not a Mac guy but their Core Audio technology seems to permit something called an Aggregate Device. I don’t know if the Metallurgy apps recognize it. Hopefully a Mac person can help you out here.

Yeah, I would like to see updated drivers too. Makes me wonder whether, after some time, PC hardware upgrades mean that a driver update for older equipment requires a hardware, not just software/firmware update to the older equipment.

I suspect the apps are directing their audio output over USB to your Scarlett audio interface. To test that, try connecting headphones to your Scarlett. I'm not a Mac guy but from my readings here I think you can create an aggregate device on your Mac to be able to use one audio device as input (Scarlett) and a different audio device as output (your Mac speakers).

Try using the 4-cable method (4CM) as described in the Stomp XL manual pg9. There are lots of threads here that describe how to use it. Essentially this setup allows you to use either the amp modelling in the Stomp, or your physical amp’s preamp section. You don’t want to use both simultaneously. You use the Stomp’s FX Loop block to determine which amp (virtual or physical) you want to use for any preset.

Your Helix Floor has 8 setlists that can each hold 128 presets. That’s 1024 presets. I suggest using a dedicated setlist for this. If you don’t have an empty one create a backup of one existing setlist and overwrite those presets with Craig’s. Repeat with another setlist if you need more space.

Have you tried reinstalling the firmware? Use the Downloads link at the top of this page for access to the firmware and installation instructions. I recommend downloading the firmware first, and then use the ‘install from file’ option. This will minimize the chance of installation failure due to Bluetooth connection instability.

There’s no reason to download associated software such as HX Edit now because it won’t run without the HX device connected. But what you can do is download and read the associated device manuals. You will find them under the Support link at the top of this page. There you will also find useful info in the Knowledge Base and FAQs and Video Tutorials section. It would also be helpful to prepare to upgrade your device firmware, the first thing you should do after receiving your device. You will find those instructions by using the Downloads link, again at the top of this page.The place to start there would be to select HX Edit in the Software field. And we’re here to help with any questions or difficulties you may encounter on your learning curve. Welcome to the community, and enjoy your HX Stomp XL!

‘Position’ refers to the horizontal mic placement relative to the speaker cone/edge. It is described in Craig’s 3rd bullet point in his most recent post.

A preset is loaded with the active snapshot being the one that was active when the preset was last saved. That behaviour is fixed and not changeable. Knowing that, perhaps you can determine which snapshot you want to be active when you load a preset, and then save the preset in that state.

The drummer sets the time and everyone else plays to that. If he/she can’t keep time you don’t need a button, you need a new drummer.

Try using a dual path Helix preset. For your iPhone, set the path input to Aux and do not use any processing blocks in the path.

… moved to Helix forum …

Open a support ticket.

That’s quite a leap! From ‘simple apparently’ to ‘easy fix’ in two sentences. Your sources for the apparent simplicity and ease of fixing?

……Moved to the Helix forum….

Yes, it’s a fact of the electronics industry. Every electronic product will eventually become unsupported. Most will still do what they were originally designed to do on a standalone basis until they inevitably suffer a hardware failure, but associated devices like newer computers and operating systems will no longer be able to communicate with them. Helix, too, will eventually suffer the same fate some years after its successor is released, whenever/whatever that may be. So each one of us makes a decision: live forever with the next-to-latest minimally supported and less costly product or pay the price to have a more powerful and well supported product - for as long as that lasts. Unfortunately I don’t think there’s any magic bullet that will ease your pain with the HD500X.

The firmware update resets the device’s Global Settings to factory defaults. You can restore them to the previous settings by restoring the backup file that your created during the update procedures.

Sorry - Can’t do that on the Stomp XL.