MIDI DESIGNER
The only MIDI controller for iPad, iPhone, and Mac


Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Check out our Facebook Group.

Of course, if you want to send us an email, feel free.

Open problem reports

Summary of user requests
Layout for Roland JD Xi - MIDI Designer Q&A

Layout for Roland JD Xi

+1 vote
asked Sep 4, 2016 in Community Requests by korakios (150 points)
regarding your very last question about batch replacements, that's not currently possible in MIDI Designer. However, we can do it directly in code for your layout when you are ready. Just sent an email to Support with the layout and explain exactly what needs to be done the simpler the better, of course. Thanks!

1 Answer

0 votes

use one of the roland checksums


1. I’ve done this for JD-xi. You will miss two bytes at the end of the sysex when you look at MIDI string. This is correct, The F7 and roland check sum is NOT shown in the midi box . If I remember correctly. 

2. Also you need to use named ticks b/c Roland goes to second byte after it reaches 0F. If you search the forum you’d find some examples of this See .your dump (last 3 lines)  

                                                                                            V 

F0 41 10 00 00 00 0E 12 19 01 20 35 00 00 00 0F 02 F7
F0 41 10 00 00 00 0E 12 19 01 20 35 00 00 01 00 10 F7 

3. Replacing values in the midi box:. For now there is no way to SELECT multiple controls and change the SYXES for all of them. I wish Dan could add this to 2.5. Otherwise when you lock the edit box (click the red light on the top right site of edit window in should change to green) That is the window with all the options, midi, relationship... ) Then when you open the MIDI message and fix a value of one control and click click another control the midi box will NOT CLOSE and show the appropriate message so you don’t need to do many click to change the values.   

answered Sep 22, 2016 by bladuck (640 points)
This is fixed in 2.4.5, forthcoming. We're waiting on an issue with ITC but it should be in the next few days in any case. Thanks!
...