[Layzer2]

probably the most important thing to know about CTRLR is the xx variable.

when you add a control, ie; a slider or button…. you tell the control
what value you want to send using the xx variable.

for example, setting a control with a range of 0 – 127 will
give xx a value of 0-127 in a midi message like : F0 11 22 43 09 xx F7 plugged into the control’s midi message box

good luck and have fun making CTRLRS!!!!!

[Layzer2]

new version up, 1.2 fixes envelope type selector is reversed issue.
thanks to Tech44 for bringing this to my attention ” title=”Wink” />

[Layzer2]

ok dimi, try again download…. im still sorting out how to upload updated panels to the DDB… think i got it. let me know if the channel selector works for you!

[Layzer2]

yeah, by default it responds to channel 1. (which is the 00 value in the sysex header)

I updated the panel, it can now be set to any of the 16 midi channels via the channel selector.

[Layzer2]

looks great widy, i think i’m gonna tackle my Ensoniq VFX next!

[Layzer2]

This one is finally done and uploaded to the DDB. like the hardware oriinal, it is missing alot of stuff like modulation routings. but it is great for doing quick tweaks to the factory patches. i may add modulation routings later so keep an eye put for V2.

[Layzer2]

Thanks for the response Das, plugged in the code u supplied, changed the variables and it would crash….
BUT the good news is…you showed me how to send midi data out directly using sendmidimessagenow….

enabling me to cook up this code, which worked perfectly!!

function buttons ()
p = panel:getModulatorByName("Osc1 Pulse")
pv = p:getModulatorValue()
w = panel:getModulatorByName("Osc1 Wave")
wv = w:getModulatorValue()
send = pv + wv
m = CtrlrMidiMessage({0xF0, 0x06, 0x06, 0x10, send, 0xF7})
panel:sendMidiMessageNow(m)
end

i swear i worked on this one puzzle all day yesterday…
moving on finally!

[Layzer2]

I’m trying to figure out a way to do the following….

2 buttons… ON, OFF

when button 1 is on, it sends the value 1 to f0 06 06 10 xx F7

when button 1 is off it sends 0

easy enough…

when button 2 is on, it sends the value of 2 to f0 06 06 10 xx F7

when button 2 is off it sends 0

no problems….

heres where im going in circles….

how can i make both buttons send the value of 3 when both are on….
and have button 1 send the values 2 and 3 if toggled when button 2 is on, 0 and 1 if button 2 is off

and have button 2 send values 1 and 3 when toggled if button 1 is on, 0 and 2 if button 1 is off?????

i can easily accomplish this selecting using one button…but this is all in the name of making the controller
function like it’s hardware counterpart…

any ideas?……

[Layzer2]

yes yes… I had my eye on the KStation for a while now…. its kinda rare. I do a search on ebay for one every once in a while.
it is a slick unit.

edit: the KS5 is the one i’m after. (61 key version)

[Layzer2]

if you need help with skinning it i’ll be glad to help with that
I can create the knobless background and the knob and button uiImage components you will need.

[Layzer2]

meh… still needed lua. I have to switch multiple uitabs with one modulator. because the knobs are spread out that get shifted.
cant do it with linking cos you can only link to one uitab with one modulator.

used the example below to acomplish what i needed to with groups and LUA i found elsewhere and a bit of tweaking

[Layzer2]

well slap me silly….. v.787 doesnt understand uitabscurrenttab property….time to update. grrr.
shows up as ??uitabscurrenttab in the properties pane…that was my clue.

thanks again atom.

[Layzer2]

awesome! much thanks guys! this is for the Access Matrix 1000 programmer panel…. allthough it would
be so simple to just make separate knobs and buttons for those that get shifted by the env2 and env3 buttons,
it would not be an exact replica of how the unit functions. most of the fun is that challenge involved in trying to do just that!

[Layzer2]

ok i set it to normal+mousover and made a button strip like so:

frame 1 = button on
frame 2 = button off
frame 3 = button on
frame 4 = button on
frame 5 = button on

that works for all options 1 – 4

it even leaves the button in the right state when you mouse off.

the only tiny detail is that when button is pushed, it is in the OFF frame.
but i can live with that, thanks Atom, ur Da man!

[Layzer2]

how do you set it to mometary AND normal+mouseover? at the same time… i’m using build 787 is those properties changed in newest version?

[Layzer2]

Finished Panel uploaded to DDB, Merry Christmas and a happy new year!
hope you like!

[Layzer2]

I am creating a virtual PG-300. check further up to see the GUI… should be done in a few days

[Layzer2]

AN1X panel is coming along…. MU90R Performance editor finished.

UPDATE:
AN1x panel now has control of both scenes. tabs would not work so i had
to do alot of manual cut-paste in a text editor to make it work. a labor of love.

[Layzer2]

Hey guys sorry for not getting back to this… I started the process of skinning it yesterday. I picked up a Yamaha MU90R and made a controller for it yesterday as well. i will be working on the AN1x panel all thanksgiving weekend and should finish it by then

[Layzer2]

great job 2mm… I’m handy at skinning, and i was going to make this panel myself. how about we collaborate?
let me know.

[Author]

Posts