Please ensure Javascript is enabled for purposes of website accessibility Jump to content

BenFM84

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Location
    Berlin, Germany

BenFM84's Achievements

Rookie

Rookie (2/14)

  • Reacting Well Rare
  • First Post Rare
  • Conversation Starter Rare
  • One Year In
  • Week One Done

Recent Badges

2

Reputation

  1. Hello everyone, I’m having the same issue here. Rebuilding the preset from scratch didn’t fix it. I’m sharing the text of my support ticket below and will update this thread once I hear back from Line 6. Hopefully it helps others who are running into the same problem. Best Ben --- I believe I have encountered a reproducible snapshot recall bug on my Helix Stadium. Here is the setup: I created the preset from scratch using firmware 1.2.1. Within the preset I use multiple delays and reverbs, including the CrissCross Delay block. Snapshot Control is enabled for all CrissCross Delay parameters mentioned below. Snapshot: “Dist | PM” • Feedback A: 60% • Feedback B: 70% • Mix: 45% Snapshot: “Dist | Rth” • Feedback A: 30% • Feedback B: 40% • Mix: 25% Expected behavior: Each snapshot should recall and retain its own parameter values. Actual behavior: I first set up “Dist | PM”, then “Dist | Rth” — everything works correctly. When switching from “Dist | Rth” to “Dist | PM” and then back to “Dist | Rth”: • The CrissCross Delay parameters in “Dist | Rth” are overwritten with the values from “Dist | PM”. On the hardware screen, “Dist | Rth” now shows the wrong (PM) values. On the macOS editor app, I still see the original correct values for “Dist | Rth”. However, the audible result clearly follows the values shown on the hardware — not the app. So it seems the device state is overriding the snapshot data, while the editor still displays the stored snapshot values. I have not been able to resolve this by re-saving or rebuilding the preset. Since it was created from scratch on the current firmware, it doesn’t appear to be a legacy preset issue. Please let me know if you would like a video, preset file, or step-by-step reproduction recording — I can provide one.
  2. In case anyone reads this later: I contacted Line 6 support. Updating to firmware 1.2.1 did not resolve the issue. Support suggested rebuilding the affected preset from scratch. After doing so, everything is working again.
  3. Hi everyone, I’m experiencing a strange issue with my Stadium and hope someone can help. Problem: In one specific preset, I’m unable to delete Stomp assignments in the Command Center. The option is greyed out and cannot be selected. In all other presets, everything works as expected. Background / What I did: I use the expression pedal as a volume pedal. For this, I enabled “Auto-Assign Blocks to Stomps.” After placing all required blocks in the signal path, I switched this option back to manual (my preferred workflow). Now I want to free up the stomps to assign Snapshots instead. The issue: I can’t remove individual stomp assignments The option is greyed out Even choosing “Clear All Assignments” does nothing In other presets, I can assign and remove blocks normally I’ve attached a video demonstrating the behavior. Questions: Has anyone encountered this before? Could this be a bug or am I missing a setting? Is there a way to fix this preset without rebuilding it from scratch? I haven’t opened a support ticket yet – wanted to ask here first. Thanks in advance for any help! :) Screen Recording 2026-01-14 at 22.41.01.mp4
  4. 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
  5. Hi everyone, got my Stadium today and I’m running into a strange issue with it and I’m hoping someone here has an idea. Problem: Presets do not save correctly. Any blocks I add are lost after switching presets. What happens step by step: I create a new preset and add two blocks. I save it as a new preset. Immediately after saving, the preset is empty and the blocks are gone. I then add the same two blocks again. I save the preset. I switch to a different preset and then back. The blocks are gone again – the preset is empty. So basically, no matter how often I add blocks and save, the preset never retains them once I change presets. I used a Helix Floor before and I’m generally familiar with the workflow. I’ve attached a screen capture showing my exact workflow. At this point I feel like I’m missing something obvious, but I can’t figure out what. The Firmware is updated to 1.2.0. Any ideas or hints would be greatly appreciated. Thanks in advance! Ben Screen Recording 2026-01-05 at 22.05.01.mp4
×
×
  • Create New...