Forum

Hi Bjoern,

You don't specify ranges of keys anymore that will be automatically mapped. In EigenD 1.4 the mapping was hidden from you and done behind the scenes, creating a lot less flexibility and mixing up the physical and the musical mapping.

In EigenD 2 you simply specify which incoming key is mapped to which outgoing key. Only keys that are mapped are considered being part of the keygroup. If you want to map four keys through Belcanto, they you specify the mapping for each key and keep it identical if you don't want to change it. In your case, this would be:

course 1 key 1 to course 1 key 1 add

course 1 key 2 to course 1 key 2 add

course 1 key 3 to course 1 key 3 add

course 1 key 4 to course 1 key 4 add

It's much easier to set this up in Workbench though, as you can directly edit a mapping string there, which in this case would be:

[ [[1,1],[1,1]] , [[1,2],[1,2]] , [[1,3],[1,3]] , [[1,4],[1,4]] ]

Note that since the musical and the physical mapping are now totally separate, you need to set up the physical keys also if you want everything to work transparently. The keygroup choose mode was created to make this very intuitive and both the physical and musical key positions that you select visually will be added to the keygroup. Workbench provides you with a handy one-click UI to enter and leave choose mode for specific courses.

Best regards,

Geert

Hi Bjoern,

That sentence summarizes the mapping function of a keygroup. When a key output is connected to the key input of a keygroup, the data is sent back out again through the active keygroup outputs. The mapping specifies how the input is transformed before it's sent to the outputs, and vice-versa for the light information.

HTH,

Geert

I think that when the keygroup has a blank mapping, then by default all the keys will play? This just happens to be the same as the mapping you created with the script above.

What key layout are you trying to achieve?

You can also use the choose mode that Geert mentions. He refers to the workbench version, but you can trigger this from belcanto also:

main keygroup listen

key as 1 choose

[choose course 1]

key as 2 choose

[choose course 2]

Where I write [choose course 1] you press the keys you want to be in course 1, one key at a time, then press the last one twice to finish. Repeat for course 2. This is all on the wiki page for keygroups in more detail.

If you don't want any duplicated keys (like on the tau and alpha, or a guitar), then you only need one course.

Thanks for a Google hangout with 0beron, we now have this problem solved. The issue was that you need to define both a physical and musical keymap, otherwise things go wrong. (Apparently Geert had mentioned something similar in another context.)

I'll post the outcome - link to follow shortly!

I have another question related to this: How do you define keyboard splits? Is this possible for the pico now?

(Previously there was a question over where the mode keys per split would go, given the limited keys on the pico. But given the flexibility in the assignment now, it would make sense to have two splits consisting of playing keys only, with configuration information passed through the existing four mode keys or in other ways.)

Hi carvingCode,

do you have a belcanto example, that sets up two keygroups on a pico?

Thanks,
Bjoern