written by: Nathan
Hi There, All,hey all,
Finally getting to work through the tutorials (though have been playing around a little with the setups shipped with 2.0.33 with my alpha; nice to be able to easily delete the strip 1 pitch bend).
I was trying tutorial 1 with no instrument connected. When I create the pico manager, I do not get the pico keyboard agent created. Is this expected?
In general, should I be able to create setups in workbench without an attached instrument?
Thanks,
D
The Agents that represent the instrument connections come and go depending as to whether or not they're plugged in. If you plug one in and then connect it in Workbench, the connections will be remembered and automatically recreated for you next time it's plugged in.
We're probably going to change this at some point (not in 2.0 though) so that the Instrument Agents stay present even when their instrument isn't there. Right now you need to plug one in for that to happen then make your connection. You can work on the rest of the setup without the instrument connected at any time, you only need it to make that initial (or final) connection, so yes you can make setups without an attached instrument you just can't quite finish them.
John
OK, thanks for the clarification. It might be worth pointing this out more obviously in the docs and tutorials though. Being able to finish the setup at a later stage is a reasonable compromise.
D
I've edited the first Workbench tutorial to mention this behaviour.
Alistair
Hi, I've just added Workbench Tutorial 3 to the documentation. This tutorial introduces Keygroups and mode keys to the simple setup built in the second tutorial. There's a small caveat - while I was writing it, a few problems with the EigenD software came to light. Geert has fixed these and the fixes will be in the next release (2.0.35). Whilst the basic principles described in the tutorial are the same in the current release, some of the detailed behaviour, notably that of the red and green lights appearing on the Keygroup Output selector keys is slightly different.
Alistair
Thanks Alistair !!.... I'm following behind with the Documentation wiki feed!! (every revision...from everyone....)
Keep up the good work!
Allistar - Curious: How would we mimic the 1.4.x use of the Pico Mode key (little, black round ones) instead of a playable key?
Randy
@Randy, those are considered regular keys that just send an activation signal and none of the others. They're ordered after the playing keys, thus from 19-22 (1-18 being the playing keys).
@geert - In Tut 3, we enter row/column values for mode keys. Can I use Row 2, Column 0 to get to the normal Pico mode key? Or will this require the use of a Talker?
TIA
Randy
@randy, actually, these keys are in considered in row 3. So the top two ones will be row 3 and column 1/2.
Super! Thanks. BTW: On the Tau (you knew that was coming, right?) what's the row positions for those 4 keys at the middle/bottom?
Randy
I'll have to check, but I think all the switches are in row 6 on the Tau, I'll check tomorrow if that's not it
Tutorial works great! I made the mistake of not hooking up the 'keyboard pico 1' agent's 'key output' to 'kgroup 1' 'mode key input'. We hadn't worked with the 'keyboard pico 1' agent, so glossed right over that in the tutorial. But after I made the wiring, all was well. Mode key switch works as expected.
I set mine up just like typical Pico factory setup, with the top, left round key as the mode key. I used Geert's suggestion of 'mode key row' set to 3 and 'mode key column' set to 2. Again, works great.
BTW: If you want to set the Pico keyboard up as 'normal', you need to modify the 'krgoup 1' 'course size' and 'key map' parameters.
PICO
course size -> [[16,0.0]]
key map -> [[1,1],[2,2],[3,3],[4,4],[10,5],[11,6],[12,7],[13,8],
[5,9],[6,10],[7,11],[8,12],[14,13],[15,14],[16,15],[17,16]]
TAU
kgroup 1
course size -> [[16,0.0],[16,4.0],[19,4.0],[19,4.0]]
key map ->
[[1,1],[2,2],[3,3],[4,4],[5,5],[6,6],[7,7],[8,8],[9,9],[10,10],
[11,11],[12,12],[13,13],[14,14],[15,15],[16,16],[17,17],[18,18],
[19,19],[20,20],[21,21],[22,22],[23,23],[24,24],[25,25],[26,26],
[27,27],[28,28],[29,29],[30,30],[31,31],[32,32],[33,33],[34,34],
[35,35],[36,36],[37,37],[38,38],[39,39],[40,40],[41,41],[42,42],
[43,43],[44,44],[45,45],[46,46],[47,47],[48,48],[49,49],[50,50],
[51,51],[53,52],[54,53],[55,54],[56,55],[57,56],[58,57],[59,58],
[60,59],[61,60],[62,61],[63,62],[64,63],[65,64],[66,65],[67,66],
[68,67],[69,68],[70,69],[71,70]]
Hi Randy
We're going to be showing people how to set up musical key mappings and key filtering with Keygroups in a later tutorial. We were originally going to put it in that one but it made it very long, so we took it out for now.
Just so that everyone knows (and I'm going to adding this to the 'Introduction to EigenD page later), keys are now mapped in two separate ways. There's a physical mapping which is always referred to as 'row' and 'column' and a separate musical mapping of 'course' and 'key'. These two concepts are completely independent and each key stream carries both sets of coordinates along with it. This is new in 2.0 - previously we only had musical mappings of course, key. We introduced it to make certain things, like Talker keys or mode keys, able to be fixed as scale or course mappings change. This used to take some very weird dancing through hoops in 1.X setups.
It's going to be bad idiomatic form to use the wrong thing in the wrong place, more than likely, i.e. to use physical key mappings for musical things, as this will make setups very fragile with any change in the geometry of upstream keyboards, but for things where you want it fixed, this is invaluable.
John
Hi Randy,
The four top most Tau switches are in row 6 and the four bottom switches are in row 7.
Geert
Hi,
I've just added Workbench Tutorial 4 to the documentation. You can find it here. This Tutorial introduces the concept of rigs and how to create a simple rig based instrument. I hope you find it useful. Feedback is appreciated as always.
Alistair
Alistair - I would appreciate a tutorial on how to allow changing of scales from the instrument, functioning like in Factory setups. Is this something that can be isolated into a short tutorial? Is this something that can be done with v2.x and Stage?
Thanks,
Randy
BTW: I've been following your development of T4 via wiki RSS feed. I think it will be quite useful.
Hi Randy
Setting up Talkers (which provide that functionality) will probably be the next tutorial.
John
Super! Thanks.
Is it just me, or is anyone else confused by the row/column distinction in Workbench? Particularly on the Tau and the Alpha, what I would consider a column (ie a course of 24 keys on the Alpha) is actually a row in workbench and vice-versa. Not a big problem but might cause people a headache.
Please log in to join the discussions
UK
