Hey danoise, you forget to mention about this Prerequisites:
The Keyboard application will not work unless you have enabled the internal
OSC server in Renoise (Renoise prefereces -> OSC settings). It should be set
to "UPD" protocol, and use the same port as specified in Duplex/Globals.lua
(by default, this is set to the same value as Renoise, "8000").
At first, since notes did not sound at all, I was straying for a while… 
Thanks for pointing that out. Added to description
insanely good!
Satobox has discovered a small issue in which certain messages are doubled (working on a fix).
Once that’s taken care of, the standard keyboard will have a Grid Pie configuration 
Edit: Fixed, download llnk updated with new version
Hey danoise - where’s your tip jar?
Thanks, I did mess up something for the monome in that last release, as acknowledged here.
In any case, the reported issues should have been fixed - I’m hoping to release something tonight.
Are you planning to use the monome or mpd18 for triggering samples? Both are of course possible, also at the same time. If you experience otherwise, this is most likely because that last release didn’t play well with the monome to begin with.
Ah, OK - I think that is just a question of changing the colors being displayed on the monome in the device configuration. Lights may be blindin’ 
But wait just a little while…this exact part has changed a lot in the upcoming release
I just made a small change in how this tool works.
Now, when you set the keyboard velocity to a fixed amount it will always output notes at that velocity level.
So, if your workflow involves temporarily switching on/off velocity for your master keyboard as a whole, this tool will now let you use the “keyboard velocity switch” in the Renoise pattern editor toolbar to achieve that.
I have just updated the original post to cover the new features in Duplex 0.99.4
Support for the new “hold” and “mono” trigger modes in Renoise 3*
Grid layouts: harmonic, isomorphic and piano style
Some controller layouts got updated in this process, and have changed a bit. Hopefully for the better, but if you are missing the exact layout offered by the previous version, it’s possible to change the harmonic layout into something identical using these settings:
GridLayout.HIGHLIGHT_SAMPLE
HarmonicLayout.ALIGN_NONE
Contact me if in doubt as how to apply these settings.
Hi danoise, 
Recently I bought Launchpad mini and tried isomorphic layout in Duplex (let’s say 5-5-2 layout).
At first I couldn’t understand how to use it, but I found this page and I get it now.
https://hearandknow.wordpress.com/2014/03/15/the-isomorphic-note-layout/
But I also found an another page and I like the alternative isomorphic layout (let’s say 3X4 layout).
http://mididesigner.com/qa/3452/layout-isomorphic-keyboard-on-the-ipad
Isn’t there the chance to adopt the 3X4 layout too in Duplex? (only a chromatic scale layout is enough.)
I compared these two layouts and I personally think that the 3X4 layout looks easier than the 5-5-2 layout.
Well, I’ve already tried to hack the IsomorphicLayout.lua (tried “local pitch = (row\ *3 ) + col - 1”), it works to some extent but I give up now, haha.
Thanks in advance.
5444 
5445 
Hi danoise,
Recently I bought Launchpad mini and tried isomorphic layout in Duplex (let’s say 5-5-2 layout).
At first I couldn’t understand how to use it, but I found this page and I get it now.
https://hearandknow.wordpress.com/2014/03/15/the-isomorphic-note-layout/
It’s pretty typical of me to make something “clever” and not document it properly 
But what you are suggesting sounds interesting too. Have you actually tried playing with that particular layout?
Have you actually tried playing with that particular layout?
Ahh, yes I’ve tried (if saying correctly, I’ve touched them only a bit) and I felt not very confortable, (sorry to say).
There are too many doubling-buttons (like 60, 60, 62, 62, etc) so I was confused, to be honest.
I’d like to memorize the cord form as easyas possible. Having a lot of layouts can be counterproductive, imho.
So I like the isomorphic chromatic scale layout. It works great already and I want to practice it mainly.
Well, it’s just an opinion of a beginner without the perseverance, so never mind too much, haha. 
Would love support for the Livid Base!
I have been trying to use this keyboard application since it launched, and I’ve still never been able to figure out how to switch layouts and choose scales like you do in that first gif. It’s just incredibly unclear in all the documentation and this thread how you achieve that. Using the default launchpad config with an original launchpad for clarification.
I have been trying to use this keyboard application since it launched, and I’ve still never been able to figure out how to switch layouts and choose scales like you do in that first gif
You can switch bothscale and keyusing the supplied mappings (already part of the Launchpad config), or simply by choosing the scale/key manually from theinstrument propertiesin Renoise.- the Keyboard application will listen for this and change accordingly.
.
To change the layout you need to have the Duplex browser visible while the Keyboard app is selected/running, click ‘Settings’ and choose the layout you want from the option called ‘Grid Layout’
I can’t find the grid mode, where the lights represent my keyzones… Other than that, everything works fine so far. Can someone help me?
Edit (because this was not specific enough):
"In grid mode , the Keyboard application is able to visualize the currently selected instrument’s key-zone/sample
mappings in real-time. This makes it a lot easier to see exactly where each sound is located, and even works
as you are moving mappings around, or transposing the keyboard octave up/down."
This is what I want to have. But when I load a sample into a new instrument and shrink the keyzone so that it can only triggered by one key, still the whole matrix will light up and not only the one key. Why?
This is what I want to have. But when I load a sample into a new instrument and shrink the keyzone so that it can only triggered by one key, still the whole matrix will light up and not only the one key. Why?
Oops, overlooked this. Yes, you are right - and you’re not the first one to notice.
Later versions of Keyboard emphasize the dynamic layouts (isomorphic, chromatic etc.) over keyzone visualization.
I will see what I can do about this, perhaps toggling the visualization would make sense.
This tool (with Duplex) actually encourages me to invest in a real midi controller again (or build an own). Mouse-free workflow for the win.
Which device would you recommend for composing with Renoise (Duplex) primarily and perhaps a bit of Reaper for mixing ? Live-capabilities are secondary.
I have a couple questions about this tool/
I found the option self.flip_octaves in the layouts. This works great for the harmonic and isomorphic layout. When I flip the octaves on the Piano however, the actual keys get flipped along with the octaves. i.e. the black keys are on the bottom and white keys on the top. Is this intentional?
Is there a way to make the keys light up based on the pattern you have selected? Say I have a Launchpad, and the current selected track has notes in it, is there a way to highlight the keys of the notes that are playing on the launchpad? or does the device only work for input?
I have a couple questions
Black/white keys being flipped, hm yes that could be seen as an oversight. I never use that particular layout myself 
No, but I could see how very useful this could be.The implementation would need a few milliseconds latency, but as it’s a visualization only this should be no big deal.
Perhaps, when I get the time to bring back keyzone visualization I could take a look at this as well.
