jpdennis

@littlespaceman Thanks. It does help as it is leading down my path with a few less rabbit holes. :-) The caveat is that i want to also control my mesa JP-2C with MIDI and the Helix with MIDI for the times I want to reproduce the in the mix breakout using multiple EQ for large outside venues and because I'm neurotic. (Oh yea) This may be a case of "having my cake and eating it too" moments. But I love the fun of only being limited by my own imagination. Now if the voices in my head would just settle down ;-) jpd

@littlespaceman You are welcome. I am just glad I no longer have to use a MIDI SysEx application as I did in the Line 6 M13 days. Hahahaha jpd

@littlespaceman I feel your pain as well. The hyper links and youtube videos being within the manual preclude the PDF version is my guess.

@littlespaceman Oh. Thanks for the clarification. I hadn't thought about the song shortening aspect. Well, the only way to test would be to adjust tempo prior to final creation. If you do that please report your finding back. I'd be interested how your click track would respond as well. Thanks again, jpd (just plain dennis)

@RJKole Thanks for the update. I did note that the information @datacommando shared with the link concerning the 3.00 update had issues with DSP with the upgraded poly blocks and compatibility with new presets once you brought in your 2.92 backup. It was an implied, though not well stated, reason many of us rebuilt our patches during the initial 3.00 upgrade. Then 3.01 addressed the bug for the audio corruption based upon certain specific block order. It would be interesting since you say you are back at 2.92 to, remove all current poly blocks then upgrade only to 3.00, follow the procedure as you state you do. After that upgrade to 3.01 and let the firmware do the rebuild which should address the audio corruption following the recommended upgrade procedures as you do. 3.15 talks about the cc remapping that tanked some of us. We learned that hard way that while we could skip firmware updates we had to read all the warnings prior to that and accept the outcome. So I suggest before you do anything, and it is just a suggestion, you read the link @datacommando shared specifically for the warnings with each firmware update starting at 3.00 and determine your best path to get to 3.8x This is just my humble feedback. jpd jpd

@littlespaceman I was using the tempo within the app then ran into an issue with the way a few obscure time signatures might adversely affect the Stadium. I now exclusively use a click track. Also, you can expand the song's end flag to a point based upon the limitation I believe that is mentioned in the on line Stadium manual. jpd

@markolguitar1 As mentioned by @silverhead it's always in the frequencies. While this won't directly be apples to apples I found this video intriguing the other day. And, since I am only limited by my own mind, I am going to see how I can use the Stadium XL multipaths out for hearing how close I can come to this physical concept in the virtual world. jpd

@mdyas Try this link for feature requests https://line6.com/company/contact/productfeedback/ jpd

@littlespaceman You may want to hold off on approaching your wife for a feature request though. <grin>

@littlespaceman Line6 was not going to release the Stadium until it was ready for primetime, so to speak - THEN - a vast majority of Helix users (and probably an accountant or two plus marketing) wanted the Stadium released. Line 6's Eric (digital_igloo) made the announcement that it could be released early but that it would not be 100% where he wanted it to be and asked us all to be patient as the eventual ready for primetime features roll out. My take was that it may be a year for the full ready for primetime goal. Having said that ... Line 6 had been very responsive to firmware patches and enhanced features over the OG Helix's life. I have already seen a few feature requests added while they are still working on and slowly rolling out all the features they have envisioned for the Stadium family. And @silverhead has been making the point that the more people who request a specific feature (collectively) the sooner Line 6 usually investigates if it can be added during one of the stepwise rollouts they have already provided as well as upcoming future ones. Line 6 really does listen and will be responsive to collective squeaky wheel requests. At least that has been my experience for more than 10 to 15 years. jpd

@Holunder4 I do not have the Big Sky so I can't specifically help. However, here is a thread with information I discovered about the way the Stadium now uses and controls via MIDI. Let me and others who read your request know if this is even close to helping you. jpd

@littlespaceman I haven't had the chance to apply this yet. And not to hijack your thread ... I have just been reading about the WIDI dongles and checking to see which works well and which doesn't work well. Which dongle are you using? My goal is to use my iPad and OnSong with my Stadium XL. Thanks for any reply. jpd

@RJKole This may be a dumb question. How did you go from 2.92 to 3.71? I know I had to go up incrementally until I got to one of the early 3.xx version. Also, once I got to 3.01 or 3.11 I would always backup, reset the helix to default, upgrade, restore from backup, allow the helix to update my patches, then proceed to the next update in order following the same procedure. I know at some point there was place you could not bypass incremental firmware updates and a place where you could. I just don't remember. You can search the Helix history to determine the exact firmware version you can bypass. However, my main question is did you go straight from 2.92 to 3.71 or did you do incremental updates and follow the backup-reset to default-restore-allow patches to update procedure? Again, forgive me if you did follow the early update and backup-reset-restore-update procedures. Thanks, jpd EDIT: you can use the link @datacommando provided to read all the firmware update caveats leading to my probably over the top method when I applied the updates.

@Stuntboy298 On my PC I can use the select all feature to save all the presets as a group instead of one at a time. Or did I misunderstand your current situation? jpd

@MojoAxe I made a portable solid sunshade device years ago for my OG Helix. The initial reason was to reduce and overheating issues. Using it with the Stadium requires me to set the brightness and brightness timeout. I haven't had a lot of outside high daylight venues since getting the Stadium so far. For the one during a late afternoon it was passable. It was not optimal. jpd