Jump to content

FantomXR

Members
  • Posts

    1,035
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by FantomXR

  1. Banks are working. But when changing a bank while pressing keys (playing a sound), the sound stucks because the note-offs now will be send on the new channel. 

    Also I don't want to work with banks because I made some scripts that allows to set splitzones which is not compatible with banks as far as I can see. My idea is, to select the different channels of the various splitzones. But I have no plan, how to get that running...

  2. 1 hour ago, Zam said:

    You can put ^val in MAP definition IIRC

    I tried this:

    MAP1/BYTEI  0:0  ^val:1:64  127:127

    without success. I also tried downslash ^val_1 and ^val1. The terminal says:

    [2944380.039] [MBNG_FILE_C:7] ERROR: invalid map value '^val_1' in MAP1/BYTEI, expecting 0..255 (0x00..ff)

    Same with HWORD btw.

  3. 6 minutes ago, macsaif said:

    1. It is mentioned that the driver is optimized for LPC17 can it be used also for STM32F4 with the same scanning freq?

    yes. STM32F4 is able to do everything the LPC17 can do and due to more RAM even more. Anyway: If you decide to go with LPC, I have some spare PCBs here which I don't need anymore.

    6 minutes ago, macsaif said:

    2. What is the difference btw. MidiBox NG and KB? Is it just firmware loaded to chip?

    NG is able to do everything and KB is optimized for keyboard-usage only (like I mentioned before: higher scanning speed => better velocity resolution). You can compare both apps by reading through this:
    http://ucapps.de/midibox_ng.html
    http://ucapps.de/midibox_ng_manual_ngc.html

    And this:
    http://ucapps.de/midibox_kb.html

  4. Hey people,

    I have a question regarding maps. I like the implementation of the interpolation techniques when using maps.
    Let's assume we have a keyboard with a map:

    MAP1/BYTEI  0:0  64:64  127:127

    This gives us a linear velocity curve. What I now want to ask: Is it possible to convert those numbers to variables f.e. like this:

    MAP1/BYTEI  0:0  AINSER:1:64  127:127

    This would allow to easily adjust the velocity curve of a keybed... make it more convex or concave regarding which sound you are playing. By adding a fourth value into that line one could adjust the velocity curve even more accurate. Also something like this:

    MAP1/BYTEI  AINSER:1:0  AINSER:2:64  AINSER:3:127

    will give you even more control. You could change the whole velocity curve with just three potentiometers very quick and easy. 

    Any ideas how to do that?

    Thanks,
    Chris

  5. 49 minutes ago, macsaif said:

    Is it possible to program Midibox to provide the mentioned operations (module 2)?

    Yes. This should work. Anyway: I recommend to start with the buttons and try to program them the way you need it. 

    I'd also recommend to go with the latest core which is the STM32F4-core. 

  6. 1 hour ago, macsaif said:

    The other question: is it possible to configure the KB module to switch between velocity on and off mode based on some digital input to the module? If not I can do it simple way...by shortening of 2 rows scanning the first and second contact of the key by relays. I have tried it with the existing master keyboard and it works. For 61 key I need 4 and for the 73 key I need 5 relays with double contacts.

    The KB-app is not able to do that. This is a general setting which (as far as I know) you can not assign to a controller. 

    I'm not sure what the status is regarding octave shift / transpose. As far as I know this is not possible at the moment. But you will have to double check with @TK..

  7. 18 hours ago, macsaif said:

    Is it possible to make this application by Midibox?

    yes

    18 hours ago, macsaif said:

    Which core do you recommend to use?

    STM32F4 as this is the newest.

    18 hours ago, macsaif said:

    Which modules (configuration) I have to use?

    DIO for the keybeds & buttons & LEDs, AINSER64 for all analog controllers, MIDI I/O.

    But have in mind, that the more digital I/Os you connect to the core, the slower the scanrate of the keybed (= less velocity resolution) will get which doesn't matter if you are playing in organ mode most of the time.

    And another thing: Good luck with the 73key TP/8O. This one doesn't have ribbon cable but foil cable. I was not able to get it working. 

  8. Alright... I tried it! But without any changes. I get the following velocity values only:

    1, 8, 18, 28, 39, 49, 59, 69, 79, 89, 100, 110, 120, 127

    As you see there is kind of "logic" behind that... but I think you go with me if I say that 14 steps out of 127 is not that much ;)

    Here is my test configuration:

    RESET_HW
    
    KEYBOARD n=1   rows=12  dout_sr1=1  dout_sr2=2  din_sr1=1  din_sr2=2 \
                   din_inverted=0  break_inverted=0  din_key_offset=32 \
                   make_debounced=1 \
                   scan_velocity=1  scan_optimized=0  note_offset=28 \
                   delay_fastest=50  delay_fastest_black_keys=0  delay_slowest=200
    
    EVENT_KB id=1  type=NoteOn chn=1 key=any use_key_number=1 range=0:127
    
    SRIO num_sr=2

     

    //edit: Alright, I set scan_optimized=1 and I get a lot more velocities! Great! Are there any other ways to speed up the scanrate or is that going to deep? ;) 

    Thanks already for that!

×
×
  • Create New...