phil_m

Is POD Go Edit the only Line 6 software you have open?

It sounds simple on the surface, but there are a lot of “edge cases”, so to speak, that would need to be accounted for, and there isn’t necessarily a straightforward way to deal with them. What if, for example, someone has a patch where they use multiple cabs, and in some snapshots one is on and one is off? If you bypass them all via a global setting, ok that’s one thing, but what happens when you change that global setting to have them come back on? It would have to somehow account for getting blocks back in the proper state. And this is just one example of something that would have to be dealt with. I think it’s these sort of things that are the reason there isn’t a simple cab on/off global setting.

No. That’s a global setting, so it’s not available to be assigned to a controller.

Well, the issue is there isn’t anything like a simple “cab section”. There are cab blocks, dual cab blocks, and then there are amp/cab blocks that contain cab modeling. And you can have multiple cab blocks in a preset, so you very quickly run into all sorts of complexities when you start trying to disable them globally somehow. Then beyond that, there’s also the IR blocks, which replace cab blocks, and it wouldn’t be unheard of for people to use the cab blocks in some presets and IRs for others... Basically, Line 6 decided to offer more flexibility as far as the signal chain goes in individual presets versus having a lot of global functions that affect every preset.

As I mentioned above, no, the G10TII should give you pretty close to the advertised 7 hours of life. Anything much shorter than that is a defect.

Yes, mine receivers have been updated to 1.01 for over a year now. I’d also add that the box is explicit that people should except 7 hours with the compatible receiver products.

I’m charging my new G10TII in my original G10S receivers. Listen, there’s still going to be failures now and then, as with anything that uses a battery, but I’m certain that under normal conditions, people should be getting much closer to the 7 hours listed on the box (and is actually printed on the box). Line 6 hasn’t been perfect, but they aren’t completely stupid.

I realized I missed that part where you mentioned that and deleted my reply in between the time you replied again.

It works mostly in Stomp Mode, but there are also capacitive touch features available in Snapshot Mode.

I’m not sure if it could make a difference or not, but have you tried a different Cat5 cable between the Control and the Rack?

There is a feature called Pedal Edit Mode on the Helix/HX products, but it doesn’t exist on the Stomp, so I suspect you might mean something else. When you press a footswitch that’s assigned to an effect, that block will become active. So it sounds like perhaps you’re in Edit View and when you hit the footswitch, that block is becoming active. It should be toggling the bypass state of the block as well, though. If you want to see the block graphics, you need to hit the Home button to switch to Play View. You can navigate to Stomp Mode by thing the Page < or > buttons.

You perform the factory reset by holding down FS2 & FS3 while powering up, not powering down. Simply do that, and you’ll get the factory presets back.

Using a compressor to squash peaky transients is probably OK, but I don’t know that I’d depend on it to even out the differences between acoustic and electric signals. I think you be better off sending separate outputs from the Helix to the board for your electric and acoustic, as most sound guys would want to EQ and mix these differently.

I misunderstood what you were saying then. There’s no way to have the BPM set to “per preset” and have the tempo be remembered after changing it when you leave and come back to a preset without re-saving the preset.

You need to set the BPM setting under Global Settings to Global in order for it to work like you’re describing.

Workbench HD works on Big Sur. The legacy Workbench does not since it’s a 32-bit application.

You do realize that HX Edit has been compatible with Big Sur ever since the 3.10 release now, right? It’s only Native that’s still having issues, at least as far as the Helix line goes.

Generally not. You can set up an aggregate device in the Mac so the input and outputs are different, but that will give you additional latency. When you plug the POD Go into your Mac via USB, it becomes your audio interface, meaning it acts as your input and output device. So you'd want to connect your monitors to your POD Go to hear the audio from it and from GarageBand or whatever other DAW you want to use.

I guess I’m still not clear on what you’re expecting to hear and where you’re expecting to hear it from. The POD Go will stream audio to the Mac, but you won’t hear audio coming from the Mac’s speakers or headphone out if that’s what you’re expecting.

First thing - paragraphs are your friend... Yes, the models are the same. They are both using the HX models. The only “but” is there fact there are a few models that are not included because of how much DSP they use - the King of Tone, RE-201 Space Echo, the Polyphonic Pitch models, and the Clawthorne Drive bass fuzz, to be exact. The other “but” is that with the 3.10 update, increased oversampling was added to the Helix. So some of the models run at high sampling rates in the Helix compared to the POD Go... So how much of a difference this makes is probably up for debate. There are also differences in the way mono and stereo effects are handled in the POD Go versus the Helix. The Helix has mono and stereo versions of most effects. The POD Go has mono or stereo versions of all effects depending on what type they are - all drives effects, filters, pitch and dynamic effects are mono. All delays, modulations and reverbs are stereo, basically.

How are you monitoring the POD Go?

The workaround is using an external pedal as the volume pedal and/or keeping the POD Go out of direct sunlight.

Workbench HD works fine on my Mac Mini M1 with Big Sur.

Apple certainly doesn't make it easy for anyone... I just bought a Mac mini because I liked the machine, but I kind of think the whole concept of updating the OS every year is just ridiculous on the surface of it. Why does anyone actually need that? It's mainly driven by Apple's desire to keep selling new hardware. The fact that they're talking about the next version of MacOS before there are tons of bugs with the current ones (like the fact that my Magic Keyboard loses Bluetooth connectivity so often with Big Sur that I gave up trying) is stupid. My wife has a MacBook Pro, and we both have iPads and iPhones, so we've certainly given Apple plenty of money over the years. I just find them infuriating sometimes.

What operating system are you running? The UI being laggy is a known issue with Big Sur that should be corrected soon, but I can’t say I’ve heard of it on other systems.