Forum Replies Created
-
Posts
-
Does it have to be twice the same panel or for example one panel just sending some MIDI sysex and an other, different one, receiving it? I’m asking because at the moment I just have a laptop with Ctrlr and the panel I’m working on, no MIDI devices hooked up, so no real testing possible.
I have finished the controller part of the panel and I’m starting with the processing of the MIDI in data from a patch dump request, because I want this panel also to become a patch editor. Unfortunately I’m not able to test the panel at the moment in a MIDI setup with the TX7 (I’m away on a kind of holiday).
While the color setting for inc/dec button didn’t show up in Ctrlr for Mac, it does show up in Ctrlr for Win (using rev. 1311). I loaded my ‘Mac’ panel in Ctrlr for Windows and all the buttons (I copied them all from one) had the intended customized color… I noticed you have this issue removed from the tracker, but I don’t see a new nightly build for Mac (?)
Thanks! Everything with the global variables back to normal again and setting them works fine now. (Was a bit lazy and in a hurry, should have found the solution of adding a boolean variable myself, sorry.)
Tried it in the Lua console:
function fixGlobal()
panel:setProperty(“panelGlobalVariables”,”0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0″)
end
This is the result:
>>> fixGlobal()
ERROR: No matching overload found, candidates:
void setProperty(CtrlrLuaObject&,Identifier const&,var const&,bool)
(Sorry, I won’t be on this forum for tonight, going out…)
I’m aware of the panel property ‘Global variables’. Normally it’s filled with ‘placeholders’ with the value -1. In my panel only one value shows up (probably k0 because this value seems to work), but other values for e.g. k1 don’t show up. (See attachment). I checked this with a fresh panel and then for example setGlobal(3,64) does work and shows the value 64 for (in this case) k4. Probably a side effect of the weird behaviour of my panel? (See my posts in the thread “Panic!”.)
To my knowledge I didn’t do anything special. Just added buttons and sliders. I did though experiment a lot with the appearance of the components, colours and fonts etc. Also I was trying out some expressions. But the panel behaved normal all the time and when I was finished I just did a save and quit last night.
THANKS!!
Especially for this panel I wanted to do everything (if possible) without Lua, at least at this stage of development, so I did not use any Lua scripting. Again, thanks, you saved my day, man!
With the help of your ‘DEMO-Complex expressions.panel’ I was able to solve the problem. I used this expression: setGlobal (0, setBit (global.k0, x, modulatorValue)) and x has to hold the bit number to set. As you can see the setBit expression uses a 3rd parameter, which you don’t mention in your Documentation. Without this 3rd parameter the expression doesn’t work (for me…).
Thanks for the example. I tried also toBack() and toFront(true) and it works! ( Sorry for the late reply, was away for the weekend.)
Probable a beginners question, but does one assign an index to a modulator in the properties panel under ‘modulator CustomIndex’?
I’m not sure I have the same issue, but let me explain. Depending which button I push on my device it sends a different amount of MIDI CC messages to the CTRLR panel (see attached screen print). The number of messages is each time the same, depending on which button I push. I need to analyze this ‘bunch’ of messages. My question: does CTRLR somewhere keep track of these messages or stores them temporarily or do I need the above ‘append’ method to put all these incoming midi messages in one memory block?
Look at this thread: http://ctrlr.org/forums/topic/specifying-a-unique-midi-message-for-each-slider-value/ (near the end)
I also like to correct a misunderstanding 😉 I know atom you help a lot with the programming stuff and I appreciate it very much, you can be sure of that! But I meant more the LEARNING part of CTRLR/Juce and Lua. This is IMHO what you have to do mainly for yourself.
