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

Also check out the Facebook Group.

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

MIDI Designer
Design your perfect MIDI controller for iPad, iPhone and iPod touch.
LAYOUT: Kawai K5/K5m - MIDI Designer Q&A

Rating: GoldLAYOUT: Kawai K5/K5m

+4 votes
Rating: Gold
asked Apr 23, 2019 in Community Shares by thedood (930 points)
edited Apr 24, 2019 by thedood
No worries mate, go for it! Its long overdue a version upgrade and your reputation speaks volumes, I use your K1 and TG77 layouts all the time! Its been years since I built it and honestly, I haven't touched it since I done the final version uploaded here. Ive been buried in a rabbit warren with Eurorack and I cant get out. Help! lol ...I am having fun though. ;)
The 'values' never go above 127, but the addresses for the parameters do!! Once Kawai hit the upper limit of available parameter address's (127) they then used a separate value further up the sysex string to give them more addresses, essentially giving them 127 x 127 addresses for parameters. The reason they did this is because there are more than 127 parameters on the unit. When you look at all the parameters you can change on the K5 (separate values for two separate oscillators - S1, S2 and Both) they exceed 127 addresses, so Kawai cheated and used another value in the sysex string to give them more. This is the value we change using the MD2 channel controller, and I color coded them either green or blue for my own sanity while designing it, so I could tell which values needed that higher byte changed (sorry its confusing I know, but once you rip apart the layout, it should slowly make sense I hope).
Ive never been a brilliant interface designer. I'm a retired C++/# coder and I mainly worked on back end services, so UI was never my forte' ;) I now look after my adult son full time who is severely autistic. That's one thing I love about your interfaces, they're very spacious and easy to use...I make mine too cluttered (always trying to save space lol). Let me know when you finish, Ill be glad to scrape the dust off mine and give it a test buddy. Cheers
Take care.
Brett Aka thedood.
By the way I recently shared an update of my K1 layout. After I managed to get hold of a memory card, I could finally check and repair a bug, which did prevent the layout from loading patches from a card (external memory E/e). It turned out to be just a stupid simple mistake in the input rule. Its now sorted and works fine.
Hi, I managed to finish my version, based on your layout. That was super helpful, Kawai gave me a hard time to understand, how they set values using the two value bytes. But looking at how your controls were set made it a lot easier. I added some parameters and spread out dedicated controls for S1 and S2 on different banks. That takes a lot of space and requires more page switching, but allowed me to create a Streambyter input rule, so I can load existing single patches from the synth into the layout. Also the layout became quite big, I think 3,7MB. Same as the TG77 editor, bank switching on my old iPad Air2 can be kind a slow.
Actually after creating the first patches using the layout, I found myself using a hybrid way: I set the DHG spectrum, using the K5 own UI (so I see the spectrum in the display) and control everything else from MD. Works really well for me and makes editing so much easier and faster. Now before I share my version, I wanted to ask if it is ok for you if I mention your name same as in your own layout. Like " original layout by Brett Anthony, new version by Ib Kai". I´d like to give credits, but want to make sure that you're okay with it.
For sure mate. No problem! You dont need to worry about the credits buddy, all software is a work in progress. I'm just glad I could help. The ability to upload will be super cool!! Ill dust off mine and get it ready, I'm hanging to try it out!!
Take care
Brett (Thedood) ;)
I finally uploaded my version of the layout. Took ages, because it is pretty complex and I had to fix a lot of problems during the testing phase. Work in progress, indeed.