Search the Community

Symptom: On Windows 11 Pro version 22H5, the Stadium App v1.2.0.15 application window crashes every time upon attempting a USB-C cabled connection to a Helix Stadium Xl at Firmware Version 1.1.0 Build:1274 for the purpose of doing a Stadum XL firmware update. This is caused by the ‘Helix Stadium Bulk Transfer’ driver packaged with the Windows version of Stadium 1.2 App not loading. On Windows, navigate to Device Manager and see the ‘Helix Stadium Bulk Transfer’ driver listed as ‘Other device.’ This is not normal. Look at the properties of this device and you will see the driver is not present and has not loaded. This is why Stadium App 1.2 on Windows crashes every time on attempting to connect to a Stadium XL over USB-C to do a fimware update. When you plug the Stadium XL into Windows via USB-C, this Bulk Transfer device appears as ‘Other Device’ but its driver does not load. When the USB-C cable is unplugged this ‘Other Device’ disappears from the Device Manager list. This issue was raised 4 December on a Line 6 forum but no resolution was documented on that post and its replies or subsequently that I can find. It has not been addressed by Line 6 yet in Stadium App 1.2 for Windows. Solution: The Line 6 developers need to fix the USB Bulk Transfer driver they are distributing with the Windows version of Stadium App 1.2. Workaround: The Stadium 1.2 app and drivers provided for Mac OS work. If you are a Windows user, you will need to ‘phone a friend’ who has a MacBook, load Stadium App 1.2 on it, make your USB-C connection between MacBook and StadiumXL, launch the Stadium App, and connect to Stadium XL so the current firmware version can be detected. If the Stadium XL is not already at 1.2 firmware version, you will be prompted to download and transfer firmware 1.2 to the Stadium XL. Background: After unboxing my Stadium XL on Monday morning, I spent hours as a Windows user trying to get Stadium App 1.2 to connect with my Stadium XL without crashing. On Tuesday, I brought my Stadium XL to work and borrowed a colleague’s MacBook Air to do the 1.2 firmware update. All went smoothly. As a hobbyist, I bought the Stadium XL specifically for the Showcase feature which is what distinguishes the Stadium XL from all other modelers at present. I was going to go for the Fender ToneMaster Pro until I randomly came across a YouTube video discussing Showcase. I was keen to immediately update to firmware 1.2 to start experimenting with Showcase. I have a 4Cast MVP stand-alone MIDI-controlled video playback ‘jukebox’ coming on Saturday which I plan to USB-C connect with the Stadium XL and recive MIDI note commands from Showcase flags to start the music video that goes with the song I am currently murdering with my guitar ‘playing.’ I will be using an AI stem extractor to get stems from the music video’s audio track to include in Showcase so the audio and video will remain sync. Obviously, Windows users need the Line 6 developers to fix the Windows distribution of the Stadium App going forward so it includes a USB Bulk Transfer driver that Windows can load. I can live with firmware that is ‘buggy’ on the features front because Line 6 has a proven track record of solid support for the original Helix over the last 10 years but when the USB bulk transfer driver needed for Windows users to apply firmware updates over time to fix these bugs is itself broken out-of-the-gate, that is a significant problem.

Hi I did search for this but couldn't find the same bug. I have a preset with 4 snapshots. I created this from scratch in the Stadium XL software and copied the snapshot settings I created to 3 others in order to tweak them for lead, quiet, chorus etc. While changing drive settings for the amp block in the Stadium XL app, then saving the preset I noticed that no levels changed on the unit itself despite the snapshot obviously changing. I'll try and add a video. Stu

Morning Not a massive deal but copy and pasting a wah or gain block that has expression pedal latching etc from one preset to another results in the target blocks behaving very weirdly: the new blocks don't turn on with the toe down click on the expression pedal first time, but do the second time, but now the expression pedal is "off" and movement won't be registered. Deleting the pasted blocks and just creating new ones with the same switch assignments works fine. There you go.

I have a patch with 3 snapshots. The expression pedal is assigned as a volume pedal in each snapshot. I start on snap1 with the pedal all the way at min position. If I switch snapshots, the min position is not honored by the next snapshot. It resets the volume and I have to push the pedal down and back up again to get it to work correctly.

I have a HOTONE Ampero Control Sending MIDI to a Timefactor and then THRU to my HX One. Currently PC messages and some CC messages are working fine, but I cannot get it to respond to CC64-127 (tap tempo) or CC93-127 (enter tap tempo). I have tried everything I can think of... MIDI Clock RX off, on, auto. (When set to on or auto, MIDI clock is working fine -- Clock coming from Timefactor) As I said above, other CC messages are working fine, but can't get anything related to tap to work properly. Wondering if this might be a bug. I am on software 3.71.0

Hey all, I didn't see any post that covers a potential bug I've found yet so posting here. I am using Helix Native 3.71 on Windows 11. My PC is decently high-end, 32gb RAM, 7900x CPU, etc. I've confirmed this occurs in both Cubase Pro 13 and FL Studio 21.2.2. Fresh installs of everything. UMC404HD interface. Helix Native works fine once added to a channel initially, and even after switching through a few different presets, but eventually after switching through many presets (30+) it stops outputting any audio. The plugin still does show the input levels are present (see pics), but even if you disable all the effects or switch presets, once it enters this broken state it will no longer output any audio. If you restart the DAW or delete the plugin from the channel and re-add it then it works fine with any preset again. In FL Studio, it actually makes a quick buzzing sound at the moment it breaks. When this occurs, other instances of Native on other channels don't cease functioning. This feels like it might be a memory leak within the plugin; resources are being allocated when switching between presets but never released, so eventually it presents an OOM exception in Native. It seems to happen faster when switching between more intensive presets (ie: DEVIN TOWNSEND). However, I don't see any increase in memory usage in the Task Manager when this happens. Does anyone know why this is occurring and how to resolve it? Is it possible to file a bug report? Would any other information could help debug this? Greatly appreciate any insight, thanks.

Possibly a bug or possibly something I'm not doing right: I'm trying to use path 1 for a guitar using the Guitar Input, and trying to use path 2 for a bass guitar using the Aux Input (found on the back) When I set this up, so that Path 1 uses "Guitar" as the input, and Path 2 uses "Aux" (neither are using the Multi-Input), signal from the front Guitar port is always sent to Path 1 AND Path 2, when I would expect it to be sent to Path 1 only. If I use the return jacks I can get it to work, but then I'm losing one of the return slots. Is this a confirmed bug? Ta very much, redev

Is anyone here pretty experienced with automating preset and snapshot changes inside Logic Pro X? I’m having an issue with automating the changes to while sending hotkey messages to control Logic. Curious if my problem is in command center or in the setup of the midi track within Logic. Hotkeys work perfectly until I start to automate patch / snapshot changes. As soon as I add the automation track, the hotkeys glitch out. I've also used MIDI notes instead of hotkeys and still encounter the same issue. So, for example. I’ve got hotkeys set up for play, stop, cycle, next marker, and previous marker. Momentary switches. Works perfectly without issue. Then I add the automation track. When I hit the play button on the Helix, the button acts like a latching button and causes the whole project to glitch out. Only way to fix it is to turn off the Helix and restart Logic. Hopefully I’ve explained this in a semi-understandable way haha thanks in advance for any advice on how to fix this!

Somehow, during service, my instrument cable disabled my preset. Is this a known bug? Is it a feature that I am somehow accidentally enabling? Is there a way to turn it off or fix it? In moving from my usual spot, to the front of stage, and back to my usual spot, my cord draped over my Stomp. In moving my cord off my Stomp, somehow I moved from my preset (004) to the next preset (005). In attempting to go back to 004, it would skip to 003—back and forth between 003 and 005. This issue persisted until I was able to turn my Stomp off and back on again. Thankfully, I had a duplicate preset ready to go. This is the only issue I’ve ever encountered with my Stomp in the couple of years since had it, but this issue has popped up a couple times now. Thanks in advance!

Hey all, My amp will randomly max out the reverb mix. I go in to the app and move it back down to my desired level but it will just jump back to 95%+ after a few seconds. This happens if I have the Bluetooth connected or not. I have updated the firmware to the latest version and unistalled and reinstalled the app to no avail. I have seen a similar post but with a different parameter, but there was no response. I need this resolved otherwise I'm gonna have to get shot of the amp as its literally unusable. Thanks.

I have uploaded my Pod Go .pgp patches, and when they are downloaded, they change extension to .l6t (original uploaded files were .pgp). I have tried this numerous times, with same results. It seems like a bug. Does anyone knows how to resolve this? This is an example: https://line6.com/customtone/tone/5879890/ You will notice that it is uploaded and marked as Pod Go (.pgp) file, but still... I would appreciate any help.

So, I bought a Vetta 1 combo today and it was working perfectly in the store. I brought I home and plugged it in and was presented with this (see image) the screen looks garbled and wonky. I took it back to the store because they have a 60 day warranty on used items and i won’t have it back for about 2 weeks. Does anybody know anything about this? I thought it had something to do with the internal battery but I just want to see if anyone here knows anything about this.

I updated Native to 3.10 and now have noticed that some of my blocks are missing some of their assignments. For instance I had a expression pedal controlling the delay time on the Cosmos Echo (midi cc4) and a Bypass parameter (midi cc12) working just fine before updating to 3.10. Now the Time parameter is gone and when I add it back it will not save the time parameter, it just disappears when I reload the saved preset! A similar thing is happening with my volume block. In the video you can see that both parameters (bypass & time)are there then after switching back and forth presets the time parameter is gone. Any help with this would be greatly appreciated. Thanks, Leroy IMG_1107.MOV

So I'm using my FBV Midi controller's expression pedal with Native (have tried both Reaper and Cantabile - this happens in both). On the Pitch Wham block I'm assigning my expression pedal (CC7) to the Position slider and it works perfectly, however if I switch Preset (and then reopen it) or restart Native the controller assign is gone. I can assign the expression pedal to other sliders on the same Pitch Wham such as Mix and that works and saves. I've also tried creating a blank preset with ONLY a Pitch Wham and this still occurs. You can see in the screenshots, the preset is definitely saved and all I have done is switched to another preset and then re-opened the original preset and the controller assign is empty.. Can anyone replicate this??? Can you assign an expression pedal to the Position slider on the Pitch Wham AND save it???

I just started my 15 days trial today and I mostly like this software but seriously, why is the input meter so glitchy? Output meter too. Compared to my DAW's (REAPER) meters, Helix Native's meter sometimes simply "doesn't notice" I just played a note, and when it does, it's some random level. Also the little bar that marks the highest volume reached sometimes just doesn't appear. Honestly looks like a bug. It's just barely usable to set the input gain. Or is it just me? Running on Windows 10, VST3.

Hi I think I found a small bug in cosmos echo when you set it to 1/8 triplet delay it sounds the same as 1/4 triplet delay. cheers Milo

Hello, I have a strange issue with my Line6 Helix device. Even when I turn down my "Phones" output all the way down to zero, I still hear sound coming from my right headphone. Is this a known bug? Is there a way to fix it?

I'm using Reason 10 as my DAW, and whenever I load Helix Native, esp if I go to a user preset (a new blank slot or one of my previously made patches) I get auto patch changes even when the sequencer is not moving and no midi is being sent. Any ideas what causes this or how to prevent it? For example, I turn off the delay and reverb at the end of my patch (bypass) to hear the pure tone so I can edit the noise gate, and while I'm tweaking and playing, the reverb turns on for no good reason, and I look up and sure enough, I'm on snapshot 2, when I DIDNT MAKE ANY SNAPSHOTS because it's a BRAND NEW PATCH?! What gives? I'm on OS X 10.12.6 (I know, old, but still meets the requirements, and no I'm not upgrading my OS), and Reason 10.4d4. I'll check Ableton/Logic/PT but even if it *does* work normally in those, I want to use Reason as my VST host and I've never had any problems with any other plugin I've ever used (from Native Instruments, Waves, Roland, Novation, Toontrack, XLN, etc) this Line6 plug is the only thing that has ever shown such weird behavior. Thanks!

Hi all. I'm currently still on firmware 2.81. Had no issues with my helix floor until upgrading firmware a few months back. After the backup and upgrade a whole heap of presets I'd made did not function properly, with 'snapshot unable to be recalled' (or a very similar message) being shown in HX edit. What I found was that reverb or delay blocks seemed to be at fault and I had to go through and change them (delete block and add it back in again) and re-save all the presets so they worked again and could be saved and reconfigured in snapshots. Now I have that all fixed I have recently, in the last 3 weeks, experience my unit starting to cut out, either indefinitely, ie screen still lit, ability to change presets and snapshots etc but no audio coming from the unit, or the unit will stutter, ie I could play a chord and let it ring and the audio being transmitted either to monitors or amp (this happened live at the weekend) cuts in and out in a very random and digital way. There's no manipulation of the sound (warping etc), just like there is a mute switch being flicked on and off intermittently. It feels like this is a processor issue, but I don't really know. Any recommendations? Should I just backup the unit and update to the latest firmware and hope this fixes the problem?

Hello guys, I have a strange problem with Helix Native in Cubase 9.0.40. When I activate the Monitoring on an Audio Channel with Helix Native as Insert Effect, I still get the clean signal together with the processed Helix Native signal. Even if I deactivate all outputs in Helix Native, I still get the clean signal from the Guitar. Direct Monitoring in Cubase is deactivate (obviously as you can also hear the processed sound from Helix Native) and other Plugins (like Guitar Rig) don't have this problem. It seems that the clean sound is always routed inside Helix Native when Cubase Monitoring is activ. This problem appears only with Monitoring. When I play back a recorded track (monitoring function now deactivated as it wouldn't play back the sound), the signal is processed the normal way. Does anybody else have this problem? Thanks for your suggestions. Greetings, Jan

Hi! I've been using the Helix for 3-4 Months now and i really love it. Now i started messing with the whole Snapshot thingy... Basically, what i want to do is: - Switch between 8 presets normally - on one of my presets i want to switch the snapshots i've created - go back to 8 presets again Now, maybe i'm doing something horribly wrong but i can't get those simple 3 things to work properly. What i've done so far: I can switch to 4 snapshots / 4 presets in the global setting, this works perfectly. I can do the normal 8 preset thing. BUT as far as i understand, i should be able to switch between those modes with the "MODE" switch. But everytime i hit the "MODE" switch, ll the scribble strips go black and nothing else happens. If i push the "MODE" switch again, it goes back to 8 presets. I've done a global reset since, but this hasnt changed a thing. I guess there is some setting i am missing and then it should work properly? I would really appreciate if you could do a "step-by-step" explanation for dumb people like me^^ Or just tell me where the setting are that i'm missing... Thanks a lot!

Hi everyone, First time poster. I have read through the topics here on the forum but it seems like the topic has not been covered. Been using the helix floor for a year now. Great piece of gear! It is in my understanding that using snapshot is the way to go to change parameters with a patch without the ''sound gap'' you would get by switching presets. So I've been using snapshots for in-song changes, and presets for song-to-song (which seems to be common). Until now everything worked fine. I updated to 2.82 lately. I have a couple of presets based on the same ''rig''; the only thing that tends to stay the same would be the amp settings. Effects and snapshot changes. Last week I started to experience a ''sound gap'' (like the one you get when you change presets). Strangely, it seems to be related to when 2 presets are the same, within the setlist. I tried to build the preset from scratch instead of copying it, but as soon as I match the amp settings, I get that problem when I go through the snapshots. I don't know if someone encountered a similar problem, or even if I did explained it well, but if anymore encountered a similar issue, or have a fix... Thanks in advance for your help. English is not my primary language but I'll try to give more details if some of you have question Thank you, Cédric

My patch-settings (Amp-Parameters) differ from one unit to another! The unit on the left side is a HD500x, the one on the right side is a HD500 The unit on the right side differes in a missing "Blackface Lux", which is wrongly replaced by a "Blackpanel Pete" and all Amp-parameters seems to be at the default-settings. I have re-flashed the POD500 (noX) but the problem is still the same. It is espacially spooky, because the following preset 01D is the same one as the 01C where only the Phaser is turned on. I will now reflash the unit 2-3 times again. Please help me!

I've had the Helix a couple weeks, and have been studiously setting up a single Preset and 8 Snapshots. Since Snapshots are my primary focus due to the large delay in preset switching, I've set the Global Setttings > Footswitches to "Manual Return" instead of auto. This was previously working fine. I could tap the Cancel button to return to Stomp box mode and enable/disable individual effects. Or I could use the Bank Up and Bank Down buttons to navigate around. Today when I boot up I find that I can't get into Stomp Box mode at all. Pressing cancel does nothing. Holding cancel will open Edit mode. Pressing up or down will allow me to choose a bank. I can choose any snapshot... I just can't get into stomp box mode? I'll try re-flashing later, but maybe I've just tweaked something weird. Anyone have ideas? I did muck with Global settings a bit to see what they did, and tried reverting some changes with no luck. ______________________ Coincidentally (or not...) The Bank Up and Down don't work as expected while in Snapshot mode. If I press Bank up, it will move one bank DOWN. Then pressing it again moves up as expected. Likewise, pressing bank down while viewing the snapshots will open up the next bank UP. Pressing it down again then moves back down. For example, I'm on preset 2A. Pressing Bank UP displays Banks 35 and 36. Pressing UP again displays Banks 1 and 2. Pressing Bank DOWN first displays Banks 3 and 4. Pressing DOWN again displays Banks 1 and 2. OCCASIONALLY no numbers will display at all and it will just say BANK on each. Pressing UP or DOWN returns to the expected BANK. Reversing the Bank up and down has no effect. It goes the wrong way the 1st time, then the way it was set the 2nd and 3rd. WTF?

Hi, Does any body experience this same issue? I've updated my Helix Floor from 2.7 to 2.80 and all my vintage delay blocks become a sort of ghost.It disappears from the signal path but they are still sounding in the back. If you try to do something that involves the delay parameters, even changing the tap tempo, it stops. I've already update my firmware to 2.81 and restore this presets from the 2.71 backup and still the same. This is my main delay so i don't wanna to reload every preset manually. So if anybody can help me, i'll be happy. Hola, Alguien tuvo el mismo problema? Actualicé el firmware del 2.7 a 2.80 y mi bloque de vintage delay se transformó en una especie de fantasma. El bloque desapareció pero aun sigue sonando. Si muevo cualquier parámetro relacionado al delay, este deja de sonar. Actualicé al 2.81 y restauré los presets desde el 2.71 pero todavía sigue el mismo problema Es mi delay principal y no quiero tener que volver a cargarlos de cero. Si alguien puede ayudarme, excelte Regards, Saludos.