cchimi

Yup

Yes. Helix was essentially a guitar pedal. "Guitar pedal" is only part of what Stadium is or can be. I suspect there are many more musicians who take requests, or who select songs in real time rather than follow a strict setlist than Line6 realizes right now. I think as more people start to use Showcase this will become evident. After all, the type of player who takes requests - singer/songwriters, duos, nursing home performers - form a natural market for a feature such as Showcase. Stadium is much more than a guitar pedal, even though most of the marketing focus has been in that direction.

No problem. This Showcase Song model is very new and we're all feeling our way through it.

Actually, why would you have to change any of the MIDI programming on the Stadium? There would be no reason at all, because the selection calls would be made from an external device. In fact, doing it that way you only need one Song list on the Stadium and one on the calling device. It's not that complicated.

Yes, of course we need PCs for Presets. And that's exactly why we also need PCs for Songs. Songs is such a new concept I suspect many people aren't seeing this yet. At the moment, assuming the Stadium is on the floor and you don't want to have to constantly bend down and press the screen several times, you cannot select a Song at random. You can only scroll through them one by one by pressing a footswitch multiple times, NEXT or PREV. That's going to be a big problem for a lot of people once they experience that. But, I should say, if you work from an ordered, predefined setlist, or if you work so that your fingers can easily touch the screen, you will likely never experience this problem and might not even see it as a problem.

At the moment, I don't think it's possible to use an Instant command to load a SPECIFIC Song. It can only load the NEXT or PREV song. If you have an ordered setlist, this might work for you. But if you have to choose songs at random, as some of us do, it won't work. Also, note that while you can be in the Preset view and play a Song, it will not be a Song that is in anyway associated with that Preset, except by accident. The Preset list and the Song list are, at present, independent of each other. One way to look at this is Songs select Presets (because Songs have ways of selecting Presets as needed on the timeline), but Presets do not select Songs (except NEXT and PREV). I hope that changes soon and we can select Songs using MIDI commands, and I hope this is helpful.

I don't think I was disrespectful, but opinions differ. I certainly didn't mean to be disrespectful. I just want a Stadium that works for me and was explaining why MIDI Selection of Songs is critical and I was surprised it wasn't included when Showcase was released. Honestly, I think it's something that people will only understand as it affects them. Thank you for the feedback link. I'll make that request.

I use OnSong on an iPad to call up songs at random as I need them. Each song in OnSong sends the appropriate Program Changes to our devices. This doesn't work at present on the Stadium because Showcase Songs are not currently selectable via MIDI. I think Line6 hasn't yet seen now important this will be for many of their users.

I posted about exactly this issue on the Facebook group and, frankly, got a ton of crap about it. It was upsetting, since I was just asking a question. I suspect that most people at this point don't really understand how Songs are different from Presets as containers on Stadium. Most people, because of prior experience on other devices, associate songs with presets. A Preset contains a Song, more or less. That's one reason we have snapshots, so that we can alter guitar sounds as needed as we play a song. On the Stadium, Songs contain Presets. It's actually a much better way to work, but I think - based on the reaction to my post - that many people can't see that yet. But as soon as they build a fairly large number of Songs within Showcase, they will see it. And, soon as they have to press a footswitch 25 times at a gig to go from Song 2 to Song 27, they will understand why Songs in Showcase must have MIDI Program Change numbers so they can be called at random, as needed. People who work from predefined setlists, and people who can easily access the song list on Stadium with their fingers, will never have to deal with this. But if you work with requests, if you pull up songs in response to the feel of the audience in the moment, Showcase - as it stands right now - is pretty well unusable. Only because there's no way (short of bending down and pressing a few buttons) to select a song at random from your list. I believe Eric Klein and his crew are aware of this, but he can't say when MIDI Song selection might come to the Stadium. He says Showcase was designed to be a standalone system not needing input from other devices (that's paraphrased). To me, one interesting thing about thinking of Showcase as a standalone system is, if that's true, why do Presets even need to have Program Changes associated with them? Any preset you want can easily be called up within a Song in Showcase. I think it's possible Line6 just didn't quite see the importance of being able to select Songs at random and decided to release Showcase without that capability. In my opinion, that was a mistake, but it's likely they don't see it that way because there's a belief that few people will need it. Since most users at this point are still wrapping their heads around what Showcase can do, there's very little insight into how this is already a problem for some of us, so our concerns tend to get dismissed, or our writing styles critiqued. But I think this is going to be a bigger problem than it might seem right now, as more people become familiar with Showcase and how Songs work. Hopefully, Line6 will see that and add this capability as quickly as possible.

You guys really helped. I knew the options were there, because I've had the pedal for a while, but haven't used it in a couple of years. Thanks a lot. Things are now working as I want them to. (By the way, I have RTFM, but not for a while. I thought I knew how to do both things I mentioned, but had a brain fart coming back to this pedal.) Thanks again, Carl

1. Can I turn off the touch sensitivity of the footswitches? I'm constantly touching them accidentally as I'm making other adjustments. I looked for this in the settings, but I don't see it. 2. The two leftmost footswitches, with the up and down arrows, can be used to switch presets, banks, or snapshots, IIRC. I'd like to set them up in Command Center to control other devices using MIDI. I can set the MIDI messages but those switches are still changing my presets. Is it possible to stop those footswitches from switching presets, banks, or snapshots such that they only send the assigned MIDI messages? Any help would be appreciated. Carl

Sorry, I haven't done this since I wrote the original post. I went off in another direction. If I have time tomorrow I'll look into it and see if I can remember. I do remember that Native was so slow and caused so many problems that we went another way with trying to automate my guitar patches, using the guitar effects built into Studio One. Carl

Thanks, cvmiller39. I'm convinced it's the POD GO WIRELESS, not the UHost. The UHost works to send MIDI to every other device I've tried it with. Admittedly, that list is not exhaustive, but it's enough to make me think there is something in the POD GO WIRELESS that doesn't like MIDI signals coming from the UHost.

Thanks. I suspect the problem is with the Pod Go Wireless, though.

I'm confused. What is it about the Pod Go Wireless that the manual says it can accept MIDI commands for setlist changes, patch changes, and some other changes by Control Changes, but I can only get it to work using OnSong on my iPad Air? I'd rather use a pedal, such as the MorningstarFX MC3, MC6MKII, or MC8. I'd rather have the control at my feet, not at my fingers. I've got an MC3 hooked up to the Pod Go Wireless right now. It's going through a CME WIDI UHost to mate the USB ports on the two pedals together. This same setup works great for other devices I have for changing patches, etc. Why not the Pod Go Wireless? I can see that data are being send from the UHost to the Pod Go, but the Pod Go makes no response at all. Yet it works using OnSong through a USB C to USB B cable. What is going on? It's clearly something about the Pod Go, something not mentioned anywhere in the manual that I can find. I've read the other thread here that is roughly on this topic, but it doesn't answer the question I have. What is it specifically about the Pod Go Wireless that means it doesn't respond to MIDI messages from an MC3 (or similar pedal) and Uhost (or similar device)? And,,why is it not mentioned in the manual or advertising so you can know in advance it won't work? Or - does it work, and I'm just doing something wrong? Thanks for any input on this, Carl