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

sotipay

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by sotipay

  1. My Helix controls an H9. I want one switch to change the H9 to preset 1, another switch to change to preset 2, and if neither is on, I'd like EITHER (1) the H9 to be bypassed or preferably (2) the Helix effects loop that the H9 is IN to be bypassed.

     

    Maybe this is because I don't understand MIDI very well, but I know I could just have the Helix's loop permanently on and send the BYPASS command to the H9, but I don't see how to have a single switch send multiple MIDI commands (namely, the PC command to change to [e.g.] preset 1, the command to UN-bypass the H9, and [upon turning the switch to the off position] the command to bypass the H9).

     

    Alternatively, if I could just get two different Helix switches to turn the Helix effects loop on/off (that is, 2 switches controlling the same exact effect in the signal chain), then I'd be set. But I don't think the Helix can do that.

     

    I'd love some help with this!

     

    nope, not possible at the moment to assign on/off status of a block to multiple switches. so you may have to do wih one switch turning on the loop as well as send a PC message to the H9 and another switch to change to another preset on the H9. Hopefully, future updates will eliminate the need to do it this way

  2. Line 6 has already laid out how the updates are gonna be. First they get the editor out, squash some bugs with user's help, update the editor, squash some more bugs then release the official release version of the editor. After that, then we get the fun stuff. All we need to do is be patient guys, that's it. If you have requests, Ideascale is there so make use of it

  3. I suppose it depends what you define as a "scene".Certainly the ability to assign the blocks within a patch set to either "on" or "off" to one footswitch, with other of patterns of blocks on and off assigned to other footswitches, would be a huge step forward.What would be truly great is if you could also amend all the parameters within each block and save that as scenes within the patch - however I will accept the first option as a start :-)

    First option you stated is all that's needed. Since you can already assign parameter changes to footswithches then all that's left is to allow the assignment of the off/on state of a block to multiple switches and you've essentially got "scenes"

  4. Only the existence of the perfect multifx device will stop users (and non-users too from what i gather from forums like this) from complaining and/or asking for stuff. Since the perfect multifx has never been achieved yet, and will never be achieved IMO, then discussions like this will continue on and on. Even the almighty and revered Axe Fx has its share of critics/complaints too bout patch change latency from what I have read in the Fractal forums. So carry on guys, discuss away.. Good thing is Line 6 actually encourages customers to speak up. Doesn't guarantee that you'll get what you want though..

  5. Line 6 can certainly do optimizations on the code, increasing patch changing times by a few ms. But from what i understand there will always be a slight gap that you will hear. True seamless preset switching would be impossible on the current implementation unless 1) They limit patch creation on 1 DSP and use 2nd DSP only as a sort of preset loading buffer, or 2) Come up with some sort of external DSP box that you can plug in to the helix to do the same thing (no idea if this is even possible). Now, the question is what patch change gap would be tolerable?

×
×
  • Create New...