Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by moehuh

  1. According to page 49 in the Stomp's manual "Synchrozining Tempo via MIDI", I should be able to synchronize the "beginning" of my modulation effects by tapping the tap tempo button once (e.g. the tremolo wave starts loudest on 1 of the song and not between beats). This works great when not using an external MIDI clock.

    But somehow the TAP once is ignored when using a MIDI clock and the modulation does not reset / is likely off because I cannot sync the MIDI clock of my controller with the band's click.


    Am I missing anything or is this currently not working with a MIDI clock? It is specifically mentioned in the MIDI section though

  2. On 11/15/2019 at 5:37 PM, rd2rk said:


    I've never experienced problems with CCs and MIDI Thru. If you have a preset that presents this problem predictably, attach a copy of the preset and I'll have a look at it.


    Will do. So far it's been random. I'll also recheck all my MIDI cabling, maybe it's just a loose connection after the Stomp?

    But like I said, it doesn't happen often (which makes trouble shooting harder...)

  3. @CraigGT

    Just found your answer in another forum (about the MIDI merge box)


    Still would love that the Stomp forwards all MIDI messages correctly... Doesn't seem like an impossible task after all.

    I guess I'd need a box with 1 MIDI in and 2 MIDI outs for my daisychain

  4. On 2/6/2018 at 6:52 PM, CraigGT said:

    So I've been messing around trying to get Strymon Nixie to work through my Helix and I've discovered that Nixie sends out a SysEx message when It's trying to detect the pedals but the Helix doesn't appear to either output the SysEx message or pass it thru.


    Has anyone else tried to get this or something similar working without using a merge box?




    I ran into the same problem with my HX Stomp. I daisy-chain all my MIDI pedals and the Stomp apparently doesn't forward the sysex correctly, so Nixie doesn't work.


    Did you find a solution?

  5. Thanks guys! Yes, that makes sense with Sysex, haven't though about that.


    Would there be any reason why a full message forwarding cannot be implemented? I'm not familiar with the machine level communication on MIDI messages.


    In general, I experience from time to time that normal CC MIDI messages are not forwarded (the Stomp is currently before my Strymon units). Haven't had that problem with the Mobius instead of the Stomp. It's rarely, but it happpens. Maybe the whole forwarding could be improved

  6. The Stomp is part of my pedalboard and I use Nixie to update all my Strymon units (Big Sky and TimeLine). All are MIDI daisy- chained, controlled from my RJM Mastermind. Before getting the Stomp, I had a Mobius and I was able to update all 3 devices, accessing from the Mastermind's USB (The Strymon units need to be set to MIDI merge).


    Since I swapped the Mobius with the HX Stomp, I cannot access the Strymon units anymore. If I take the Stomp out of the loop it works.


    Has anyone a suggestion what I could try? Seems like not all MIDI commands are forwarded from the Stomp. All "normal" MIDI commands work

    • Like 1

  7. Someone on the RJM forum suggested quickly switching the Stomp to true bypass, when a new preset is loading. I think this would be a cool and simple solution to reduce the pain of the current 200-300ms complete blackout. Especially, if not using amp sims and only effects. This would make preset transitions much less audible for sure!

    • Like 1

  8. 2 hours ago, Kilrahi said:


    I certainly agree it could be MORE powerful - and cost more too. That wouldn't even necessarily be a bad thing. I might even buy it. 


    I just have a hard time interpreting it as extremely limiting compared to what it's designed to compete up against (traditional pedals). It's great you'd rather use other fuzz pedals and I do that sometimes too (as well as sometimes other compressors, reverbs, etc.), but the Stomp is far more versatile than any fuzz pedal I know of . . . I'd call a pedal like that extremely limiting before I throw that label at the Stomp.


    I can't think of another pedal options expansive as the Stomp. Just because I can think of more it could do doesn't make it an extremely limited pedal. 


    Ah, now I get why you were asking :-) Of course the Stomp is mega versatile compared to other pedals. No question about that! Just as a side note though: a great fuzz face is probably the most versatile analog pedal possible: likely every gain stage you'll ever need just controlled by your guitar's volume ;-)


    Ok, so let me rephrase: Without being able to fully use presets while you're playing, the Stomp is very limiting to ITSELF.


    Think of the thread "Are 6 blocks enough?". I think they can be enough for one specific sound. But for a full song, 6 blocks are not a lot to work with. Sure you can work around that with using snapshots, using amp gain instead of overdrives etc., but compared to having and being able to access 126 completely unique presets, this seems really limiting. You could do: ambient swell for intro, crunch for rhythm parts, blistering solo with a Wah part in the middle and then a clean outro with a slight chorus. This would be really hard to do with one preset, but very easy with 4 different presets. Even without any other pedals!


    So I stand by my word, so much unused potential without good transition between presets.

    Always a matter of perspective, I guess ;-)

    • Like 1

  9. 2 minutes ago, Kilrahi said:


    Extremely limiting compared to what? You revealed you use a regular pedalboard, what do your other pedals do that it can't?


    I mainly use the Stomp as a dual amp setup with 2 amp models and separate IRs. That's 4 out of 6 blocks always on (or turned off when using real amps). The 2 remaining blocks would actually be sufficient if I could swap presets during a song.

    Another interesting usage would be two or three different amp models for your clean, rhythm and lead sound (think of Eric Johnson). Currently you cannot use that potential (unless you have multiple units).


    It's less about what the Stomp / Helix cannot do, it's more about sounds and pedals I love and I'm not interested in replacing (e.g. the POG has really good tracking with chords, fuzz pedals are always a bit different and if you like one just keep it, a real photocell vibe is hard to copy, Chase Bliss builds crazy analog stuff, Strymon has exceptional delay and reverb units, etc.). I think there are many guitarists out there, who feel the same way and are not willing to "give up" their favorite pedals for a big floor unit. The Stomp offers a great entry point into the digital simulation world.


    I grew tired of carrying around heavy amps and the Stomp offers a great solution for that, but it could do so much more. I wouldn't mind spending more $ on a double DSP unit with perfect spill-over!

  10. 2 hours ago, Peter said:

    No it's not possible I think. When you switch the preset, the Helix needs a little moment to clear the memory and load the new effect blocks. This cannot be fixed by an update.

    ...if you need more blocks and snapshots, you have to buy the floor/rack/LT  ;)


    I think the number of blocks and snapshots work well for the bigger units. Couple of friends have the floor and I use Native for recording.


    The Stomp has a unique role, because the bigger units are not really feasible for a normal sized pedalboard. There is simply no way I could upgrade as there is no room for a bigger unit on my board and I'm not interested in replacing my pedalboard completely.

    Plus I don't need more sounds simultaneously, I just need to be able to make use of the preset functionality.


    The Stomp could become a no-brainer-pedal for most bigger pedalboards and really threaten all the H9 and Strymon pedals. It just lacks some "pedalboard friendliness" compared to them (e.g. power connector)

  11. Had a corruped preset on my HX Stomp. Caused it to freeze when receiving a MIDI clock signal. The problematic preset wasn't even selected once, and it still froze.

    Only realized it when I couldn't do a full backup. Somehow found out that one preset was bad, replaced it and the Stomp has worked perfectly ever since...

    On software V2.81

  12. Does anyone know if they are working on this and if it's even possible to have a spill-over?

    Having to work with 6 blocks and 3 snapshots per preset is extremely limiting, while a smooth preset change would offer near endless possibilities (escpecially with a MIDI controller). Without this, I feel like the Stomp will never live up to its large potential...

  13. Found a solution with the RJM Mastermind:

    Configured a button to send CC messages to change snapshots on the Stomp whenever I change a preset on the Mastermind. The button itself is not stored, so it always sends the current state (e.g. always Snapshot 1 together with all other MIDI messages, which puts me to snapshot 1 on the new preset, even if that preset was stored on snapshot 2). Fantastic!


    Once starting to use the Stomp like this, I found out that there is a significant audio delay when changing presets. This is a real bummer and ultimately a show stopper for me  (the cut out is clearly audible even in a band setting). Seems like I will have to keep using the Stomp as "just amp sim" after all...

    Really hope the Line6 guys will find a solution for a spill-over between presets! Without this, the stomp will never use it's full potential

  14. @JeffMN

    Might have actually found the problem. Had a customtone preset called "Lonely Heart" on my Stomp, which could not be exported when I wanted to do a backup. Removed all customtone presets and only kept my own. The MIDI clock now works and TAP/Tuner turns from red pulsing to blue pulsing (before it froze at constant blue).

    Have you tried isolating the units to see if the problem still exists (only Boss MS-3 to Stomp, no other MIDI pedals)?

  15. On 8/13/2019 at 4:14 PM, JeffMN said:

    It is maddening.  For such an amazing unit, it's discouraging that this is happening.


    I feel your frustration.


    As a software engineer myself, I can tell you that there is an eternal struggle between releasing software as early as possible (you want your customers to experience all the fancy and amazing stuff you've been working on) and on the other hand to provide a software, which is as stable as possible. Proper testing takes an immense amount of time and at the end there will never be a 100% stable version (ancient programmer's wisdom: there is always one more bug).

    Best thing to do is trying to understand a company's philosophy and adapt accordingly when it comes to software updates. Line6 seems to be more pushing forward than conservative, which usually results in fancy stuff and a bit more unstable first releases. Therefore, if you want a stable version, I'd advise to wait a couple of months before upgrading your firmware.



    Maybe a Beta-release would be a good idea for the next big release. That's what we do in our company and it's a great way of getting customer feedback, engaging those who want to try the new stuff (but are aware that there might be issues) and still create the same hype for new features.

  16. On 8/13/2019 at 4:14 PM, JeffMN said:

    So, I have an HX Stomp that I love.  I have it on my board with a BOSS MS-3, and also a Morningstar MC6.  I've had some issues with the HX where it 'freezes' - the UI just stops responding altogether, and the right most stomp switch turns a solid blue color, no matter what it was prior to that.  The good thing is, the pedal still processes audio while the interface is frozen, but you cannot change anything (patches, snapshots, etc) while in this state - it requires a power cycle to 'reset' things.


    This past weekend, I was determined to figure out why this was happening, as it has been happening more frequent lately as I program my board with MIDI messaging.  I can freeze my HX without fail over and over again - literally right on booting it - by just having my BOSS MS-3 send MIDI clock data, which I configure the HX to listen for.  I've posted a video of this behavior here:  https://www.instagram.com/p/B0_WlE8nrNX


    In the video, I've just booted everything up, and attempt to send a PC message to the HX from the MC6.  I made this video prior to discovering that if I turned off MIDI clock info from the MS-3, that the HX doesn't freeze any longer.  But here, you can see it boots, but as soon as I try to change patches, the freezing happens.  Again - I can do this over and over again - when MIDI clock is enabled on the BOSS.


    I'd prefer to keep MIDI clock enabled, as my tap tempo switch is connected to the BOSS - the MS-3 has no MIDI input, so I have it at the 'top' of the MIDI chain - MS3 -> MC6 -> HX Stomp.  I've tried having the HX configured to listen on a specific MIDI channel (6) or Omni, I've tried it with and without the MC6 in the chain, it doesn't matter... it happens every time.  I've opened a support request to Line 6, but I'm still waiting to hear back from them on this one.


    EDIT : I should also add - I updated to 2.81.0 and performed a factory reset on the device.  I've loaded no backup or anything.  I also cleared all presets / IRs / settings by booting it up holding all three stomp switches.  This was all done prior to creating the video above, as you can see it's an entirely empty patch that I am able to get it to freeze with.


    Is anyone else experiencing issues like this?  It is maddening.  For such an amazing unit, it's discouraging that this is happening.




    Same issue here!

    Was running my MIDI board with MIDI clock on 2.71 with no problems (RJM Mastermind PBC-10, FW 2.4.0).

    Updated my HX Stomp to 2.81 and it freezes as described above when the Mastermind sends a MIDI clock. Checked a lot of things and can to the same conclusion: 2.81 cannot handle MIDI clock signals properly.


    Work-around until bug fix:

    - turn off Rx MIDI CLOCK

    - downgrade to 2.71

  17. 2 minutes ago, cruisinon2 said:


    Didn't realize there's only one set list on the Stomp... if that's the case, then you'd have to keep your amp/no amp  patches isolated within the one list you've got. Assuming that you haven't filled every available slot, you should have enough room to do that... just label them accordingly.


    Unfortunately, it needs to be the same preset number, as I'm controlling everything through my PBC Mastermind (PC messages saved per preset per song). Changing the PBC presets would be even more work.

    Limiting myself to 10 presets and manually changing snapshots and save the presets again seems to be the easiest solution so far.

  18. 35 minutes ago, cruisinon2 said:


    In the long run it's gonna save you a lot of time if you maintain different set lists for each scenario...I know you've said you don't want to do that, but the alternative is to be in a constant state of editing back and forth. Yes it'll take a little time initially, but you only have to do it once... with the process you're opting for instead, you'll never be finished.

    Is there a way to load a setlist without HX Edit? The Stomp unfortunately only has one setlist on board... And there WILL be the scenario, where I forgot to change the setlist at home before the rehearsal / gig ;-)

    Otherwise, this would be a good solution -> setlist 1 with amp, setlist 2 witout

  19. 37 minutes ago, DunedinDragon said:

    By the way, one trick I use for having multiple presets that share the same snapshots and settings.  When you export a preset to disk you typically save it under a given name, in my case the name of the song it applies to.  What you can do is add identifiers to the file name on disk.  When it's recalled it will still only have the original name of the preset.  So I have multiple presets of the same song saved on disk, each one geared to the guitar I'll be using on it for example.  So on disk I might have "My Song - Gretsch:" and "My Song - Tele".  Both of these will show up as "My Song" once it's imported, but will be different variations of the same preset.

    That's good to know, thx

  20. 51 minutes ago, DunedinDragon said:

    It sounds to me like you want to apply a snapshot structure across multiple presets, and if so that's not something that falls into the domain of what the Helix does as the Helix is only aware of the one preset it has in memory at a time.  To apply some function across presets would require an external operation similar to that used in the Line 6 Updater for cycling through the presets in your Helix or your Helix setlist to apply those changes.  Even then I have a hard time imagining how you would designate how a snapshot gets applied given that a snapshot is constructed around the blocks in a single preset.  If an amp block is different in another preset, the snapshot wouldn't know that's the one to be used or what to do with it.  This is why you can't just copy a snapshot to another preset or save a snapshot.  Essentially it only exists within the context of the preset it was created in.  It's not a separate entity.

    Correct, you would need an external operation going through each preset. I'm not talking about overall snapshot structures across multiple presets, just changing the selected snapshot on each preset to the same snapshot number across all presets (what you do with your snapshots per preset is of course dependent on that specific preset alone)

  21. 1 minute ago, cruisinon2 said:


    You can do that now... whatever state the patch is in when it is saved, is exactly how it'll be recalled the next time it's selected. So if you want all your patches to load with "snapshot 2" engaged, just save them all that way.

    This is exactly what I'm planning to do!

    But with something like 20-30 presets and having to move presets, whenever I switch from amps to HX Stomp only (which happens weekly), this will be very time-consuming.

    Therefore, my suggestion to have a global function which "moves" all snapshots from e.g. 1 to 2 :-)

  22. 1 hour ago, cruisinon2 said:


    I'm not entirely sure what you're asking for. You can only have one patch loaded at any given time... how would globally toggling snapshots on patches that aren't currently in use be of any benefit?

    I'm talking about the snapshot number saved on each preset (see edit above). Loading of presets would remain the same, just always the same snapshot number.

    E.g. After moving all snapshots to 2: preset 0 has snapshot 2 selected, preset 1 has snapshot 2 selected, etc.

  23. My HX Stomp is part of my pedalboard and is mainly used as amp simulator. I have a RJM Mastermind to control all pedals and I like using presets on my MIDI pedals. The board is set up so I can switch between going direct (HX Stomp always on with amp sims) or using real amps (amp sims off). This gives me excellent flexibility and it's been a lot of fun already with great feedback from my sound engineer.


    So far, I've only been using 1 preset on the Stomp, because I have to switch the amp sims on or off depending on my setup. However, I would love to use multiple presets and utilize more of the Stomp's possibilities.  I switch at least once a week between real amps or sims and the time consumed by adjusting presets is of course multiplied by the number of presets used.


    I figured the best way to arrange my presets would be to use the 3 snapshots per preset like this:

    1: amp block & IR off (use real amps)

    2: low output guitar amp sim

    3: high output guitar amp sim

    -> the other blocks remain untouched (e.g. one preset for chorus effect only and another one for autoswell with delay and reverb, etc.)


    It would be great to have some sort of global function to change snapshots on all presets. This would save a lot of time and potential mistake when changing presets.

    I can imagine that other Helix users would love this too (considering you want to use another guitar with different output and sound, but want to keep your preset structure)


    Thought about using 2 different setlists, but that's not really practical (use of computer and HX edit).

    Will check with Ron from RJM, maybe he has an idea, after all you could select a snapshot via MIDI too.


    If you have other suggestions, I'm very happy to hear them!



    Edit: When you save a preset, it saves the current snapshot you're on too and recalls that snapshot when loading the preset. My suggestion is "moving" the saved snapshot on all HX Stomp presets, e.g. from snapshot 1 to snapshot 2.

  • Create New...