H90: recreating slow/fast switch in midi

Home Forums Products Stompboxes H90: recreating slow/fast switch in midi

Viewing 7 reply threads
  • Author
    Posts
    • #190626
      MirageIndigo
      Participant

        What a good way to recreate the “perform” switch from the H9 using midi?  Historically on the H9 I did this using a #CC8 -127 message that was sent from a button press on my controller on Press. Then I’d press again and it would send it again.  Assigning it to the perform switch in the H9 seemed to do the trick. It had the useful function of also doing freeze on some of the Delay

        How can I get the fast/slow switch on the Rotary on the H90 over MIDI? 

        It seems I could do something similar with hot switches but I’m not sure if that means i need to set my own slow/fast rates and it wouldn’t seem to “just work” for other perform switch behavior and whatnot.  There doesn’t seem to be a direct conceptual mapping between the H9 perform switch and the H90 hot switches (which seem to be about teleporting a preset to a specific setting snapshot state).  I am using the editor, so I don’t need the explanation of the mechanics of configuring MIDI, I am asking what h90 setting I’m even supposed to be fiddling with.

         

         

      • #190628
        joecozzi
        Moderator
        Eventide Staff

          How can I get the fast/slow switch on the Rotary on the H90 over

          Say, for example, the Rotary algorithm is on the preset A slot, get into PERFORM mode and press the A LED button above the footswtich to assign the BRAKE/SPEED control to the switch; it’s the 8th option. Then, press & hold that LED button to enter the Performance Parameter Mapping. Under “Ctl Source” select MIDI CC and assign the CC# you’d like to use to engage the BRAKE/SPEED. Don’t forget to save your Program.

          It seems I could do something similar with hot switches but I’m not sure if that means i need to set my own slow/fast rates and it wouldn’t seem to “just work” for other perform switch behavior and whatnot.

          The instructions above allow to make assignments on a Program basis. However, there is a way to make assignments globally which is similar to how there is one “performance switch (middle)” assignment on the H9, except on the H90 you have six!

          If you go into the System Menu > MIDI > MIDI-Global Ctl you can use the first quick knob to scroll through assignable parameters. There are six that correspond to the PERFORM mode parameter mappings across all programs. They are titled PERFORM 1, PERFORM 2,…PERFORM 6. You can assign each a CC#. Then all you have to do is make sure the performance parameters for each one of your programs is mapped to things you want to control, like the BRAKE/SPEED on the Rotary presets. But the bottom line, once you’ve mapped these PERFORM parameters globally, you can access them with your MIDI controller across all programs.

          Here’s a video explaining these concepts: https://youtu.be/5y14LwN9oAk?t=856

        • #190629
          brock
          Participant

            [Edit: Too slow for Joe]

            … I am asking what h90 setting I’m even supposed to be fiddling with.

            If I am understanding correctly, you would need to use Global Mapping to emulate how the H9 addresses the [PSW] mappings.

            The H9 had to combine the ‘3rd switch’ functions of the TimeFactor, ModFactor & PitchFactor with the unique-to-Space hotswitch function, all while accommodating both types of controls in the newer H9 Special algorithms.

            It’s more versatile in the H90, splitting up the functionality.  You can map to each Performance switch individually.  The 3 HotSwitches can each cover any combination of base parameters in any of the algorithms now.  And each of those momentary or latched HotSwitches can also be mapped to a controller individually.

            HotSwitches are saved at the Program level, and Performance switches at the Preset level.  You can either map each type consistently to a particular slot in every Program / Preset, or map that slot to a control globally across any Program / Preset.

          • #190720
            MirageIndigo
            Participant

              Thanks for everyone’s help.  To follow up: I got it working by mapping the Preset (A in my case) to Hotswitch 5 to the function I wanted to twiddle (Slow/fast/brake).  Then separately mapping Hotswitch 5 to a midi CC (#21 in my case).

              Note that I appear to be able to map hotswitches 1 and 4 to Program, 2 and 5 to Slot A, and Hot Switches 3 and 6 to slot B.  In my case, I almost always have a modulation or Fancy pants delay in Slot A, so I’m fine with this limitation.  It’d be ice to be able to map just “Preset MyFooModulator always maps onto Hotswitch X” but I can see why this would also be problematic when combining presets without a control mapping strategy.

               

              From there, the magic for fast/slow/stop appears to be that a single CC #21 – Value 0 toggles the state between Fast and Slow. A single CC #21 – Value 127 activates the brake.  This relationship also holds on most of the modulation algos. I’m stil workign on my morningstar controller to try to get the right toggle behavior, sometimes my slow/fast labels end up out of sync with the H90. I might need to simplify.

              For Delays, the perform setting I am interested in is the Repeat, which appears to be similar CC# – Value 0 turns it Off, CC#21 – value 127 turns it On.

               

              With the hotswitch mappings, the behavior I’m getting is I’m able to override the MIDI using the actual footswitch assuming I’m on the correct page of the hotswitches (which is accessible by tapping the perform knob live).

            • #190721
              MirageIndigo
              Participant

                And right now I’m doing this per program. But that’s fine because I only have like 9 programs so far.

              • #190722
                brock
                Participant

                  … For Delays, the perform setting I am interested in is the Repeat, which appears to be similar CC# – Value 0 turns it Off, CC#21 – value 127 turns it On …

                  Maybe this has changed in the H90 (I’ll have to check).  The delay algorithms from the TimeFactor reacted differently in the past [value 127 for ON and a following value 127 for OFF].

                  Performance/hot switch activation by midi

                • #190724
                  MirageIndigo
                  Participant

                    Ah I think you’re right!  I had misinterpreted why the change was happening.  I am using an MC3 and I have the CC#21 – value:0 on Release and CC#21 – value:127 on a Long Hold.  The repeat is engaging on the Long Hold, so the 127 doing the toggle state is consistent with that.

                    I’m rewatching the Morningstar Toggle switch videos to remind myself how to get the toggle state to stay in sync.  I figured this out on my H9s such that I could keep everything in sync, but then forgot how to do it in the the last 3 years. I have the HS1,2,3 still set to bypass for P,A,B so I can hit a switch to kill the thing.

                    Other than Repeat and Slow/Fast/Brake what other goodies are out there beyond the basics?

                     

                     

                  • #190726
                    brock
                    Participant

                      … I am using an MC3 and I have the CC#21 – value:0 on Release and CC#21 – value:127 on a Long Hold. The repeat is engaging on the Long Hold, so the 127 doing the toggle state is consistent with that…

                      Yeah, you have to be careful those Long Press / Long Release commands on the Mornigstars to avoid some puzzling results.  My long-term suggestion is to establish some kind of generalized template for the H90 MIDI CCs.  There’s a huge number of controls that can be MIDI-mapped, and they can all be saved ‘underneath’ a Program (whether or not they’re in active use inside that Program).  Then you can source that H90 map from purpose-built MCx templates for specific applications or H90 algorithms.

                      Most of the H90 MIDI CC Implementation is fairly consistent [v64-127=ON; v0-63=OFF].  You’ve run into one exception with REPEAT, but [v64-127=ON] also logically applies to parameters like TAP.  With momentary functions, [v64-127=ON] on Press, and [v0-63=OFF] on Release.

                      Other than Repeat and Slow/Fast/Brake what other goodies are out there beyond the basics?

                      Oh, now you’ve opened up Pandora’s Box.  At least a few Performance options in every algorithm.  The ‘lowly’ Retrigger can be mapped to the same CC in two mod effects, for synchronizing LFOs.  Extra pages for Looper transport controls.  The newer Harmonizer algos [Polyphony, PolyFlex, Prism Shift] and PolySynth have FREEZE & pitch shifting toggles to explore.  The newest Harmonizer+ have the deepest toolkits of Performance parameters.

                      My more recent PatchStorage uploads have become overloaded with MIDI mappings, so I can point you to an example.  The MIDI Implementation is buried under the comments, as is a direct download to a modified sample of that Program.

                      Guitar-Peggios To Scale

                  Viewing 7 reply threads
                  • You must be logged in to reply to this topic.