Thank you, I am unsure what happened, I have just produced a new release that works on windows
https://github.com/StudioSixPlusOne/rack-modules/releases/tag/RC1.1.1.3c
There seems to be a bug with the mapping in 8x8, If I assign something then click on the next square to assign it then the assignment from the previous one jumps to the new square so doing many assignments at once is impossible.
1 Like
Thanks for taking the time to test. May I ask, when you are assigning, are you selecting the ui parameter first, then the midi, or the alternate. Could you possibly try it both ways?. If one of these methods works I shall disable the other
1 Like
Ah ok, yeah I was clicking the parameter first, trying the other way works as expected. Maybe other people can give some feedback about the preferred way, to me I would expect to hit the midi first but that may just be conditioned from other programs I’ve used in the past (ableton I guess).
Launchpad_MK2.vcvm (16.7 KB) Here is a preset for the mk2. The buttons on the right control the active buttons and the Mixer button controls the length. I didn’t map the Reset or Clock buttons as I would never use them but perhaps they could be mapped to User 1 and User 2? I can update it if you want.
1 Like
some more iverson feedback:
- i played around a bit with the controlPageUpdateDivider (and paramMidiUpdateDivider too) and until i reduced it down to what @stoermelder is using in midicat (see link below) the stepping of the leds on the controller was always looking a bit bumpy if i just connected a clock to iverson - with the values from MidiCat it steps very smooth (i actually halved the values for my sonaremin build as i’m often using lower sample rates than usual like 32 or 22.05 khz)
- learning mode on 8x8 seems to work fine for me by clicking the button on the ui and then on the controller
- how about some unlearn mode for a single mapping by either adding an unlearn button which unlearns the mapping of the button clicked next (with unlear button they should be switched to blue as well like in learning mode so that it is visible what is all mapped) or alternatively in learning mode if i click on a blue button and afterwards to a new button to learn that (without hitting a controller button first for the last clicked button) or exit the learning mode then the first clicked button gets unmapped
- i could prepare a mapping for the akai apc key 25 too - it has 5x8 buttons - kind of a mini apc mini
… what are you all mapping except the matrix button mappings in your presets? (i might look at the code but maybe just saying it here might be easier)
the link promised above:
best wishes - hexdump
1 Like
I may have a idea why this is happening. I don’t own a lauchpad mkII, but there is a programming manual that I shall have a read from to see if I can improve the situation. I would like this to be able to work with as many controllers as possible. You mentioned a key point, “It they way im used to”, I be looking into this as it will make for a better user experience.
Thanks for the template, I agree the mapping of the clock and reset are not priority, I only used them when testing, but never when playing. Mapping the page 1 and page 2 buttons may be more useful, as this would give access to sixteen steps / one bar from the controller.
1 Like
Thanks for experimenting with the clock dividers, getting feedback on hardware other than my own is invaluable. I shall reduce the dividers in Iverson.
Unlearn mode, there is currently an option for this in the context menu, “Clear midi mapping” then select the UI element you want to unmap, if you are in midi learn mode this becomes clearer. Your feedback make it clear that I need to update this.
All key mappings are welcome, I will update the documentation later today showing the current mappings. I currently only have a two line description of there use, at the bottom of the manual, I am sure pictures will help.
- The factory presets for APC mini Iverson JR map the sequencer grid, the lower buttons map the page selection, loop length and reset, the faders are assigned to the main probability controls.
- The factory presets for the APC mini Iverson when used with dual controllers features the same as above, with additional sliders for the Alt probability controls.
I forgot to mention the page buttons, I have mapped those to the arrow buttons on the top left.
I mistyped what I meant to say in the last post, I am used to clicking parameter first. It’s been a while since I’ve messed around with midi controllers and even longer since I’ve done any mapping with them. I just tried Renoise and it works by selecting the parameter first. I’m also trying Reaper but that seems to have it’s own weird way of doing things.
1 Like
I will make some pictures of your mapping for the manual, and check with you I have them correct before I publish. I am going to have to look at how I am mapping the launchpad MK3, as when in user mode I get no midi from the arrows, ard the right hand column buttons.
I am thinking of possibly adding an option the the context menu, for the mapping order, but I may think if there is a better way I can handle this, while I am away from my PC next week.
That could be a good compromise having the context option.
Do you mean you get no feedback, or no signals received in Rack? I’m not getting feedback for the arrow keys but the right hand buttons are working for me (both midi and feedback).
Maybe I need to dig deeper into the launchpad itself but the Session, User 1/2, Mixer buttons appear to do nothing special for me (just act like mappable buttons with no special modes or anything).
1 Like
here is a preset for the akai apc key 25 - the 5 rows of matrix buttons are mapped to the first 5 rows in iverson, the 5 buttons on the right to the matrix are mapped to the first 5 active buttons in iverson, the four arrow buttons below the matrix are mapped to the four page buttons in iverson, volume is mapped to length and pan to reset. the first five rotary controllers are mapped to the main probability of the first 5 rows in iverson.
i noticed that mapping the rotary controlles did not work well - i had to always enable learn, learn one button, disable learn and then do the next this way - otherwise somehow the button below the one i learned actually got used … it would be good if controller moves would also be visible during learning and making them blue too would be helpful as well … for controller usage it would be nice if they would have some pickup mode, so that their values get ignored while moving until they hit the current value in the patch for non-endless controllers
all the above are just suggestions of course
akai-apc-key-25.vcvm (14.6 KB)
best wishes - hexdump
1 Like
update: better ignore my apc key 25 mapping for now - i think it can be improved … i’m thinking about only mapping 4 rows and 4 controlles and leaving the remaining row and 4 controllers for mapping to other controls in a patch as this device is a universal controller not only for the gate sequencing … also i found out that mapping the clock hold button is nice too
one more thing i noticed is that the reset and clock-hold buttons stay lit when mapped - maybe buttons mapped to those non toggle settings should only be lit while being pressed?
1 Like
Thanks for the mapping, maybe take some time to see what mapping works best, or we could have a couple of mappings if you feel that works better, for different configurations. I am not planning on submitting to the library for at least a couple of weeks, I have a few days away from home, so no rush.
All your suggestions are welcome, I like community projects, I feel they can lead to more versatile and used modules.
When in user mode on the MK3 I get no midi from the arrow are RH button, this is not limited to Rack as I have checked with GMidiMonitor and ableton, maybe I need to do some more reading of the documentation, it could be user error on my behalf. I am not familiar with the launchpad yet, as I only purchased while developing this module, my normal controllers are the APC mini.
on the apc mini key 25 there are also some buttons hardwired internally and do not produce midi like a shift button and the octave up/down buttons - maybe it is something similar on the launchpad?
1 Like
There was a discussion on one of the @stoermelder treads about one of the launchpads and how to activate a user mode to control the LEDs (I can’t find the post now) but this was the link - https://www.partsnotincluded.com/how-to-control-the-leds-on-a-novation-launchkey-mini-ii. I tried to send the message from reaper to my mk2 but it did nothing so I don’t know if it is exclusive to that particular model or if I was doing something wrong but it might be useful to look into if you want to investigate.
It would be good to get feedback for the page on the arrow buttons but I’m not sure how to look into it, perhaps the buttons are hardware set to be one-shot (what’s the right word for this?).
I just want to express my gratitude to you for making these modules, you identified something that was really lacking and made it very easy to use these grid controllers, previously it took so many modules to make them even half usable and now it is very easy. With thousands of modules available that is not a small feat so well done and thank you.
1 Like
2 Likes
The controller modes you and @stoermelder have linked shall be very useful, and a nice bit of reading while on vacation next week. Looks like the novation controller will require a bit more development on my part, but will definitely be a required improvement.
1 Like
Thank you for sharing your work! I am myself on holidays as well, I did not bring my APC Mini, I will test when I get home. It feels like a really good step forward. I think this kind of feature should be enabled more easily by VCV through its API, e.g. a plugin could specify in its manifest which controllers (using device ids for example) are compatible. Along the same line there could be a widget to select both MIDI in and out, you rarely need to only send feedback or only receive input.
I do have my Akai Fire with me though, for which I am working on a similar module (as I explained here)
Sadly the Fire makes heavy use of SysEx for most of its interface, which is not working in Rack v1. The Fire also integrates a screen, shift and alt keys, leds and knobs ; I felt it makes sense to write a module dedicated to it, though as I said in the link above the programming work could be made much easier using scripting languages.
Anyway, I’m happy to see other modules do the same and I wish we can collaborate where useful to both of us! Thanks.
3 Likes
will this work with linnstrument in some way?