jpdennis

Je télécharge uniquement avec Chrome. Edge me pose problème. J'espère que cela vous sera utile. Veuillez m'excuser si ce n'est pas le cas pour vous. Veuillez excuser ma traduction française.

letterond, I only use Chrome for my downloading. Edge has been problematic. Hope this will be of help and forgive me if it doesn't help where you are. jpd

tufanderince, As I stated earlier, I do understand your frustration. I know that Line 6 is preparing to have PROXY in the coming update which I am hoping is released by mid March at the latest. Your other ideas are great. If you haven't already sent these ideas as feature request to line 6 support, I'd say please do. I have to say the idea of an onboard DAW seems interesting. Not sure how the multiple channels would work but the Matrix feature and Showcase may have some interaction. Only Line 6 can say what the current hardware is capable with respect to future firmware upgrades, as it was suggested during the prelaunch they are working on many things with the Stadium family, of which some have not been revealed yet. On a side note. and knowing this isn't what your vision is for a hardware upgrade with respect to the iPhone hardware use case idea you are speaking of, I have yet to connect via Bluetooth using my iPhone for any interactive capability for the Stadium. Having said that, the concept of the current iPhone connectivity opens up my thoughts to investigate at a later date what the Stadium can or cannot do at this time. In closing, I use this forum for conversation as well as sometimes reading with no feedback to open my mind to the possibilities of what others are doing, dreaming of, and issues solving with old fashion know-how & creative thought. 90% of my use for this Stadium is playing. The device just allows me to channel my Hendrix side. <AWAAN> Play & Party On! jpd

Fazly, To start this conversation, I haven't had to check the state of snapshot control for my EXPs, they just work but I do have auto assign engaged for several things in global settings. You will want to make sure the EXPs are allowed to be controlled by snapshots; I assume nothing so forgive me if this is already within your wheelhouse. What I normally do is have the vol assigned to one EXP (for my example I will say EXP2) and then the "state of a block parameter" assigned to another EXP pedal (for my example I will say EXP1). I will have EXP1 on (engaged) for the snapshot I want to control a parameter for (in this example the "amp drive"). All the other snapshots will have the EXP1 off (disengaged) and EXP2 on for vol. The other option is not to have a vol block and just assign one EXP pedal to the amp drive control EXP is on in the one snapshot and off in the rest. I do this for several of my presets based upon the snapshot setting I am controlling. But like putting on my shoes, there are several alternatives to my use case. YMMV jpd

goviline6, It is the "norm" from what I have experienced. Any change triggers the "you've made a change so do you need to save it" alert by either italics or e. I treat it like the Microsoft "are you sure" pop-up. It is a nice built-in for those you don't know if they want to exit or not from the Windoze app or OS. Personally, I made a mistake back in 1992 with DOS OS and I now know if I want to save or not or exit or not. Normally with the Helix family, I do a final save on a specific snapshot for each preset as my "initial" start when triggering a specific preset when at a performance venue so I won't be saving at the venue unless it is a leveling issue during sound check anyway. However, when creating and testing I always double check myself and what setting change or preset or snapshot within a preset I want to trigger a final save. At first it was a little annoying but after some time I learned to just accept it. It has saved me a couple of times so ... jpd

bverdon, This would happen even in my OG Helix Floor if I switch snapshots while playing, used the expression pedal by switching or adjusting the % of incline, as well as turning on and off blocks with the footswitches. The app as well as the Stadium will see that as a change of some sort. The app will just see it a few moments after the change. jpd

nobod999, Thanks. Nice to know there is a work-around at this time. jpd

brydo, I haven't had this issue "yet". And I am not saying this doesn't have to be addressed at some point in command center. When you use your finger to touch the problem footswitch, assuming you've left the footswitch themselves assigned to press and touch, does a menu popup on the Stadium XL itself and allow you to unassign it? jpd

tmlambert, It would be annoying if that was the case with respect to your chorus, EQ, and the two compressors. I use snapshots and for the FX blocks that I do not want touched by snapshots I make sure they are not controlled by the snapshot which is a per FX block setting. That way they stay at the same settings from snapshot to snapshot. As I get more comfortable with Showcase I am anticipating using fewer snapshots and preset linking. I have yet to hit the snapshot control limit silverhead has spoken of. I am only slightly concerned by that how it could affect DSP usage and preset stability since I have way more control than I had with the Helix Floor. jpd

I understand the OP's disappointment if a finished product was expected by the OP. However, Line 6 is deploying more as they can via current and soon to come updates. They are addressing the bugs slightly faster, which I can say due to the expeditious way I have been contacted by Line 6 support during the recent four tickets I created. I know that they are being careful to not address too many bugs without testing what is broken in the process of final release of updates. And I have read that Proxy is being demonstrated at NAMM, though I am not physically at NAMM. The Stadium XL is usable for what I need right now and has made headway with the updates. My memory may be bad, however, I believe they are committed to delivering updates in a tighter timeline than when the Helix Floor and Rack was first released. I may search when I have some time. jpd

Anyone know if this is just for demonstration at NAMM and will be in the next release?

All, my "SIDENOTE" issue is a known bug and I was informed by Line 6 support they are aware it. It will be addressed in a future update. jpd

GAJ52, Thank you so much for sharing your trial and error findings. I am finally getting some new stems created. I am hoping to have my first polished tracks ready. Please let us know if your backing tracks have sound over the next few days as you use/turn off/turn on and use again. If not, and if mine stop working over the next week or less, we will both need to create a new trouble ticket with Line 6 since I know more users have been waiting for this update to fix the "no sound" on backing tracks issue. jpd

Has anyone with the no sound issue checked the signal level bars by turning on the global eq, even without adjusting it, to see if there is a signal coming through at that point then check the Matrix levels. Upon applying the 1.2.1.xxx update I did have a couple of interesting issues. This may not directly apply here but I thought I would share that my Matrix levels were not quite right. A few of the matrix levels had been zeroed. When I first used the Stadium XL with the 1.2.1.xxx I had no sound and thought I broke something. I even made sure my guitar vol pots were set right and using my other amps and modelers to check. Not sure why I went straight to the Matrix levels at that point to check though when I was checking the global eq I did note that I saw the signal levels working fine even with no sound coming into my playback devices. jpd

theElevators, I agree that the Stadium will not be for every guitarist. I know from experience that modelers may not be the choice for every guitarist as well. While I wasn't part of the "I want it now and will deal with the bugs" crowd that requested early release, I did order it as soon as the early ordering was available. What I am interested in is the modeling improvements with the Agoura models. And, once Showcase is fully implemented and rock solid the best use case I see is the ability to have a "rig engineer in a box" so to speak. For me this opens up the "one man band" concept with reduced footswitch dancing as well as stage lighting controls. My Helix Floor was perfect for everything but the foot switch dance for complex songs and/or cover songs that require the "band leader wants the exact sound for the songs" demands. I am very interested in the Showcase feature as well as deep diving into the latest update that did fix several of the issues. [SIDEBAR] We had the helicopter sound rear its ugly head in the OG Helix as well back in 2017. And I did a search finding hits concerning DSP stress tests on the Stadium XL creating strange sounds. However, for my OG Helix, as well as the Stadium XL, I usually kept to presets that did not push the limit of the DSP capability; and I would create a "goto" footswitch within presets on the OG Helix if I needed to link presets for a very details song. That will be another test of the Showcase feature for me. Though, I may not be a typical user. <YMMV> jpd

gbr13697, Oh, got it. My fingers a little big as well. I now understand what you mean. Thanks for the clarification. jpd

gbr13697, Line 6 says, if all things are equal, to do exactly what you did. Of course I first log into the app and DO NOT connect to my Stadium via Wi-Fi or usb. I have disabled the auto-connection feature because of the issues I have read a few users are having. What I do every time I use the Stadium Desktop App in normal day to day use, before closing the desktop app, is I disconnect from the Stadium XL then log off the app then close the app. So again, when an update is ready, I log into the Stadium Desktop app without connecting to the Stadium XL and update via the prompt I see when the app launches. I update the app on the computer first. Once done I reboot my computer. While it is rebooting I then make sure my Stadium is turned off. I then turn it on, make sure I logged into the Stadium with a good Wi-Fi connection. There will be a red circle in the upper left. I use the hamburger menu to go to the download section and follow the prompt to update the Stadium firmware. [Now at this point I may be overthinking it but my process has never failed me so far] After the Stadium comes back on line I check to see if I need to reconnect to my Wi-Fi SSID and put in the password just incase I need to; I was taught to trust but verify. I then check to see if I am logged into the Stadium and if not I log into the Stadium XL. After that I launch the Stadium app on my computer, check to see if I am logged in still because the stadium desktop app update usually shuts down the app with me still logged in during the update process. I will log out then log back in. Next I connect and make sure the Stadium queues up for the final connection process and all is well for me. I then disconnect the Stadium from the app, log off the app and close the app. I will work only off the Stadium at this point to check to see if any of the blocks look strange in focus view; which is how I discovered the issue with the Parametric EQ block for the few presets I used it in. jpd [SIDE NOTE] Because I do not know how Line 6 fixed the code for the Global EQ and the fact that the Parametric EQ FX block is similar if not the same, I can only speculate the Global EQ fix also affected the Parametric EQ block and may have not been caught in final testing to let us know to have to reset the FX block if necessary. Again, I may just be full of it here. I have created a service ticket for this to see if it is something they should know about.

bbehrens, Are you saying you have the Stadium connected to your system via usb-c at the same time you are connecting via wi-fi? Thanks for any clarification. jpd

gbr13697, Could you post a picture of what you are seeing? Thanks jpd

I updated the desktop app just by launching the 1.2.0 app. After that I updated the Stadium itself. The update went smoothly. I did have to check the level settings for the headphones, XLR, and 1/4 to make sure they were at the correct level. I had a backup of my system so I decided to restore after doing a default setting reset. As Line 6 stated the global EQ does not come back after the update nor does a restore from the previous version 1.2 set of backups bring it back to my previous settings. So I deleted all my previous backups and created a new one. Resetting to the default settings and restoring from my new backup did bring back the global settings I had just recreated. I do have to reenter my SSID password each time I restore or reset to default but no big deal at this point. The great news for me is that I can go in and make all the setting changes I want with respect to snapshots without having to save each time I change a single snapshot. I made many parameter changes to the amp, FX blocks on & off & on, path level adjustments, output adjustments, etc. for all my 8 snapshots using a "one size fits all" preset I have. I then saved it just once after switching to the initial snapshot I want it to start with AND all my parameter & block state changes for each and every snapshot had been saved as I wanted them to be. This is huge for me! Great job there. I did note the stereo parametric EQ doesn't work as expected with the restore of existing presets. However, I created a Parametric EQ test preset and it works as expected. I have seen this with the Floor Helix before. I also noticed several of my FX blocks in several of my complex presets need to be fine tuned with this latest update. And after reading what the Line 6 engineers fixed I am OK going through all my presets and making any and all adjustments to the blocks. And I've created favorites of my main FX blocks so hopefully this won't be an issue with the next updates. The Stadium Device connects a little cleaner when I open the Stadium App. I do not set it to connect automatically. Anyway, those are my findings and reactions for now. jpd

Thank you for the reminder. I did forget about that!

I really enjoy using the Helix family. Over the 10 years I used the Helix Floor, Line 6 came through with feature updates they hadn't thought about that the user forum engaged in discussing then feature enhancements that would work with the hardware and software that where submitted to the developers for review. The enhancements that many users requested using the feedback to developer links had priority over the requests that one or two user only requests. So, the users of this forum would make sure everyone would submit the request to the correct link since Line 6 doesn't monitor this forum for the purpose of identifying fixes and enhancements, as a norm. Software/firmware bugs where addressed as well as more modeling amps, cabs, and effects added to the device. So, now that I am using and learning about the Helix Stadium XL, as I did with the Floor, I am very satisfied with it and know from past experience the Yamaha/Line6 support engineers will get it working as it has been presented or go many sleepless nights to get it working as expected. I am sure we will have even more modeled devices added. For me, I am looking forward to the coming years with the Stadium and hope I can learn to use it to its fullest. jpd

cacibi, I did notice the 32GB limitation. I found some information concerning having a SD Card reader to attach to my computer for the purpose of copying the folder/file structure of the 32GB to another SD Card. I am awaiting delivery of different size SD Cards and a reader just for this testing purpose. So, don't take this as fact until I can report back. I've set this post to be followed by me. Once I get the parts AND have some time I can report back though it may be a few weeks as I have some new studies and some darn home & motorcycle repairs to deal with. Glad I have the life to have a life! ;-) jpd

JakeHodges, You are welcome. This workaround came from my 10 years working with the Helix Floor. I am not sure if there is some DSP issue based upon fx block placement as well as the "at what point" I placed the block in the path that was never resolved. I could not exactly replicate the issue when I needed to. But when it does happen that is my solution. Maybe others can chime in and add what they have done in this case. just plain dennis (no one important) ;-)

gbr13697, Funny story, I have setup many customer facing public wi-fi subnets for hotels, casino, etc. It was quite a balancing act in regards to traffic shaping. And thus my build of a secondary mesh wi-fi at home. Thanks for the memory! Enjoy the Stadium and play on! jpd