Line 6 Helix Stadium Talk

[Sascha Franck]

Block presets would be great too as long as they’re unlinked from global blocks.

Yeah, and that's where Boss fails so miserably. Because they're pretty much one thing.

---

Here's one possible scenario:

- When saving a patch with global block data, it *must* ask whether you want to keep the global block data or not. Unless...
- Ideally, there should be global block groups, a) for additional sanity, b) to keep the list of available global blocks manageable. In that case patches saved outside of the group would automatically lose all assignments whereas the assignments would be kept inside that group, which I'd actually find to be a decent solution.
- All global blocks should be available from a preset-alike menu. Just that this menu should have zero to do with block presets. In case a group approach is available, the number of global blocks in these lists (which should always only show the global blocks in that very group) should be very manageable. I mean, given my current setups, I have around 7 global blocks in use per gig.

 

[laxu]

I don’t really find the Boss thing too difficult outside the poor labeling in the app. Each block type has 10 “stomp boxes” that can be shared across presets. When you move to a block to edit you can see if it’s a global block or not and if you don’t want it to change others just turn the stompbox preset to Patch Data and go to town. Block presets would be great too as long as they’re unlinked from global blocks. The least complicated way to do this stuff is usually the best IMO. The more options you put into either of these features the more convoluted they become.

Yeah sounds like the Boss way is about as complicated as Fractal's in many ways, just different key issues.

It almost sounds like to do global blocks well, you need some totally separate workflow. Sascha's idea of groups/setlists starts to make more sense to me. It's basically tree structure presets, where the top tier determines simply "these blocks are global for these presets". Something like this:

Global 1: Drive A, Amp A, and Cab A are [global]
   - Preset 1: [Drive] -> Delay -> [Amp] -> [Cab] -> Reverb
   - Preset 2: Comp -> Mod -> [Drive] -> [Amp] -> [Cab] -> Reverb
   - Preset 3: [Drive] -> Pitch -> [Amp] -> [Cab] -> Delay -> Reverb
  
Global 2: Amp B and Cab B are [global]
   - Preset 4: Drive -> Delay -> [Amp] -> [Cab] -> Reverb
   - Preset 5: Comp -> Mod -> [Amp] -> [Cab] -> Delay
   - Preset 6: Pitch -> Mod -> [Amp] -> [Cab] -> Delay -> Reverb

Adjust any global block within those presets and Global 1 or Global 2 blocks get updated.

 

[Sascha Franck]

You're such a fucking hypocrite. You take jabs too, when I had you on ignore. Seriously, go fuck yourself, you miserable asshole. You get into arguments with literally everyone on this board, and yet you think everyone else are the crazy ones. I literally couldn't think less of anyone else on this board.

Same story again.

"Mum, what's that awful noise in the bedroom studio?"
"Don't worry, it's just dad losing temper on the internet yet again."

And fwiw, I'm getting along pretts fine with most people. Even round these parts.
The only persons constantly going for personal insults is you and that british guy.

 

[paisleywookiee]

Same story again.

"Mum, what's that awful noise in the bedroom studio?"
"Don't worry, it's just dad losing temper on the internet yet again."

 

[Whizzinby]

You're such a fucking hypocrite. You take jabs too, when I had you on ignore. Seriously, go fuck yourself, you miserable asshole. You get into arguments with literally everyone on this board, and yet you think everyone else are the crazy ones. I literally couldn't think less of anyone else on this board.

When an unstoppable force meets an immovable object…

 

[ian_dissonance]

I just don’t think it needs to be that complicated. Block presets are a settings you can recall into a preset, if you change it it’s not a preset anymore unless you save it as one. Global blocks are always tied to each other. The biggest thing for me is that it’s easy to know which blocks are global at a glance. I think it’s reasonable to leave the keeping track of which patches use global blocks up to the user.

 

[paisleywookiee]

When an unstoppable force meets an immovable object…

Nonsense. It’s all nonsense.

 

[Orvillain]

Same story again.

"Mum, what's that awful noise in the bedroom studio?"
"Don't worry, it's just dad losing temper on the internet yet again."

And fwiw, I'm getting along pretts fine with most people. Even round these parts.
The only persons constantly going for personal insults is you and that british guy.

I've not engaged with you for months now Sascha. Because frankly, you're just about the most ill informed person I've ever encountered. So we've not even spoken, had any exchanges, or sparred on any topics for months, and you feel like now is the right time to bring me up?? You've just completely proven @paisleywookiee 's point.

You are incredibly stupid and arrogant. I'm not going to bother responding further.

 

[laxu]

Y'all need some sort of "Gladiator arena" thread for shitslinging. Because "Helix Stadium Talk" is not it!

 

[Sascha Franck]

It almost sounds like to do global blocks well, you need some totally separate workflow. Sascha's idea of groups/setlists starts to make more sense to me. It's basically tree structure presets, where the top tier determines simply "these blocks are global for these presets". Something like this:

Dunno, maybe that'd be an idea - but seriously, global blocks and block presets should be two completely different entities and never ever even be close to the same menu structure.

Here's roughly how I could imagine dealing with it.
- Create preset (you could obviously use block presets when doing so, they wouldn't be affected in anyway or play any role down the line...).
- Tell preset to be in a group (copy to setlist, tag it, no idea what'd be ideal, but that's not a big deal).
- Select, say, one amp and tag it to be global (well, within that group...). Not sure whether it needed a naming function (ideally it's show some info automatically). After all, we likely won't end up dealing with tons of global blocks per group. The icon of the amp should reflect the global setting.
- Create another preset.
- From the amp selection menu, there could now be a submenu showing you the amp tagged as global in your first preset. When you select it, it'd instantly work as a global/group block.

And that's pretty much it already. You could at any time select another amp, remove the global tagging, and what not.

---

One somewhat important question would be whether one should be able to completely change the amp model or even a completely different thing for any specific block.
To stay with amps: Let's assume I'd want a Plexi instead of a Bassman - should that change be reflected globally as well or should one of the requirements for a global block be that it'd stay with the very same model?
Or, to take that even further: You could even do wild things in case anything was possible, such as replacing your amp block with a send/return block to use the same group of presets with a real amp.
I could live with either approach, being able to even select anything you'd like and have that change reflected across multiple patches might confuse some folks (even if I'd love the idea myself).

 

[Orvillain]

Y'all need some sort of "Gladiator arena" thread for shitslinging. Because "Helix Stadium Talk" is not it!

You need a sub-forum where you can spit your UI complaints into the void.

 

[Sascha Franck]

Because frankly, you're just about the most ill informed person I've ever encountered.

"Any pitch shifting needs at least one full wave cycle to happen!"

Talk about ill informed. Byebye.

And yes, let's leave it at that.

 

[yek]

 

[Sascha Franck]

I just don’t think it needs to be that complicated. Block presets are a settings you can recall into a preset, if you change it it’s not a preset anymore unless you save it as one. Global blocks are always tied to each other. The biggest thing for me is that it’s easy to know which blocks are global at a glance. I think it’s reasonable to leave the keeping track of which patches use global blocks up to the user.

Personally, I'd be fine with that. But: When you end up with many patches using global blocks across different music projects, that list might become quite cumbersome to deal with.
Also, you could run into a situation where you wouldn't know anymore which global block was safe to be deleted or overwritten.

 

[Orvillain]

All this talk about global blocks is far too premature. Can we have a stable product first???? FFS.

 

[JiveTurkey]

Onboard favorites with a toggle that saves them as global or per preset local. "Problem" solved.

 

[paisleywookiee]

All this talk about global blocks is far too premature. Can we have a stable product first???? FFS.

I'm more concerned about getting the newer amp modeling into more models as well.

 

[[Nathan]]

I dunno how anyone gigs with a quad cortex or any modelling unit without global blocks. This is a total deal breaker and is of the utmost importance

 

[ian_dissonance]

I dunno how anyone gigs with a quad cortex or any modelling unit without global blocks. This is a total deal breaker and is of the utmost importance

I’m not going back to NOT having it if I don’t have to. It’s way too convenient for performance presets.
I just think it’s being way overthought here. It doesn’t need to meet every possible option, especially if it’s going to require six nested menus to make it work properly.

 

[Sascha Franck]

Onboard favorites with a toggle that saves them as global or per preset local. "Problem" solved.

Not a bad idea, still adding too much room for errors.