FantomXR

Did you ask your local ROLAND-service? ;-) I'll visit them the next days... I'll ask them kindly ;)

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

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.

I guess you don't have any further informations about the keybed itself? What I did on a yamaha keybed some time ago is using jumper cables to check out where which BK / MK / row is. But in that case the local yamaha support was kind enough to send me the schematic of the keybed... so in the end it was not that hard...

Ha! Tricky..... ;-)

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..

Please do me a favor and read through the ucapps site. It's all there ;-) In short: You can not use the KB-app because it doesn't support AINSER64 and the connection / configuration of buttons & LEDs.

Yes. That should work. Have in mind that you need resistors for the LEDs and diodes for the switches. Also you can not use the KB-app which is made for high speed velocity scanning.

yes STM32F4 as this is the newest. 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.

Alright! Great! I'll check that out in detail and will let you know how it worked out! thanks again!

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!

Hey TK, thanks for that detail! That sounds good! I'll try that now! What does "Page" mean? How many DOUTs will be supported if I set this to 1?

No, not really. I want to send a text message from my DAW to the MIDIbox. ;)

Sure. But this is way not enough.

Hey people, some of you already know that I'm very interested in getting the keyboard-handling as smooth as possible. Some of you also know too that the higher scanrate of the KB-app allows a much higher velocity-resolution than in NG. NG is very limited in this case and only allows a few (like 10-20) velocity-values. What I'm trying to achieve is, to modify NG in that way that the scanrate of the digital I/Os respective the I/Os where the keyboard is connected to is higher to get a better velocity resolution. The reason for that is, that NG allows a much easier way to modify the keyboard parameters and also due to the SD-card it's very easy to make a backup of your configuration. I had it now a few times, that (for whatever reason) MB_KB was reset. So I took a closer look at the source code of what is going on under the hood in NG. As far as I can see the Period-Scanning is in both apps NG and KB 1ms. I'd like to know what blocks NG to give the digital I/O scanning a higher scanrate. Are there any other routines running in background that I can simply disable if I don't need them? I'll do some test the next days but if anyone can give some hints on this, I'd be happy to read them! ;-) Thank you very much! Best, Chris

Hey people, I have another question on this... I don't have any displays here to test... so I thought asking may be faster ;-) Is it possible to send pure text to the displays without converting them into hex first? If yes, how would this be done? Thanks! Chris

I don't talk about range. I talk about NRPN number and referring to the NG manual this should go up to 16383...

I have another bug report. It's about the NRPNs. As far as I understand a NRPN contains at least three different CCs: CC#98 = NRPN number CC#99 = NRPN "bank" CC#6 = NRPN value So if I set nrpn=20, it sends CC#98 20, CC#99 0 and CC#6 depending on the value of the controller. If I go over 127, CC#99 changes to 1 and CC#98 counts again from 0. That makes totally sense. But! If I go over 256, CC#99 stays at 1 and doesn't count up to 2. Or do I overlook something?

SmashTV aka AVI ShowTech... just google it and you'll find it. You can also send me a PM and tell me which PCBs you need. I maybe can help you. I'm from Berlin, Germany.

I just noticed, that the cable that goes from PA2 to PA3 is equipped with a 220Ohm resistor. I do not use a buffer. So the only differences we have are the applications and the 1k pullup to 5V. I don't have the tools to build this small setup here. But I'll try to test as soon as possible.

There is only one cable that connects both cores. This goes from PA2 to PA3. It's about 10cm. But I didn't use a pullup. Just a straight connection. I will try with using the pullup (as the MIDI standard dictates ;-) ). Maybe it's a problem with combining different apps... we should check with TK.

This is what I meant ;-) Alright... here is my result: I made a direct connection between two cores like @Zam suggested. PA2 to PA3. One core runs MB_KB, the second core runs MB_NG. The connection is in one direction only: Out from KB to in of NG. No optocoupler used here. I opened the mios32_config.h like @TK. suggested and added the lines. I compiled different versions like Zam with 312k, 625k, 1000k. Of course the applications in my test run the same baudrates. First test was with 312.5k. Didn't test yet under heavy circumstances. Just tested if notes come through. They do... works good for now. Than I went over to 625k. Here it stopped working. When pressing my keys, the NG receives random pitchbends and program changes. Also the console says: [765645.838] [MIOS32_MIDI_Receive_Handler] Timeout on port 0x20 Than I tried to modify both applications and add a buffer of 255. But this didn't change anything. I didn't test another baudrate yet because if this is not working I don't think that higher rates will work. So for now my conclusion is: 10x speed seems to work fine. Above that it get's unstable in my environment.

BTW: this setting has just effect on the MIDI ports right? The USB-speed is not affected by that, correct? (every ms counts :-) )

Thanks for checking that! I'll do a test with 20x speed and will check if everything works at my side! I'll report later today. @Zam: Thorsten wrote some posts above, that 10x speed means 1ms... so if you are at 20x it should be about 0,5ms.

Yes. That's what I meant. Simple example: LED ring 1 CC1 bank = 1 LED ring 2 CC2 bank = 2 if my software now sends both values for CC1 and CC2 only the selected bank gets updated. The unselected bank doesnt. If I switch to the unselected bank it shows the old value. If I than turn the controller in my software, the LED ring jumps to this value.