Originally Posted by
Onimode
Onimodeeeeeeeeee. :C
actually i almost write omnimode the other day... being how "omni mode" is where midi data is sent on all 16 channels
Speaking of changed to the API and whatnot, is there a way currently to have a "shift" button as a toggle-able button? button_shift() makes a momentary button only. I'm currently mapping my MixTrack out of fun, but seeking full original functionality.
sure - no need for any new functions for that. the shift button on the layout i created uses this:
Code:
hold_modifier("lp", "arm", 0, lp_hi_yellow, lp_lo_red, "lp_shift")
all you need to do to create one called "lp_toggle" on the "solo" button is this:
Code:
toggle_modifier("lp", "solo", 0, lp_hi_yellow, lp_lo_red, "lp_toggle")
you can then pass "lp_toggle" into that button_shift() function as normal. it just checks the state of the variable "lp_toggle" it doesn't care how/what set it. whether from code or a shift button or toggle etc.
button_shift() was probably a bad name - i just wanted a quick and dirty function that i could give two different events to send to traktor depending on the state of a shift button. feel free to come up with a new name for it
also, if u look in lib/base.lua you'll see other functions you can use for routing data in different ways:
Code:
-- Function Toggled Target Local Ignore Src Routing
-- Led Set Off Events
--
-- pipe() no device no no A ---> B
-- join() no device no no A <--> B
--
-- trigger() no device yes yes A ---> B
-- button() no device yes no A <--> B
-- button_shift() no device yes no A ---> B
-- toggle() yes device yes no A <--> B
--
-- pipe_modifier() no var yes no A ---> V
-- hold_modifier() no var yes no A <--> V
-- toggle_modifier() yes var yes no A <--> V
i've changed the names of functions round so many times already - but just realised that button_shift() function isn't duplex so should either be made duplex or renamed to trigger_shift() or maybe just something completely different
Bookmarks