jpdennis

I went back and recreated some of the patches from scratch as well as revisited the Vox patches. It seems I can use the default or just slightly below default setting for Ripple now. The AC isn't as pronounced as well. I am going to be away for about two weeks. I'll check this thread once I return just to see if there has been any furhter feedback from you or others. Merry Christmas, Happy Holidays, Happy New Year, and 2026 is almost here! jpd

I will be taking a two week hiatus from music starting this week. Hope you all have a great Christmas and a fun filled entrance into 2026. This will be the first year I did not applied for any music jobs during the end of year and first of year since 1967. My present to my family and myself is to be present this whole period. If I do not appear active for the next few weeks I am not being rude. Maybe you all and the Line 6 staff you may read this have a wonderful time this season! jpd

So far I have created two presets to date that trigger this issue. I uploaded the first one to Line 6 support via a ticket I created. They couldn't replicate it with my preset. I do not know if it is a continuation of the DSP issue where I could create a preset that should have been limited to adding FX blocks up to but not beyond the DSP limit of the device. I will reopen the ticket and upload this second preset. jpd

The workspace is saved for me as well when I am working in the user setlists. And the app is now full screen every time I open it. Plus I no longer have to resize the sidebar or the path & FX selection workspace once I set it up.

hairshirt, Line 6, as most other model manufacturers, is attempting to get as accurate a sound as possible. In the Line 6 reveal event for the Stadium they shared many of the latest values they are using for the modeling process. This "rectified 120Hz hum", while extremely accurate, isn't heard on the analog physical amplifier as it can be with the digital representation of the ripple value. I haven't used my FRFR yet. I will be doing that after Christmas by this weekend. Hopefully it gets buried a little more. I will let you know in this thread my findings. jpd

Daddy_Rocker, I have not seen this. I checked and was able to boot to maintenance mode several times. You may have already followed the exact procedure I have. I have the Stadium turned off. I then hold down Home & Song. With those two held down I turn on the Stadium and wait until it boots into maintenance mode before releasing those two buttons. Let me know if you already did this. If so you will need to create a ticket with Line 6 support. https://line6.com/support/tickets/add.html jpd

Yes sir. :-)

I found this from an older thread; Have you done this already? I do not have a pedal to test. However, phil_m is well known in these forums. Also, some have gotten this to work using a TS cable instead of a TRS cable. jpd

qm1pooh, If you've already tried the following, I apologize for any redundancy as you've worked through this. While I do not have a RC-5 to test, I dug through some manuals and a few online videos to be safe due to other stomps I've seen limitations on. First, a thought is to reverse what the RC-5 is expecting; have 0 on push and 127 on release. Also, is the RC-5 set to receive pc, cc or both? So, second, what happens if you change the value to 99 on press and 1 on release, and/or reversing that thought, what happens if you change the value to 1 on press and 99 on release? And determine which device controls sync tempo to be safe Master/Slave: Decide if the Helix or RC-5 will be the tempo master. If RC-5 is Master: Set Helix Global Settings > MIDI/Tempo > Receive MIDI Clock to "MIDI" or "Auto". If Helix is Master: Set the RC-5 to receive MIDI Clock in its settings. Sync Effects: On the Helix, set time-based effects (like delays) to use note values (e.g., 1/4 note, 1/8th) so they snap to the tempo. Please forgive me if you already have the manual, which I have attached in case you do not have the manual for the RC-5. I have watched two videos and included the link to one with insight into setup for the various toggles for cc and pc functions within the RC-5. I am researching one more thing and will revisit this thread later today if I find anything that be of help to you. jpd RC-5_reference_eng02_W.pdf

cchimi, Thanks for your input and analysis of this new feature. It is unacceptable that you would be chastised for asking a question especially since I do not see any disrespect in the posts you've added to date. I haven't yet focused on Showcase because I am rebuilding all my presents from scratch as I slowly go through the manual. After reading and rereading the initial request & replies, plus the insights, from everyone in this thread to make sure I what's being said so far, I may have to fast track my timeline to get to Showcase ASAP. I say this because I can think of a few scenarios from my past work that would fit this need. One is a group were the vocalist would get a request in the second set, as an example, to repeat a real crowd pleaser from the first set or advance one or two from the next two or three sets at that moment: bar band tip jar could even trigger this. Or the vocalist may not be ready to sing a song that looked great in the lineup but at 10:15pm doesn't seem to work for that vocalist. One other is the Friday-Sunday afternoon day time public event a one man band or small band venue that asks for requests for tips. I don't know the math of how many of current Stadium owners this represents though it could really be a great demographic to seek out as the Stadium evolves. And I know it will evolve as everyone keeps sending feedback, suggestions, and bug fix tickets to Line 6 support. This has been proven over the past 15+ years with the original Helix family. Having said that, this thread has pushed me to start attempting to use Showcase sooner rather than later to determine what can and what cannot be accomplished at this time. Thank you all for the push. Never too old to learn more. jpd

Did this happen even with the 1.2 F/W update? If so please create a ticket with support. jpd

Please forgive me if either of you you have already done the following ... and if so, create a ticket on the main line6.com page using the feedback link on the lower left about 2/3rds down ____________________________________________________________________________________________________________ Have either of you seen the update on the download page when you go there even though you say the download itself is the wrong version? And have you cleared cache in your browser as well as deleted any pointers to the original 1.1 download? And checked compatibility, Let other Mac OS users know by replying. If possible the OP may want to add - Mac iOS to the Topic. jpd

Scroll down about 2/3rds on the line6.com main page and look for the following on the lower left. Click on LEARN MORE.

From Line 6 Ripple—Controls how much AC ripple interacts with your tone. Power amp circuits will sometimes let a little bit of rectified 120Hz hum (that the power supply filter caps can't quite fully remove) into the audio signal when the power supply is being pushed hard. Much like Hum, Ripple provides a bit of non-musical distortion to the power amp at distorted settings. _________________________________________________________________________________________________________________ Just to baseline my findings, I use my headphones (open back 250ohm) for initial preset creation and playback. I have been tracking a disturbing "remnant" when playing a hot solo since I started using the Helix Stadium. As I was working on patch from another thread in this forum I tried something that has completely removed the "remnant" (or reduced it to below anything I can now hear). I set the Ripple value for the amp model to the lowest value available (so far either zero or minus 10 based upon the amp model). I haven't tested every amp. Of the ones I use right now only the VOX AC models still retain the annoyance even at the lowest setting for the Ripple value. Again, this is just my ear. You may not hear it as pronounced as I do or you may hear it more pronounced. With all the additional values Line 6 have been using with the new capturing it could be I never noticed it as predominant in the older Helix Floor I had. In fact I normally set Ripple, along with Sag, a few clicks higher than default. And I no longer own the Helix Floor for me to test. I thought I would share if this helps anyone else noticing an annoying remnant to a note as it is sustained and vibrato-ed as well. jpd

Note to all, For clarity and focus it may be best to start a new thread if the topic of the question you have doesn't directly relate to the the OP (original poster) Topic (in this case "Stadium XL update 1.2 problem"). Just a thought. jpd

Dougz51, I haven't tried with the v1.2 yet but with v1.1 on a Windows PC AND installing the ASIO driver after the amp only using the USB-C from the Stadium to the USB-C connection on my PC, playing YouTube vids to play along with works great. I use my headphones for playback. jpd

HeartySalmon, I think I located the issue. I set the Boost on the Kinky Boost to adjust by snapshot. That isn't the root issue but doing this will help. At this point the Kinky Boost FX block is on for all the snap shots. For the Clean Snapshot I have the Boost parameter off. For Drive SN and Lead SN I leave the Boost parameter on. I've attached my version for you to test. Also, I discovered something concerning the Ripple parameter for the amp that I will address in a new post. Let me know your thoughts, jpd BogDennis.hsp

I still notice popping using the Bogner preset using v1.20 F/W update when going from snapshot 3 back to SN1 or SN2. Not as pronounced but still slightly audible. I do not hear a pop using the 808 preset. If you've already updated to v1.2 do you still hear the pop on 808 or is the pop still the same on the Bogner presets for you? Let me know once you've updated what your findings are. And if Line 6 support gave any recent feedback. Thanks jpd

As most know from the Helix Floor I had, and making sure I was logged into the Stadium device; I export my presets because in my world my backups have backups. I then entered maintenance mode to create a backup. Next, while still In maintenance mode, I reset the Stadium to factory default & shut it down using the maintenance mode button for that. After logging into the Stadium desktop app, I used the app update feature on my PC to update the app first. While waiting on the app update process to complete I started the Stadium, reconnected to my network and entered the password (reset to default requires that step), logged in to Line 6 on the Stadium, and started the F/W update download. While waiting for the F/W download to complete, I went to the Line 6 site download for the latest ASIO driver download since it is not automatic at this time, installed it, then rebooted my PC again. The F/W update was ready by that time and, after a few minutes, my Stadium was successfully updated after which I turned it off. I then restarted the Stadium in maintenance mode, restored from backup, then shutdown again. While that is a lot to type the time went rather swiftly and successfully. That is my experience, YMMV. jpd

Sorry for the late reply. Internet circuit at my home and surrounding 4 mile radius was down for about 40 hours since Sunday. The USB-A does send power. It is the way the USB-Network adapter will need to be powered to work for the computer wired connection. Good experimental test. I am not sure of the power signal but it should be hot enough to power simple devices based up the rating in the UPDATE portion I have added as well as provide a charge your USB v2.0 or v3.0 power charging capable phone or tablet if needed in a pinch. I guess we could call this an "undocumented feature". It would be good to create a ticket just to make sure it doesn't have an adverse affect on the Stadium hardware. While I doubt it, it would be good to get Line 6's blessing as well as what the power rating is; v2.0 or v3.0. I am going out in a limb due to the latest USB-A to ethernet adapters are v3.0 [UPDATE] USB-A power specs start at a basic 5V at 0.5A (2.5W) for USB 2.0, but increase with newer standards to 5V at 0.9A (4.5W) for USB 3.0 Here's a breakdown by USB version and charging spec: USB 1.x/2.0 (Standard Port): 5V @ 0.5A (2.5W). USB 3.x (Standard Port): 5V @ 0.9A (4.5W). jpd

I was revisiting this thread and tested to see if my experience is consistent. So here is what I have found on my own if I do not change the colors manually after assignment YMMV Test for assumptions about what Line 6 considers the default auto color for several areas of the system; 1) Auto for presets is red 2) Auto for Snapshots is white 3) Auto for a single FX assigned a single footswitch is the default block color 4) Auto for multi-FX assigned to a single footswitch is the color of the first assigned FX block to a specific footswitch using the touch screen. 5) Auto for multi-FX assigned to a single footswitch is the color of the first assigned FX block to a specific footswitch in the app. The interesting this is that when I look at the Stadium unit itself the color of the footswitch is the same as the last assigned FX block in the app. There are times I want to assign a custom color based upon what I call the footswitch or the snapshot. I use a light blue for 12 string and pink for mandolin or dobro. For SAG I assigned multiple FX blocks to one footswitch and after 14 I stopped; not that I would want to do that. I do not know the limit but that has been my test to date. Anyway, for the why of this "auto" color selection you'd have to ask the line 6 engineers. TIAFN jpd

Very cool. Thanks for the reply. My sound person from 2017 created a nice global EQ that I closely matched on the Stadium. I create my patches without it when I use the headphones. I engage it when testing using my FRFR since I can copy and paste the GEQ to the three individual output (1/4" XLR Headphone matrix). It was really effective for the in the room amp sound and cutting through the mix for my patches. I like the way this has been expanded for the Matrix. Good luck with the support ticket! Let us know the outcome once support gives the final piece of information. jpd

Have you sent this to the Line 6 support ticketing system? If not please do. Good catch. The work around is good but not great. jpd

The manual only states it must be formatted using the Helix Stadium process using its maintenance screen. You may want to call support for an exact answer. jpd