Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,206

  • Joined

 Content Type 

Posts posted by TK.

  2. Change Main Encoder Function

    in MIDIbox SID

    Posted

    I can't access the files, could you please attach them to this posting?

    On 21.1.2020 at 0:33 PM, imaginarion said:

    Which function is responsible for switching to the menu where i can assign functions to 5 potentiometers ?

    I guess you mean CS_MENU_BUTTON_Knob

    Best Regards, Thorsten.

  4. Sender and if_equal

    in MIDIbox NG

    Posted

    It should work now -> http://www.ucapps.de/mios32/midibox_ng_v1_037_pre13.zip

    Reason was, that I "compacted" the storage for conditions so that it fits into a 32bit value. But meanwhile we've so many different event types, that I had to spend another bit for the hw_id of the condition.

    As a quick solution I sacrificed two bits from the condition value, and gave it to the id
    Which means: currently it's not possible to check for values >12bit anymore, but the ENC event type should be found as expected

    Best Regards, Thorsten.

  16. Save and recall sysex strings

    in MIDIbox NG

    Posted

    I think that this could be somehow solved by using ^dump in combination with sysex_pos for individual dummy events which collect the characters - the characters then have to be print out conditionally, e.g. based on another dummy event which stores the selected channel.

    Best Regards, Thorsten.

  17. Save and recall sysex strings

    in MIDIbox NG

    Posted

    Hi Chris,

    you could just define multiple EVENT_RECEIVERs, listening to incoming SysEx, matching on certain bytes which indicate which channel is addressed, and then store the value into ^val

    E.g.: 

    EVENT_RECEIVER id=  1  type=SysEx  stream="0xf0 0x11 0x22 0x33 0x00 ^val"
EVENT_RECEIVER id=  2  type=SysEx  stream="0xf0 0x11 0x22 0x33 0x01 ^val"
EVENT_RECEIVER id=  3  type=SysEx  stream="0xf0 0x11 0x22 0x33 0x02 ^val"
EVENT_RECEIVER id=  4  type=SysEx  stream="0xf0 0x11 0x22 0x33 0x03 ^val"

    In a NGR script you can access the received values with (id)RECEIVER:1 ... (id)RECEIVER:4

    Which means for your NGR script: if you switch to another channel, just take the corresponding value from the receiver and display it.

    Best Regards, Thorsten.

  18. Can encoders send NRPN values with inc/dec?

    in MIDIbox NG

    Posted

    There is a trick which might help here: a SysEx stream can also send "common" events, which means: we can just put all CCs into a single String.

    Example: 

    EVENT_ENC id=1   hw_id=1    label="@(2:1:1)Attk "   enc_mode=Inc01_Dec7F  if_equal=0x01  type=SysEx stream="0xbb 99 0 98 23 96 1"
EVENT_ENC id=1   hw_id=1    label="@(2:1:1)Attk "   enc_mode=Inc01_Dec7F  if_equal=0x7f  type=SysEx stream="0xbb 99 0 98 23 97 127"

    Best Regards, Thorsten.

  19. Can encoders send NRPN values with inc/dec?

    in MIDIbox NG

    Posted

    An example setup for this use case can be found here: https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/conev_1.ngc 

    # send CC#96 if value is incremented
EVENT_ENC  id=2000  hw_id=2000  enc_mode=Inc01_Dec7F  if_equal=0x01  type=CC cc=96 lcd_pos=1:1:2 label="Enc INC"

# send CC#97 if value is decremented
EVENT_ENC  id=2001  hw_id=2000  enc_mode=Inc01_Dec7F  if_equal=0x7f  type=CC cc=97 lcd_pos=1:1:2 label="Enc DEC"

    Best Regards, Thorsten.

  22. "No free token memory"

    in MIDIbox NG

    Posted

    Hi,

    linking this information with your proposal for "bulk operations", and it makes sense ;-)

    Would "combined" set_active help to reduce the number of commands, or are there other commands which are repeating a lot?

    Best Regards, Thorsten,

     

     

  25. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    @sis.tm concerning MacOS update: I will observe this - once I got more indicators what could go wrong there, I will try to safeguard the upload. There are already some measures (e.g. checksums and handshakes), but it seems that this isn't enough.
    Otherwise: sometimes patience is a virtue - hopefully Apple will fix this.

    Concerning CV modules: just tested at my side. No ground hum, and no noticeable noice. Only if I extremely amplify the audio signal in my DAW, I can notice some digital noise (at an ignorable -80 dB level) which disappears if I disconnect CV and Gate, but definitely no hum.
    The system: MBSEQ is connected via a externally powered USB Hub to a MacMini 2012, a "Kraftzwerk" is connected to the CV interface, and Audio is connected to a Firestudio Mobile.

    Best Regards, Thorsten.

×
×
  • Create New...