BrianHV

Q: How do I prevent the patch from advancing multiple times per switch press?

I'm using Mainstage 2.1.3 with a Roland RD-300SX. I have an FS-5U foot switch that I'd like to use to advance patches plugged into the Roland's control switch port. Regardless of what I've set the Roland to send for that port, it sends one or two messages with a value less than 127 before sending the value of 127. This causes Mainstage to advance 2 or 3 patches each time I press the switch.

 

I saw that recent release notes said that this didn't happen for the sustain pedal now. Indeed, it does not. However, I need the sustain pedal to sustain.

 

Is there any way to get Mainstage to only advance one patch in this situation? Perhaps set a threshold value for the action?

MainStage, Mac OS X (10.7.1)

Posted on Nov 29, 2011 12:57 PM

Close

Q: How do I prevent the patch from advancing multiple times per switch press?

  • All replies
  • Helpful answers

Page 1 Next
  • by BrianHV,

    BrianHV BrianHV Nov 29, 2011 1:52 PM in response to BrianHV
    Level 1 (0 points)
    Nov 29, 2011 1:52 PM in response to BrianHV

    I've found a partial workaround. It involves setting the pedal to type "Press/Release" in layout mode, then for each patch mapping it to "Current Patch" and setting the max and min values to the next patch. It's tedious and still only behaves properly about 80% of the time. It still sometimes advances two patches with one press. Still looking for a real solution.

  • by BrianHV,

    BrianHV BrianHV Dec 1, 2011 12:40 PM in response to BrianHV
    Level 1 (0 points)
    Dec 1, 2011 12:40 PM in response to BrianHV

    I've improved my workaround.

    • Unlike my suggestion in the previous message, the pedal should be of type "Absolute" in layout mode, not press/release.
    • In edit mode, map the pedal to the "Current Patch" action. Set the "Button Off" parameter to the current patch and set the "Button On" parameter to the next patch.
    • Click the "Parameter" box to bring up the parameter curve. Edit the curve so that input values 0-126 are at the bottom, and input value 127 is at the top. It should look like a very steep line at the right side of the window.

     

    Would still love a less tedious solution.

  • by Blueberry,

    Blueberry Blueberry Dec 3, 2011 9:12 AM in response to BrianHV
    Level 4 (2,944 points)
    Dec 3, 2011 9:12 AM in response to BrianHV

    Your "improvement" seems about right:

     

    • In Layout mode the controller should be assigned to whatever it acutally sends. Your pedal sends an absolute value, so "Absolute" is correct.
    • "Current Patch" is a way to switch to a specific patch. If you just want to switch to the next patch, why don't you simply use the "Next Patch" action?
    • Because you want the same behavior in all patches, the mapping should be made at concert level. You can always override in specific patches and/or sets, if you don't want it in all cases.
    • The graph is a good way to filter values you don't want. But it might not be necessary - try it out.
  • by BrianHV,

    BrianHV BrianHV Dec 3, 2011 9:19 AM in response to Blueberry
    Level 1 (0 points)
    Dec 3, 2011 9:19 AM in response to Blueberry

    Thanks for the response.

     

    • I can't use "Next Patch" because it triggers multiple times with one press of the footswitch. Were it not for that issue, this whole thing would be much easier.
    • If I were using "Next Patch," it could go at the concert level. But since I have to use "Current Patch" for the aforementioned reason, I need to configure it manually for each patch.
    • The graph is necessary; if I don't use it, even "Current Patch" behaves poorly. And unfortunately, the graph isn't available for the "Next Patch" action.
  • by Blueberry,

    Blueberry Blueberry Dec 3, 2011 9:22 AM in response to BrianHV
    Level 4 (2,944 points)
    Dec 3, 2011 9:22 AM in response to BrianHV

    Can't you fix the "multiple times" with a graph that triggers only once e.g. at 127.

  • by BrianHV,

    BrianHV BrianHV Dec 3, 2011 9:26 AM in response to Blueberry
    Level 1 (0 points)
    Dec 3, 2011 9:26 AM in response to Blueberry

    That's effectively what I'm doing with the "Current Patch" graph. (Though technically it still takes action at values 0-126, the action is to change to the patch I'm already on.)

     

    When I choose "Next Patch" as the action, the "Parameter" button with the graph is greyed out and unclickable. Am I missing a way to get to it anyway?

  • by Daanvm,

    Daanvm Daanvm Jun 11, 2012 4:03 PM in response to BrianHV
    Level 1 (0 points)
    Jun 11, 2012 4:03 PM in response to BrianHV

    Hi Brian,

     

    It's been a while since your last post in this thread. Did you find a better solution? I'm having the same problem with my Roland RD-700GX. Mapping the foot switch for each patch is not an option because when I change the order of patches, things get realy messed up.

     

    Thanks,

    Daan

  • by BrianHV,

    BrianHV BrianHV Jun 11, 2012 4:36 PM in response to Daanvm
    Level 1 (0 points)
    Jun 11, 2012 4:36 PM in response to Daanvm

    I haven't had occasion to try again, so no, I haven't found a better solution.

     

    I just looked at the release notes for Mainstage 2.2, and they say "It is now possible to block unwanted incoming controller messages." I haven't tried 2.2 yet, but that looks promising. If you could block the messages on the control channel in question with values less than 127, that ought to solve the problem.

  • by Daanvm,

    Daanvm Daanvm Jun 11, 2012 10:13 PM in response to BrianHV
    Level 1 (0 points)
    Jun 11, 2012 10:13 PM in response to BrianHV

    That sounds like the solution I am looking for. Thank you! I'm currently using MainStage 2.1, so I think it's time for me to upgrade.

  • by BrianHV,

    BrianHV BrianHV Jun 12, 2012 1:09 PM in response to Daanvm
    Level 1 (0 points)
    Jun 12, 2012 1:09 PM in response to Daanvm

    Lest I get your hopes too high, I downloaded 2.2 as well but couldn't find a way to block those messages. I've posted a followup at How do I block unwanted incoming controller messages?

  • by Daanvm,

    Daanvm Daanvm Jun 13, 2012 12:34 AM in response to BrianHV
    Level 1 (0 points)
    Jun 13, 2012 12:34 AM in response to BrianHV

    Ok, thank you. Maybe I'll download 2.2 anyway. There are other nice features and it seems that 2.1 isn't stable anymore since the last update of OSX Lion.

  • by jimthe2,

    jimthe2 jimthe2 Aug 3, 2012 4:05 AM in response to BrianHV
    Level 1 (0 points)
    Aug 3, 2012 4:05 AM in response to BrianHV

    I've had this problem - bad polarity on the pedal was my demon.

    I have found a very stable configuratio.

    On my 88 note midi-master keyboard, the lowest note has been assigned to step back one patch, and the next black note, to advance one patch.

    This works just fine, and these are notes I never use - just be careful if you do big "sweeps" of the keyboard to STOP before these last two notes.

     

    Sort of "off" subject.

    Mainsatge 2.2.1 and OS 10.7.4 are unstable.

    Deleting the "CPU/Ram" meter has been suggested as a fix, or shell out for MS 2.2.2

    Or, apparently OS 10.8 fixes the stability problem.

     

    Good luck

  • by Bobby Simons,

    Bobby Simons Bobby Simons Aug 3, 2012 5:05 AM in response to jimthe2
    Level 1 (30 points)
    Aug 3, 2012 5:05 AM in response to jimthe2

    I do exactly the same with the bottom A and Bb keys, it's great. I also have two buttons on my Edirol PCR800 assigned to the same function, but find I nearly always use the keys. (Remember to assign at the Concert level.)

  • by A11egro,

    A11egro A11egro Nov 15, 2013 3:44 AM in response to BrianHV
    Level 1 (0 points)
    Nov 15, 2013 3:44 AM in response to BrianHV

    I changed pedal from 'Absolute' to 'press/release', and put program change up to 127.  This fixed it for me, hope it helps!

Page 1 Next