Leaderboard

It doesn't matter what you think you see in the preset. The only thing that matters is what is actually being sent. Here's a simple FREE monitor: MIDIView - Free MIDI Monitor tool for Win & Mac Here's an online monitor: Disaster Area Designs MIDI Monitor

Yes. You use the Stadium app running on your computer to export Setlists and USER presets to a folder on your computer. Then you swap devices and use the app again to import them to the other Stadium device.

Stadium can import individual IR wav files, but not the set of IRs contained in a Helix Bundle or Backup file. Here’s a potential workaround for IRs: 1) In Helix Edit go to the IR area. Select all IRs and export them all in a single operation to a specific folder on your computer. 2) In the Stadium app go to the empty IR library window. 3) In the IR computer folder Select All wav files. 4) Drag/Drop the set of all selected individual wav files into the Stadium IR library in a single operation.

I don't think the question is how is it possible, but is it possible? The answer (AFAIK) is no. That would require something like a sidechain triggered by a gate, which the Helix does not have. All time based/mod effects in the Helix run off their own clock and are not 'triggered' by an input. Your sound bite is very cool, but also sounds very DAW/Studio based and outside of what the Helix can do. It'd be cool to define (for example) the point on the curve a flanger starts when triggered by a sound, but no.

Computers. Can't live with them, hitting them with a stick is satisfying but expensive.

This is a known bug that should be fixed soon.

You can submit this idea as a feature request here: https://line6.com/company/contact/productfeedback/ It has been suggested before but the more people request it the more likely it will eventually be implemented. The idea is partly addressed in Helix Stadium. This is how presets now behave in Stadium - a change to one preset is propagated to all. It has not yet been implemented on a per-block basis but the request has been made there too.

What silverhead said. I'd possibly not bother too much as the latest internal cabs of the HX series are pretty damn good, so you'd likely be wasting a lot of time hunting IRs without much of a substantial win (if any). Add to this that you'd have to "waste" an extra block for them whereas you could just use a single amp&cab block in case you're doing fine with the internal cabs.

An IR is effectively a Cab. It is not an amp replacement. It is based on a capture of an ‘Impulse Response’ generated by a specific cab and microphone combination including a specific mic placement.

user error found and remedied.

Try the mode button.

This is a known bug that came with the latest update. It will be repaired in the following update, which I am told will not be for about a month or so.

It sounds like you're comparing apples and oranges. No FRFR (and I mean none) will sound the same as your amp through a guitar speaker direct to your ears. When modelling there is always a microphone between the amp/speaker and the reproduction system (then your ears). So, unless you're mic'ing your amp into the B1s you, and the audience, are hearing a raw guitar amp/speaker sound. To acheive a similar sound with a modeller you would use an amp model, into a power amp, into the speaker cab - no speaker model. If you mic your amp/speaker and run it through the B1s as well as stage, you need to work out how that sound compliments the stage cab sound in the room and aim for that through the B1s, or the compromise that emulates that mix. The latter will be very tricky. You might need to change your mindset about what you want/need to hear and accept the inherent compromise of ALL modelling. As to the volume jumps between amp models - that's why the Helix/Stadium chain has a heap of post production tools like compressors and gain blocks to normalise the levels, and EQ to assist with getting common perceived volume. The analogy of modellors being amps and effects in a box is fundementally flawed, they are a studio in a box with guitar amps and effects and need to be treated like that.

Any questions on bundle-and-save should be directed towards Flo.

Maybe a stupid question, but as you've not said, is it connected - as in with a USB cable? Have you tried different cables, and/or USB ports? Not much else I can suggest with limited info, AND not being a Mac user. Howver have seen lots of posts about specific Mac OS and Line 6 incompataility, so maybe post your OS version as well and any other info a Mac user might need to help. They are all just end users here, not Line 6 support, so need all the info you can give.

Load a MIDI Monitor program so that you can see what EXACTLY is being sent. Using the preset that works, note (on paper) the messages being sent by each Snapshot. Do the same with the preset that doesn't work. This procedure will show you where the problem lies.

I haven’t done this myself but the manual says you can. See Global Settings -> Switches/Pedals, particularly the Control A/B settings. You will need a TRS cable with a Y-splitter to control up to two external pedals/footswitches. Also, probably good to read the manual section on Configuring External Controllers.

rmbecker23, Maybe I missed it, what amp are you using? jpd

https://rigclone.com/ https://thegearforum.com/threads/fractal-and-helix-stadium-presets.10392/

HELLO IM ITALIAN AND WRITING IN ENGLISH, SO FORGIVE ME FOR ERRORS I HAVE RECEIVED MY NEW HELIX STADIUM XL AND UPDATED IT VIA WIFI (ANYONE CAN TELL ME HOW UPDATE VIA USB AS THE OLD FLOOR HELIX?) AND IMPORT OLD PRESETS EACH ONE WITH 8 SNAPSHOTS. THEN THE PROBLEMS: - SOMETIMES THE STADIUM FAILS TURNING ON WITH CONTINUE REBOOT AND THE "X" ON THE SCREEN ALTERNATE TO "LINE 6 HELIX STADIUM" LOGO MESSAGE - WHEN CHANGING SNAPSHOTS WITH THE CHANGE OF AMP OR CAB MODELS YOU EAR A BIG "POP" AND LOUD SO I CREATED THE PRESENTS FROM ZERO, I DID A FACTORY RESET AND START PROGRAMMING WITHOUT IMPORTING NOTHING AND: - THE BIG LOUD POP REMAINS CHANGING SNAPSHOTS WHEN I USE 4 AMP AND 4 CABS AND TURN ON DIFFERENT ONES IN DIFFERENT SNAPSHOTS (I READ SAME PROBLEMS OF OTHER PEOPLE TELLING TO USE THE SAME MIC IN THE CABS, OR USE ONLY ONE CAB.... BUT REMAINS!...THE PROBLEM IS WHEN YOU USE DIFERENT AMPS....) - DIDN'T SAW THE OLD REBOT PROBLEMS BUT THE MOST INCREDIBLE AND NON SENSE BUG NOW IS: IF I DISCONNECT THE STADIUM FOR HOURS AND THEN I TURN IT ON, 3 TIMES ON 5 YOU WILL NOT EAR NOTHING! NO INPUT AND OUTOUT VOLUME...THE IF YOU ARE LUCKY, AFTER SOME REBOOTING ALL IS NORMAL..... IS NOT HARDWARE PROBLEM CAUSE WHEN THE SOUND IS DISAPPEARED, IF YOU RESTORE FACTORY DAFAULTS IT WORKS. SO IS A FIRMWARE BUG I THINK. ANYONE HAS THE SAME PROBLEM? DO YOU KNOW IF LINE6 IS PROGRAMMING TO RESOLVE AND IN LITTLE TIME WILL BE ABLE TO RELEASE A NEW UPDATE FIRMARE?? WITH THIS 2 PROBLEMS IS IMPOSSIBLE TO RISK IN A LIVE CONCERT AND FOR A MACHINE OF 2400 EURO IS A THING SCANDALOUS!!!

For anyone hitting this post searching for how to run Helix Stadium on Linux, I've figured out one way to do it - but it only works if you have Wifi setup on the Stadium Install Steam Download the Helix Stadium installer In Steam go to Library > Add a Game > Add Non-Steam Game and select the downloaded installer exe Find the entry in your Steam Library and click Play, the installer should show up. Go through the install steps choosing the defaults Once that's done you'll need to find the directory that Steam puts file under. For me it was ~/.steam Under that directory you need to find where it installed Helix Stadium. For me it was ~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/Helix Stadium.exe. Copy the full path to the EXE In Steam right click on the entry for the installer and choose Properties... Rename it to Helix Stadium Change target to "{path to the exe above}". For me it was "~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/Helix Stadium.exe" Change Start In to "{path to the exe above but without the exe filename at the end}". For me it was "~/.steam/steam/steamapps/compatdata/{the most recently created folder}/pfx/drive_c/Program Files (x86)/Line6/Helix Stadium/" Close the Properties window Click Play and Helix Stadium app should start I had to cancel the auto connect, and manually type in the IP address, then click Connect (this needs to be done at the start every time) Once I did that it works as expected! Hope that helps somebody.

Windows 11 considers this driver invalid and refused to switch 'core isolation' on, which MS considers a safety issue.

I'm not going to re-type my explanation/refutation of your nonsense assertions. If anybody believes this guy, tag me and I'll link to the LENGTHY discussion that he hopes nobody is skilled enough at SEARCH to find for themselves. The short version - there's a SWITCH. In one position it IS attenuated. In the other position it is NOT attenuated. It's an OPTION. The long version explains the reasoning.

Hi all, I recently posted this on a couple of Pod Go Facebook groups, so thought it might be useful for folks here too: NEW YEAR TIP: POD GO BACKUPS, SETS for GIGS, FRFR, AMP, HEADPHONE Hi guys & gals, and a very Happy New Year to everyone. Although I’d kind of assumed that this was pretty much common knowledge I’ve since picked up that it’s not, so the following might be useful especially for those who’ve used up all their Pod Go slots, & who need patches to suit different guitars, amps, FRFR, headphones etc and are worried about tweaking/over-riding settings and losing the originals. OK, I think Pod Go users are pretty familiar that when there’s a firmware upgrade (which incidentally you should only ever do through the latest Pod Go Edit) the process creates a back-up for you. You can also create a similar back-up if you go into ‘file’ in Pod Go edit and select ‘create backup’. These backups are a total backup of everything in your Pod Go and are convenient from a ‘safety’ aspect as these will get all your patches and IR’s back into your Pod Go if there was a glitch/failure & you lost everything. But it’s an ‘all or nothing’ backup and you can’t see and access individual.pgp or .wav (IR) files within the back-up file, which is a bit of a nuisance if you mucked up a single patch and wanted it back how it was. Now, I think most folk know you can save an individual .pgp file and export it to share or put on Line 6 Custom Tone etc. But some folk are under the impression that it’s a long and laborious process to save every .pgp and .wav file in their Pod Go – with up to 128 files in User, factory & IR sections that’s 384 files. But it actually only takes a minute to create a full back-up of all your user & factory patches & IRs in their proper .pgp and .wav format. Here’s how – I’ve made this step by step but the whole thing takes less than a minute: 1. On your PC or Mac create 3 folders and name them e.g. ‘My factory’, ‘My user’ and ‘My IRs’ 2. Connect your Pod Go to Pod Go Edit 3. Select ‘user’ patches in Pod Go 4. Click on patch ‘01A’ to highlight the whole entry in grey including the patch number (don’t select just the name where it highlights in blue) 5. Using the scrolling bar on the right of the patch list, not your mouse, scroll down to the last patch (let’s say you have used all 128 slots and its 32D but if you have less just go to the end of your list) and just hover the cursor over the patch name and it will highlight it in grey. 6. Now, hold down ‘shift’ on your keyboard and left click your mouse on the patch – you’ll now see ALL 128 factory patches grey highlighted. Now right mouse click and select ‘export’ or ‘Control+E’. 7. A ‘browse for folder’ dialogue box will appear. Go to the ‘My user’ folder you created in step 1, select it and press ‘OK’. ALL your patches will now load into that folder and they will be in full .PGP format that you can import back to Pod Go as individual files, or as a group set, or the whole list. So if you mucked up say patch 24B all you need do is go to that patch in your backup and drag and drop it back in to the relevant slot in Pod Go Edit. 8. Repeat the same process for your factory and IR patches, and you’re done. What’s great is that you can create groups of custom patches eg gig sets, patches for different guitars, patches for headphones tweaked for FRFR etc. Even if you’ve run out of blank slots, once you’ve backed up your original patches, it doesn’t matter if you copy these over other patches you don’t currently need because you have all of those patches backed up. And there’s no limit to the backups you can create. If you wanted to have 15 gigging patches for your Les Paul and 15 for your Strat and 2 for your acoustic, you can import and export these patch groups easily with no risk of losing anything you have. You can use the import & export set-list option within the Pod Go Edit ‘File’ tab, or just drag & drop these in. You can create umpteen patch groups eg those you’ve tweaked for FRFR or with your amp v those you’ve created for Headphones use. The options are virtually endless. You can even create template patches based on your favourite settings so that you don't have to start from scratch when you are creating a new patch.

For anyone who wants his variax to be more accurate: https://www.vguitarforums.com/smf/index.php?topic=24065.0

if u re-flashed ur hd500x, u must calibrate exp pedal, otherwise it will do nothing.