Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/18/2026 in all areas

  1. I’VE FOUND A FIX FOR THIS PROBLEM!!! I noticed that the only Setlists that were locked to Current Preset / Current Snapshot, were Setlists that had NOT had a preset added AFTER updating to v1.4. So I tried adding a random Preset to a Setlist that was locked within a Song, and when I go back in to the Song and try to add a Flag, not only can I add a Flag from the Setlist that was previously locked to Current Preset/Snapshot, but even better, ALL the correct Flags from before the v1.4 update were back in place in the Song again, and work as they should. If you don't want the Preset you just added in that particular setlist, you can clear it from the Setlist, and you'll still have access to that Setlist within the Song when you try to add a Preset and/or Snapshot Flag. I have shot a video, which is 276mb, but that is sadly far too big to upload here, so I don't know how to share that with you guys - hopefully my explanation will be enough.
    4 points
  2. Well, first off: Parametric captures are already happening. And they will likely take off quite a bit in pretty much no time. Those would likely not run on the OG HX units, but there's already some tools allowing you to extract a static NAM capture from a parametric one, so you could just do the "homework" in a DAW and export the setting(s) you like the most. Besides, you can tweak NAM captures a LOT. After all, many amp gain circuits and tonestacks are pretty simple things, not all that much different from what you get in various NAM player options. So once you find a suitable "middle of the road" capture, representing kind of the "essence" of whatever amp channel, some tweaking can take you a long way already. I recorded the following example during a similar discussion on a forum, all of this is one single capture through one single IR with just some pre/post EQ and different gain settings applied (in the Tone 3000 plugin), plus a little reverb and delay here and there. Six variations: 1) Original (just the capture and an IR loaded). 2) A kinda more oldfashoned "narrow mid" version. 3) Almost completely clean for some funky stuff and what not. 4) Even cleaner, some jazzy thing. 5) A kinda riffy rendition. 6) The noodling lead thing. https://drive.google.com/file/d/1P7_LM3aR4m8XAR-aGaEvyU6BI3MBYbTv/view?usp=sharing I think this is at least as efficient as any amp controls. Sure, you need to know your EQs a bit. And no, it doesn't sound like the authentic amp tone stack. But I couldn't care less.
    3 points
  3. The icon just means that there's been a change to the preset. It won't go away until you change presets or SAVE the changes, even though the change was just a toggle and the state is the same as the original preset.
    3 points
  4. The Apple silicon chips have been out since 2020, after 6 years, L6 should really be releasing software to support this natively. even the latest helix stadium software is still not released with native builds. I haven't installed rosetta and don't plan to on my M3 macbook air, i have an old intel macbook from 2008 that still works and runs the software. I really don't understand why companies like L6 don't have modern software chains, this is basic stuff that should be addressed quickly - It's not exactly a surprise that they're doing this (did i mention the Apple silicon chips have been out for 6 years?).
    3 points
  5. I've used the hacked software on my Stomp for more than a week now and had no issues with it so far. It's great. If I had the LT I'd try it. The hacked firmware does not change the boot loader so you can always go back to the stock firmware. Even if the hacked firmware was totally corrupted and didn't boot up you can hold footswitches 6 + 12 while powering on (update mode) and upload the stock firmware. So I guess the only drawback is that uploading an unofficial firmware to the device can be interpreted by Line 6 as a breach of warranty. So if your device doesn't start anymore during the warranty period and has the hacked firmware on it - that might be an issue. I guess for Line 6 the main concern with this firmware hack is that could potentially add work for their customer service. Also I think the Line 6 guys are basically hackers, so they probably have a soft spot for stuff like this. I mean what else are modded amps and pedals if not hacks - changes in the device to make it do what you want? Just my two cents.
    2 points
  6. Of course they have to say just that. My inofficial advice is to check it out in any case as the improvements are incredible. Gapless amp "channel" switching within one single block. Between up to 128 captured amps. That's just gorgeous. And quite obviously, some NAM captures sound fantastic (even if it's just the lite versions, there's very little differences between lite and full).
    2 points
  7. Operation complete, it's back! A bit of work to get the new smaller one to fit in the same spot, but it all came together.. (whew!) Note, there was live dangerous AC power while testing with the case open. I have literally decades of experience working on electronics, so I know how to be safe. This is not a task for someone who doesn't know their way around live AC power. And if I charged myself a reasonable hourly rate, it probably would not have made sense to repair it. Be warned!
    2 points
  8. Use Snapshots wisely. Use MIDI. Assign switches on a basic MIDI controller to the simple ON/OFF functions and use the Helix switches for the more complex stuff. Don't make every preset a "kitchen sink".
    2 points
  9. Helix Stadium Native has a built-in A/B feature for such comparisons. There’s a free trial period. Hardware and plug-in presets are interchangeable.
    2 points
  10. One more update: for anyone who wants to edit from a tablet or phone without a cable to the pedal, there's now the Helrig Box, a small DIY Wi-Fi bridge that sits next to the pedal. You flash a Waveshare ESP32-P4-NANO board from the browser, plug the pedal into it, and the Helrig apps on Android, Mac, Windows and Linux connect over Wi-Fi. It works with every Helix and HX the apps support. Build guide: https://box.helrig.com Video: (Helrig is an independent project, not affiliated with or endorsed by Line 6 or Yamaha.)
    2 points
  11. This is very exciting! I've been wanting an editor for Linux almost since I got the Helix in 2015. I'll have to try this out - HX Edit has been almost the ONLY reason I've kept Windows devices and VMs around lately.
    2 points
  12. I've sent a bug report so hopefully this is now on radar for the developers...
    2 points
  13. I was having the exact same problem described in this thread with my Line 6 Spider V30 MkII. After a Windows 11 update, Spider V Remote stopped detecting the amplifier and showed: "No Device Connection" The USB connection itself was working correctly: the Spider V was still recognized as an audio interface and worked normally with the ASIO drivers. I also tried: Different USB cables Different USB ports Reinstalling the Line 6 drivers Reinstalling Spider V Remote Older versions of Spider V Remote Running as administrator Compatibility mode Factory resetting the amplifier Nothing worked. My system is: Windows 11 25H2 OS Build 26200.9168 Feature Experience Pack 1000.26100.344.0 Line 6 Spider V30 MkII The solution The problem appears to be related to the new Windows MIDI Services stack introduced in recent versions of Windows 11. Microsoft provides a compatibility option called Legacy MIDI API Mode, which allows older MIDI applications/devices to use the previous Windows MIDI stack. I enabled it by adding the following registry value: Open Registry Editor (regedit.exe) Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 Create a new DWORD (32-bit) Value named: UseLegacyMidi Set its value to: 1 Restart Windows. After rebooting, I opened Spider V Remote, connected my Spider V30 MkII, and it immediately detected the amplifier and worked normally again. So if your Spider V Remote suddenly stopped detecting your amplifier after a Windows 11 update, especially on Windows 11 25H2, I strongly recommend trying this before replacing cables, reinstalling drivers, or resetting the amplifier. Important This does not appear to be a problem with the USB audio functionality itself. In my case, ASIO/audio continued working normally while Spider V Remote could not communicate with the amplifier. I have not seen an official Line 6 statement confirming this specific compatibility issue, but the timing and symptoms strongly point to the changes in Windows MIDI Services. If this fixes the problem for you as well, please report your Windows version/build and Spider model in this thread. Hopefully we can establish whether this affects Spider V users broadly and give Line 6/Microsoft enough information to address it. Edit: To undo the workaround, you can change UseLegacyMidi back to 0 or remove the registry value and restart Windows.
    2 points
  14. FEATURE REQUEST: NAM A2 Support for Helix LT Dear Line 6 Team, Please consider adding Neural Amp Modeler (NAM / NAM A2) support to the Helix family, especially the Helix LT. The Helix already has powerful DSP, IR loading and a highly flexible signal chain. Adding a dedicated NAM block would give Helix users access to the rapidly growing NAM ecosystem of high-quality amp captures. Even supporting only NAM A2-Lite or Helix-optimized models would be extremely valuable. This could be a major firmware update that would extend the life and capabilities of existing Helix hardware without requiring users to buy additional equipment. Please consider making NAM support a future Helix firmware feature. I would definitely use this feature on my Helix LT. Thank you, Line 6! Best regards, A Helix LT user
    1 point
  15. My post was just a “heads up” about the official Line 6 take on the current/ongoing NAM issues. Steve Sterlacci recently did a podcast with Steve Atkinson - the creator of NAM captures, and he (S.A.) says that he uses A2 Lite versions because, as you have already found, most people would not notice any difference in sound and they are more efficient on CPU power. Personally, I have no objection to NAM as such, and I have even used the converted/resampled Snaptone versions of A2 captures in my cheapo, cheapo Valeton GP200. I find that the downside to this stuff is having to trawl through thousands of captures to find really good ones, in a similar way to how we all went down the “rabbit hole” of speaker IRs. We are a constant state of flux with this stuff.
    1 point
  16. Yeah - but also possibly that there's now quite some more pressure for them to improve the Stadium units. So far, there's pretty much just UI changes, Agoura amps and Showcase setting them apart from the OG units. If you don't care about Showcase and are fine with the old UI, I can see pretty little incentives to buy a new unit. I would agree on that. I'm sure that pretty much any programmer is at least "fascinated" at what's happening right now (for good or bad).
    1 point
  17. Hi, Well, even if it does appear that just about every other modelling unit can load and use NAM A2, right from the tiny Pocket Master on upwards, the official advice is not to do it. This is from Frank R, over on BookFace. https://m.facebook.com/groups/line6helixusergroup/permalink/3462267550623560/?
    1 point
  18. If you're not afraid to load custom firmware, on LT and stomp you can already have nam a2 lite https://github.com/andreidevs/helix-lt-nam
    1 point
  19. I had no connectivity issues at all until 1.40 which broke it all. 1.4.2 fixed everything for me. First check your time zone you are set to on your Stadium. Mine had reverted to the US with the 1.4 update which stops you logging in (this was a known problem with earlier releases too preventing login). If you can get there far (and maybe with a bit of the above I posted) hopefully you can get unto 1.4.2 and all will go away. It did for me (although I know some still have issues)
    1 point
  20. Good news, I powered up the Helix with a bench supply, it's alive! (No point in replacing the built-in supply if the Helix was dead). I didn't hear back from Line 6 support so I ordered this supply, all in for $50 Canadian: VOF-65C-S12 POWER SUPPLY, ITE, 12V, 5.42A https://www.newark.com/.../power-supply-ite.../dp/13AJ1512 It's slightly smaller so I'll have to build a mechanical adapter. The original Helix supply is no longer available. Now I wait for the new one to arrive..
    1 point
  21. I solved the problem in a different fashion. I created a VLAN for the Line 6 traffic. I enabled the 2.4gHz radio only. I enabled client isolation. I gave it a /29 IP. With this I get automatic connections to the editor as soon as the Hellx boots. The connection is rock solid for hours with no glitches.
    1 point
  22. Same way you toggle any pair of effects. Assign them both to the same FS, then SAVE the preset with one ON and the other OFF.
    1 point
  23. A small update for anyone using the Helrig Box. With the latest firmware, the Box also shows up as a Bluetooth MIDI device. A setlist app like OnSong can send program changes through it to the pedal, so the pedal switches to the song’s preset without a MIDI cable. Helrig still edits the same pedal over Wi-Fi through the Box, and both work at the same time. On my HX Stomp board it replaced my WIDI Jack, and on the iPad I run OnSong and Helrig side by side. A few things to know: Bluetooth MIDI switches presets, it doesn’t edit them. Editing goes over Wi-Fi or USB in Helrig. It goes one way, from the app to the pedal. If your pedal has MIDI Thru, it passes the messages on. To update an existing Box, flash it again at box.helrig.com/flash. Your saved Wi-Fi networks stay. Other setlist apps that send Bluetooth MIDI program changes should work the same way. Try a preset change before a gig. Bluetooth MIDI needs no license. Editing through the Box needs Helrig Connect or Pro, same as over USB. Video of my gig board: https://youtu.be/H00CTybne_M Setup steps: https://helrig.com/helix-bluetooth-midi Helrig is an unofficial, independent project, not affiliated with or endorsed by Line 6 or Yamaha.
    1 point
  24. Have you searched the Helix Marketplace options? I found this: https://line6.com/mp/product/3896 … but I’m not a bass player and have no idea whether this would suit you. Just want to point out the Marketplace.
    1 point
  25. To submit a feature request: https://line6.com/company/contact/productfeedback/
    1 point
  26. Then spend 10 minutes and just fix it yourself! No need to "clean" anything, since the Helix is brand-new. Take the back cover off. Loosen up the expression bolt or even remove it to make sure grease gets into appropriate places: wherever all those plastic spacers etc make contact with metal, it squeaks. Obviously don't grease up the thread of the bolt where the nut is attached, or it will come off. Otherwise grease everything up. Tighten all the screws while you're at it (in particular the "claw" that attaches the pedal to the mechanism). Those 2 screws need to be tightened, otherwise the pedal can go crooked. When it goes crooked, it squeaks and scrapes. At the factory they don't tighten it all the way. Some people say Lithium grease is bad for plastic, I don't believe it. Spread it all over like cream cheese on a bagel. It'll be absolutely fine. It's a 10 minute job. I've done way more complicated surgeries on my equipment. I addressed the squeaky pedal and my Helix has been silent since 2021. Out of all the Helix repairs, this one is the easiest. Just note which screws came from where when you remove the back cover off. Have good quality Phillips small/medium screwdrivers, so you don't strip the screws. With the Line 6 instructions, you should be all set.
    1 point
  27. Hi, Hmm… not a bug - it’s the way it works. A few things to bear in mind here - all signal paths are stereo throughout, and an amp block is essentially a mono effect. Any mono effect on a stereo path will collapse it back to mono. I’m not sure what you are really trying to achieve here? Are both of those signal paths using identical amp blocks with identical settings? If so, then have your drum bus feed into path 1, then add a single amp block adjusted to suit, then Y split the following path into 1A and 1B and then pan those hard L&R. Not sure if this helps - more info may be required.
    1 point
  28. Ha, yes, fair point - although firmware v1.4.2 has now been released which fixes this problem :o)
    1 point
  29. Interesting. I don't think that the Stadium, nor the Helix, worked that-a-way. But I don't see why you can't have what you want. It is NOT a bug. I would file it as a feature request. But let me give it some thought. And maybe some really creative, knowledgeable, and talented types on here has figured, or can figure, this one out.
    1 point
  30. Working fine for me. If USB MIDI is ON and MIDI PC Rx is set to USB, and both the MC3 and HXS are set to MIDI Channel 1, connect the MC3 USB to your computer and use a MIDI MONITOR to see what's being sent. If you don't have a MIDI Monitor, you can use this free web based monitor: Disaster Area Designs MIDI Monitor
    1 point
  31. 1 point
  32. Sounds fun...I have your part 1 patch somewhere, maybe time for me to check it again.
    1 point
  33. What i will miss: - the better audio device (Valeton only supports 44.1 KHz) - The Mic in with 48 volts - Parametric EQs as blocks, not only as global EQ - Some unusual patches like the organ patch from Glenn de Laune - Quality of some effects, especially when it comes to pitch shifting and polyphonic things. So enjoy your devices, they're really something great.
    1 point
  34. You can easily invert that. Just activate the block you want on the "lightning" state manually and deactivate the other (not using the switch). That'll flip the on/off and the light status.
    1 point
  35. I had the same issue with not being able to do the update via USB connection to my computer. I kept getting an error saying unable to install update response -3. I finally did what was mentioned below and did the update from the device itself and it worked. While I'm glad I got passed that, it's still been extremely frustrating the amount of bugs the stadium has for a unit that costs $2,199.99. From the moment I got it there has been bug after bug. I didn't get my first Helix until it had been out for several years so maybe it had lots of issues out of the gate too, but I never saw those. This is pretty ridiculous. All that being said, once you can get past the interface bugs, the unit works great. Hopefully they get this stuff worked out soon.
    1 point
  36. 1.) Define and understand your requirements. Effects thingie that can run multiples and has a desktop editor. Must have MIDI, scribble strips, and lots of buttons, doohickeys, and entire I/O sections that I’ll never use. 2.) Search the marketplace for a device that currently meets all requirements. Check. 3.) Don’t buy something that may (or may not) meet one or more of those requirements sometime in the future. Check. I doubt Line6 will bother to remove the YouTube app in a subsequent firmware update just because they don’t want to patch it to run the latest ad service. 4.) Just because something is older doesn’t mean it doesn’t meet your requirements. I’ll say! Sitting out an entire product category for a couple of decades can really yield a makeover in the landscape. 5.) Every electronic device eventually fails, so age is a consideration but if it’s working when you buy it, it could continue to work for several years. . . If you buy it used make sure you have an adequate test/trial period or return policy. Buying new from a reputable merchant has its perks. 6.) [D]on’t expect the manufacturer to keep it up to date with evolving computer OSs.. . . . Don’t expect infinite product support from the manufacturer. I’m preparing myself for the sad day already. 7.) If you buy it used for cash from a stranger in a parking lot with no opportunity to test it … that might work out OK, but it might not. To make the most of our time together, I’ll ask the guy if he has any Pokemon booster packs while he’s rifling through the trunk of his 1989 Chevy Cavalier to see if he has the power supply. 8.) Good luck. God save the Queen.
    1 point
  37. This is very hard to answer - even with more relevant context: cab, how do you hear yourself, what genre and tone goal etc. What raised an eyebrow is the High Cut of 6.5 kHz in the parametric block: notice that the Parametric and Low/High Cut have a steeper slope compared to the cab and IR block. Try it at 12 kHz. That might help to make your guitar's attack more present against the keyboard and cymbals. Record your sound and compare it with relevant isolated guitar tracks. There are plenty on YouTube. That might give you a hint what is lacking or is too much. Generally tweak your sound at gig volume. Also make sure to read this article: Eric Klein: At Least Half of Your Modeler’s Sound Is Determined by Your Playback System
    1 point
  38. Apparently there were a number of intel based macOS applications still out there for Apple customers, that Rosetta support continued in macOS 27. However, now I get the deprecation alert that the app will not be supported under macOS 28. Line 6, I'm not asking for any new features, but to simply compile this application for Apple Silicon Native. That way it'll continue to operate even under macOS 28. Appreciate it!
    1 point
  39. Also check your Global Midi Settings, there are 3 new midi commands sent out. I had to go in my Global Midi Settings and turned OFF Matrix 1/4" Midi, Matrix XLR Midi, and Matrix Phones Midi, then everything worked again with a restart. Then I had to basically set my EXT Amp Settings to the opposite of what I had them to get the EXT Amp switching to work again. Now it's all working again. Hope this helps.
    1 point
  40. Restarting doesn't make a difference. I installed the Stadium App onto a different computer and I get the same result (no USB connection). Both PCs are newer high-end machines running Windows 10, so its not like I'm trying to connect to an outdated machine.
    1 point
  41. I'll take that as permission https://github.com/zz9pa/Amplifree If Line6 disagree - I will of course take it down immediately. Still working on getting the editor working properly - but it should already allow selection of tones from the 100 stored on the amp, and the tuner probably works too Your mileage may vary etc.
    1 point
  42. I have also been testing Showcase MIDI song selection extensively with a Helix Stadium XL and the app Easy Performer, and I wanted to share my experience. I can confirm the behavior described in this thread: CC63 works correctly by itself and changes the Playlist. CC10 works correctly when the desired Playlist is already active. However, sending CC63 followed by CC10 does not reliably select the requested song from the newly selected Playlist. I also tried adding delays between the commands, but could not make it consistently reliable. I eventually found a workaround that is much more reliable for my setup. I created a "MASTER" pad in Easy Performer that sends CC63 = 0, selecting the main SONG LIBRARY. Once the Showcase is in that state, I can use individual song pads that send only CC10 to select the desired song. There is an important detail: for this workflow to work reliably, the currently selected song must already be paused/finished. The MIDI command then puts the new song into a queued/paused state. I have not been able to make the newly selected song start playing automatically through MIDI. So my workflow is: MASTER → select SONG LIBRARY SONG PAD → select song (Queue/Paused) then manually Play This is much more reliable than trying to send Playlist + Song selection together. To me, this suggests that the issue may be related to how Showcase handles the change of Playlist/context before processing the subsequent CC10 command, rather than simply being a problem with MIDI transmission. Hopefully this additional information can help reproduce and eventually fix the issue.
    1 point
  43. In think, I got what you are speaking of... however,to my ears, mic placements changes sounds - sometimes even more than the cab itself... And some placements I never like... (Cone, close)... I think to understand the cab sound, for me it would help to go through with a standard mic setting... Should not be too hard to implement ("lock mic"-button)... That's why I wonder, if I miss something?
    1 point
  44. Hi everyone, I am writing this post as a concerned Mac mini M4 user. Every time I open POD Go Edit, macOS repeatedly warns me that this software will soon lose support because it still relies on Intel architecture (Rosetta translation). Apple will eventually drop Rosetta entirely, and the POD Go community on modern Macs will be left completely stranded. We need an official statement or an update: When is Line 6 planning to release a native Apple Silicon version of POD Go Edit? Furthermore, the user interface (UI) feels incredibly outdated and clunky for modern desktop standards. Navigating the software feels like a chore rather than a helpful tool for musicians. The POD Go is an amazing piece of hardware, but the desktop software experience is severely lacking and falling behind the competition. Please, Line 6 team, give us a modern, native app that matches the quality of the pedalboard itself. Who else is facing these constant macOS warnings? Let’s bump this up so the dev team takes notice.
    1 point
  45. Would the community really get upset over like 100 USD? I think itd be a good thing if line 6 opened up the unit so it doesnt become e waste or redundant as quickly. Id gladly pay for the model packs if they were avaliable (even Line 6 Selling said firmware i mentioned in OP), im not trying to cheap out on this. For guitar i can get away with not using the Model Packs but being stuck using the Flip top for bass isnt ideal. The SVT or the G Cougar are deffinatley needed. Honestly ill give it abit of time and if something doesnt become an option i can just sell the unit and use my Orange AD200 Bass Amp.
    1 point
  46. I am one of many people who bought a brand new 2025 Helix Floor model and am wondering when there is an update to 3.80 available? There are many users of the Floor and these are STILL available at major retailers new. Certainly the best of the Floor series is worthy of an update to remind loyal Helix users that their expensive investment on these units is worth it (as evidenced by support from Line 6).
    1 point
  47. Another reason for drops (not saying this is the case for anyone here, but just something to ba aware of and check) is something configured with the same IP address as the Stadium. If you monitor ARP entries (though whatever method...), this would manifest as the mac address associated with the Stadium's IP changing back and forth between whatever device has the same IP and the Stadium.
    1 point
  48. I found a solution for my issue. I put the Monkey application in Windows 10 "XP Compatability Mode" . That fixed my issue and the FBV MKII now connects to my W10 Laptop without isse.
    1 point
  49. Don't you mean 'not really what I am waiting for'? Not sure how you can extrapolate to 'most people'. I happen to prefer the Grammatico and am certainly not waiting for another high-gain amp/channel.
    1 point
This leaderboard is set to Indiana - Indianapolis/GMT-05:00
×
×
  • Create New...