Leaderboard

please check to see if you have it set (global settings) to automatically assign the block to a footswitch. If this is set to manual, then adding a wah or volume will not work correctly until you make their assignments manually. easiest fix is to delete them, turn on the automatic add and add them again. Hope that helps.

The one area I'm finding lacking so far is Preset management. In the OG Helix I had a setlist for each band and could easily offload or reload sets by band as necessary. My current method in Helix Stadium is that I group all User Presets by band, batch color them by band as well, and alphabetize within band groups. Then I can easily just save one band's presets to my PC to make room to load another band's presets if need be. I play and sub in a lot of projects and also lots of one-off shows, and make a preset per song so that the Helix is also my setlist, so they can build up fast. To that end, 3 things I think could vastly improve management. 1. Folders within the User Presets. Then I could have a folder per band. 2. since set lists are just "aliases" pointing to a user preset, being able to rename ONLY the alias would be super helpful. That way if I have 10 songs that just use my "Marshall Plexi" preset, I can rename them for each song while also have them all just pointing to the same preset. As it is now, I just have to have 10 redundant copies of the same preset if I want them to be named for 10 different songs. 3. If I save presets from the setlist to my PC, it only saves 0K "alias" and not the actual preset, which I can't see why I would ever want to do. It seems like it should save the actual preset to my PC. There very well may be better solutions as well, this is just what I've thought of while figuring out my workflow.

PaulTBaker You were correct, the setting was set to manual for Assign FX to stomps. Maybe this should be the default :) I also determined that if you copy a block from a working one it also works. Hopefully this will help someone else. thanks everyone!

Hi everyone, I’ve been exploring the DL4 MkII and its MIDI capabilities, and I had a feature idea I’d love to discuss. The pedal already handles MIDI Clock really well for delay, and it has a very creative looper. My thought is: what if the looper could also sync to incoming MIDI Clock? This could allow: Loop start and end to be quantized to incoming clock Loop length aligned to bars or beats Possibly a simple “loop sync” option in Global Settings I know the DL4’s looper is designed as a free-time tool, and the pedal is mainly a delay device, but since it already receives and sends MIDI, enabling this as an optional mode could really expand its potential, especially for live setups with multiple devices or synchronized loopers. Has anyone else thought about this? Do you think it’s technically feasible with the current DL4 hardware? Looking forward to your thoughts and ideas!

Silverhead, thanks a lot for your explanation, and you're right, I'm going to write this request, following your link.

I’m a bit confused. You’ve posted this in the Helix Stadium sub-forum but you are talking about the DL4 MkII product. I have moved this topic to the proper sub-forum.

That's not what I said, I mean , you can send for example Stereo Guitar -> XLR L&R outputs / Backing tracks L&R-> Jack L&R outputs / Click -> Send 1 Output Then send all to the mixer which have Aux outputs I presume. Each Bandmember have his/her own aux dedicated and can make his own mix with what is connected to the mixer. With the mixer you can simply have the click in the Aux Outputs and put the volume to 0 to frontstage (excuse my english)

Hello everyone, many thanks for your comments. I powered on the Stadium this morning and the issue is now gone. When I was testing yesterday, it was directly after the firmware 1.2.0 update had finished installing. I assume that an additional restart was required and missing, which caused the issue. Now everything is working as expected. :) Yesterday, it didn’t matter whether I gave the presets a custom name or just used the default “New Preset”. It also made no difference whether I saved the preset via the app or directly on the hardware. Thanks a lot! :) Ben

Agreed with you all. I am still trying to figure out how the preset management is better now in the Stadium over the Helix. I assume that it would have something to do with Showcase and saving songs. But for now, it is just confusing to me. But what I DO understand is that I have half of the preset storage capacity on the Stadium as opposed to the Helix. I know that I might be able to use multiple SD cards. And 512 presets is still more than enough for any particular show. Still, I found myself swapping out Set lists on the Helix pretty regularly for Preset Development, Play-Along Set Lists, Sunday Set Setlists, Christmas, Top 100 songs, Bass Guitar Set lists, recording, etc. But this only allowed me to at least always have a backup of a set list that I needed to offload in order to create a new one or bring another one in. Remember, we could have 8 Setlists of 128 songs! So far, I have had to reset my Stadium back to Factory several times due to buggy issues and that has only made preset management MORE problematic trying NOT to lose presets that I had created so far (which is not very many yet, either. Remember to ALWAYS SAVE (like the early days of Windows!)

I think we’re going to see improvements in how setlists are implemented in a future firmware update (but I have no basis for that expectation; purely speculation). The idea of using aliases with a single copy of a USER preset is a good one, imho, but the current implementation is a bit confusing to me. Like you, I also see no point in having a setlist file on my computer that has nothing but aliases. I also don’t understand the frequent appearance of a numbered suffix. e.g. (1) behind a USER preset’s name when importing setlists.

I submitted all this to the product feedback. My set lists are per band as well. So I see what you're saying but I don't see it being a problem at least for my personal scenario. Especially as I won't be using showcase at all. the SD card thing just seems like a lot of hoops to jump through. I'm currently still of the opinion that the old Helix way of doing things was actually better, but I'm trying to adapt to the new way to make sure it's not just a case of "familiarity" vs. "new." It used to be so simple and easy to just swap in/out setlists which also included the presets.

One option is to maintain separate microSD cards for different purposes (e.g. bands). Swapping presets in and out of the USER area can become problematic with setlists and Showcase. It’s possible to end up with incompatible versions of USER presets, Setlists, and Song data in the device. For instance, suppose you swap out USER presets named, for convenience here, A and B. If a setlist contains an alias to preset A and/or B it seems that setlist is now incompatible with the USER preset area. Also, if a Song contains flags that refer to preset A and/orB the Song data is also incompatible. Stadium system data including USER presets, setlists, and Songs form a tightly integrated dataset. Creating and restoring backups using different microSD cards maintains data integrity. Another thought that I haven’t experimented with so I’m speaking theoretically here…. What about using Songs and Playlists instead of setlists? I know you can create an Empty Song in Stadium using the app. Presumably you could add a flag at the Start of each Song that loads the desired USER preset. That way you could use different Song names in a Playlist without being forced into USER preset redundancy as you described above using setlists. The Songs would have no audio; they would just be used for preset management. Again, purely theoretical. I like your idea of renaming setlist elements while retaining the alias to the underlying USER preset’s name. Have you submitted this as a feature request?

I spent a lot of time going through the settings the Tone War guy suggested for all the metal amps and got those where they sounded great. I came across this by accident looking for different blocks to try...At the very end of your final chain get a stereo model of the Bass DI (located in the Dist section) put the Bass and Treb at 4-5 and the level to suit, this will give your preset a full rich low end def and sparkle presence no EQ or Comp can do. Try it you will be adding it to your presets asap. I have no idea what it was intended for but man it fixes the punch and feel of the real amp that is missing.

Hey. I am attempting to sync tempo/delay to my DL4 MkII using Reason 12.7 running on a MacBook with Sonoma 14.2.1 with Nektar's T4 keyboard being used as the MIDI interface. It worked about a week ago, but has since stopped syncing tempo/delay functions. All other MIDI data transmits to the DL4, so I'm confused why I can't sync the delay settings to the MIDI out tempo. I recently purchased the DL4 so it has the latest firmware. My MIDI cable is brand new. I've reset to factory settings on both the T4 and the DL4. Any help would be appreciated. ~steve

...or a church using volunteers for running sound in which case they may adjust overall levels for channels, but not EQ'ing. Probably better they don't touch the EQ anyway.