›

MIDI control of Mute buttons?

effegeeeffegee
edited September 2013 in Technical details and features
Is it possible to control the individual voice Mute function through MIDI (via NRPN messages)?

Comments

  • julianjulian
    not yet ;)
    at the moment it's mostly sound parameters that are save in a preset that can be automated.
    you could use the voice volume parameter to mute a voice via MIDI
  • effegeeeffegee
    Actually, I've done this for a touch surface mixer layout, but it's not possible to "un-mute" the voice back to the previous volume level. The best I can do is return it to a default value (100, for example). Being able to mute/un-mute would be far superior :)
  • julianjulian
    I see. Should be ready to add in an future update. I put it on the list.
  • effegeeeffegee
    Cool! Thanks a million!
  • effegeeeffegee
    Actually, I should add that I've used an alternate method of muting voices by placing a "dummy plug" in the L2 or R2 1/4" jack and then assigning the "Mute" button on the control surface to redirect the voice to L2/R2. It works, but sacrifices the extra audio out.
  • julianjulian
    edited September 2013
    try http://www.sonic-potions.com/public/MUTE_FIRMWARE.BIN
    rename it to FIRMWARE.BIN and update the LXR.
    you should be able to controll the mute buttons with NRPN 93 to 99
    still a minor bug-LEDs are updated in every mode. even if the mute leds are not visible at the moment.
    will be fixed with the next major firmware update.
    Could you report back if it is working as intended?
  • effegeeeffegee
    It works! Now there's even a mute for the open hat.
    I'm going to update my iPad control surface layout to include true mute buttons and post a link to your v0.24 update. Is that okay?
  • julianjulian
    yeah.I just did not want to make it a major firmware update with just 2 small bug fixes ;)
    will be included in the official firmware over the next days when more fixes are ready.
  • effegeeeffegee
    Julian, there's something wrong here in v0.24. NRPN #94 seems to be connected to the morph amount and #93 connected to the manual roll in the Performance menu. What's odd is that I can see the Morph amount number increase when controlled via MIDI, but I can't hear any change in the sound (i.e., the sound doesn't morph). When I use the LXR pot, then the sound morphs as the value increases. Also, if I change the morph amount via MIDI (NRPN 94), there is no change in sound (morph amount) until I load another kit. Only then can the change in morph amount be heard.
  • julianjulian
    thats what you get for an early morning MIDI hack ;)
    so the mute button NRPN also controll morph and roll?

    Added to my todo list!
  • MöbiusMöbius
    edited December 2013
    I would like to control the mute/unmute status with my DAW for creating build-ups without the need to sit in front of the LXR.
    Using the search function I found this old thread.
    In the change logs Julian added this entry: "NRPNs for track mute added (NRPN 200 to 206)".
    I never used NRPN before, but read a lot in the last two days about it.
    I tried to send this control messages to the LXR:
    CC#99 x
    CC#98 y
    CC#6 z

    But I dont know the values for x,y and z. According to the change log it should be 200-206 for the channels 1-7, I guess. I wonder how to select NRPN number 200 by using x and y.
    Futhermore I wonder about this points:
    What is the threshold for CC#6? Means a value of 0 on or off?
    Do I have to send the individual messages at the some time or is a delay allowed?

    Maybe someone can help me to clear this things up. Thanx!
  • julianjulian
    NRPN's are 14-bit values (0 to 16,384)

    CC98 and 99 select the parameter to change.
    CC6 sets the value for the parameter previously selected by CC99/98.
    Normally your MIDI host should handle the NRPN encoding.
    Doing them manual is cumbersome.

    a midi message has a maximum of 7 bit (0-127)
    so to send a higher value than 127, 2 midi messages are combined (C99 high, C98 low)

    say you want to select NRPN nr 200.
    200 is 00000011001000 in binary 14 bit. (the windows calculator helps ;) )
    now we split it to 7 bit each
    0000001 = 1  = CC99
    1001000 = 72 = CC98

    then you can send the new value via CC6
    I'm not 100% sure, but I think CC6 = '0' and CC6 = 'something else then 0' should set/reset the mutes.

    delay is allowed. You can even select the parameter once wit 98/99 and send various CC6 after that to change the value.

  • rudeogrudeog
    99 and 98 are for specifying the NRPN that you want to modify, and 6 is for specifying the value.
    So its similar to regular CC's except that you are using two bytes to specify WHICH parameter you want to modify and 1 byte for specifying the new value you want to set. It allows you to specify a parameter which is bigger than 127. The tricky part is figuring out the values of 99 and 98 in the case of a parameter with a number bigger than 127.  In the case of these mute parameters, since they are less than 127, you should be able to set them by just setting 99 to 0 and 98 to the parameter you want to modify and 6 to the value you want to set it to. I'm guessing you'll set the value to either 0 or 1. So for example for NRPN 93:
    99=0, 98=93, 6=0 or 1
    For setting a NRPN 200 value:
    99=1, 98=72, 6=0 or 1

    The way you can calculate that is: open your windows calculator, set it to "programmer" mode from the view menu, make sure Dec is selected on the left, and enter in 200. Then click the Bin button on the left. Now take the RIGHT MOST 7 digits and write those down (this is your Least Significant Byte or LSB), take the digits to the left of those and write them (or it) down (this is your Most Significant Byte or MSB). For 200 you get a LSB of 1001000 and MSB of 1. Now, stay in Bin mode and enter each of those in Bin mode followed by switching to Dec mode. You get 1001000=72 and 1=1. CC 99 is where you enter your MSB (which is 1) and CC 98 is where you enter your LSB (which is 72). CC 6 is where you enter your value (a value typically from 0 to 127).
    There are easier ways of calculating NRPN using math but this way demonstrates how the parameters are stored: which is to split it into two 7 bit chunks.
  • rudeogrudeog
    Haha, I guess we were both typing at the same time, or I didn't refresh the thread.
    Yes.. What he said.

  • MöbiusMöbius
    Thank you guys for these nice explanations!
    Normally your MIDI host should handle the NRPN encoding.
    Doing them manual is cumbersome.
    I am using an old Atari ST with Cubase 3.1 for sequencing.
    I don't think the Atari is able to encode NRPN. Just pure controller messages. :-)
    I will definitely try it that way.
  • rudeogrudeog
    Old school! Good for you!
  • fcd72fcd72
    @Möbius
    Yay! Rock Solid Timing is what sequencing is all about…. it doesn't get much better than ST!
  • MöbiusMöbius
    It works! :-bd
    Thanks again!

     
Sign In or Register to comment.