Jump to content

jdomine

Moderator
  • Posts

    8
  • Joined

  • Last visited

About jdomine

jdomine's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare

Recent Badges

1

Reputation

  1. I am able to reproduce this and have logged a bug for it. It seems to go all the way back to 3.00.0 if not further. It does not seem to happen if you use EXP1 for the ext amp control and EXP2 for expression. For now I would recommend using this configuration as a workaround.
  2. If you could email the problematic preset to me at jdomine@line6.com or attach it here I'd like to test this out.
  3. Thanks guys. I can reproduce this using the attached presets and have logged it as a bug. Appreciate your report!
  4. This is indeed a bug. I have logged it for review by the team. Thank you for the report!
  5. This sounds like your DAW is sending MDI CC 68 to the Helix to activate the tuner. Try changing the midi channel in the global settings on the Helix. You can also use a midi message monitor to see if you daw is sending CC 68.
  6. If you unplug the USB cable after it has become unresponsive does that snap it back into functioning?
  7. Is your keyboard sending out MIDI clock or any other MIDI data constantly when powered on? Simply having something plugged in via MIDI din should not matter but I could see flooding the MIDI stream with clock and other things could theoretically cause an issue.
  8. I am able to reproduce this easily. I noticed that if I deleted the looper block at the end of path 2B the problem goes away. Do you use that looper at all? If not I recommend deleting it from the preset until the bug is fixed. The bug seems to be that if you load a preset with a looper on a B path after coming from another preset with a looper on a B path audio stops passing.
×
×
  • Create New...