Replies: 12 comments 19 replies
-
|
btw. does anyone have a horizontal slider for me? the "KnobGallery" at www.g200kg.com link for png's is dead, isn't it? |
Beta Was this translation helpful? Give feedback.
-
|
you can use wayback machine to recover old web pages : |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, thanks a lot for this tip! |
Beta Was this translation helpful? Give feedback.
-
|
Is pitch a CC? I might be talking bullshit here cause I don't know sysex though so take what I say with a grain of salt |
Beta Was this translation helpful? Give feedback.
-
|
pitch relies on 2 bytes. One for coarse, one for fine. MSB LSB alike. It gives more precision like this. _In the pitchbend message, we combine the two bytes (the LSB and the MSB) to make a single 14-bit value that has a range from 0 to 16,383. We do that by bit-shifting the MSB 7 bits to the left and combining that with the LSB using a bitwise OR operation (or by addition). So, for example, if we receive a MIDI message “224 120 95” that means “pitchbend on channel 1 with a coarse setting of 95 and a fine resolution of 120 (i.e., 120/128 of the way from 95 to 96)”. If we bit-shift 95 (binary 1011111) to the left by 7 bits we get 12,160 (binary 10111110000000), and if we then combine that with the LSB value 120 (binary 1111000) by a bitwise OR or by addition, we get 12,280 (binary 10111111111000). The MIDI protocol specifies that a pitchbend value of 8192 (MSB of 64 and LSB of 0) means no bend. Thus, on the scale from 0 to 16,383, a value of 0 means maximum downward bend, 8,192 means no bend, and 16,383 means maximum upward bend. Almost all pitchbend wheels on MIDI controllers use a spring mechanism that has the dual function of a) providing tactile resistance feedback as one moves the wheel away from its centered position and b) snapping the wheel quickly back to its centered position when it’s not being manipulated._ https://sites.uci.edu/camp2014/2014/04/30/managing-midi-pitchbend-messages/ |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, thank you very much for the tip about representing the numbers in binary! Btw. I saw that the old CTRLR Forum is no longer available. Okay, I have combined all the nibbles and bits and see the result as hex. Byte Offset Okay, I combined the nibbles & bits within LUA. -- console("Pitch Mod Value+ :"..pitchValue) Kind regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Peter, Hope it helps |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, many thanks for the functions. I'll try it out. |
Beta Was this translation helpful? Give feedback.
-
|
This is one way to do it using a uiSlider - You can also use a uiFixedSlider. Set your uiSlider to -480 +480. I will name it pitch Set this field like this and hit enter to register the expression:
Set the MIDI to sysex with a formula like In this field you need a call back function for received MIDI:
The lua function in this callback will be something like: midiReceived = function(--[[ CtrlrMidiMessage --]] midi)
if midi:getSize() == 11 then
local MSB = midi:getData():getByte(7) * 128
local LSB = midi:getData():getByte(8)
local sum = MSB + LSB
sum = sum - 480
panel:getModulatorByName("pitch"):setModulatorValue(sum, false, false, false)
end
end
Roland usually uses zero for the lowest negative I am guessing this is the case for your drum machine, but I haven't read the manual. |
Beta Was this translation helpful? Give feedback.
-
|
Hi John, All mods and yes the pitch mod too, sends correct sysex values with: ... and so on The problem is, that the R-8m doesn't sends parameter values. So I must request a full patch dump. -- Pitch if pitchBit9 == 0 then The panel is for me awesome, all mods sends correct sysex and if receiving the bulks, all values are set correctly. I have an additional question, if I may ask you?! KInd regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Peter, So have you got it working with negatives? What is the sysex for -1? 5F 03 or 7F 7F ??? |
Beta Was this translation helpful? Give feedback.
-
|
Yup, it's working :-) |
Beta Was this translation helpful? Give feedback.
-
|
Okay - I know what to do - stand by :) |
Beta Was this translation helpful? Give feedback.
-
|
Okay I think this is it: I didn't really read the question properly. This is the algorithm you need to pass all two byte (negative) values through: local rawValue = (msb * 128) + lsb
local val = rawValue > 8191 and rawValue - 16384 or rawValue
|
Beta Was this translation helpful? Give feedback.
-
|
Wow, thanks a lot john. The functions are perfect! I'll add it to the panel. |
Beta Was this translation helpful? Give feedback.
-
|
I have a question... The R8m has three PCM-Card Slots, the Cards are „hardware coded“ numbered from 1 to 11 and contain various samples. My idea is, to use the information I set in the uiCombos PCM Card1, PCMCard2 & PCMCard3 Example: and the uiCombo Media then looks like: or Example: and the uiCombo Media then looks like: uiCombos PCM Card 1 - 3 with selectable content: The setting of a modulator content, I’ve understand, but not how to program a dependency of various contents of uiCombos I hope I expressed it somewhat understandably Kind regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Peter, Do you mean you have one uiCombo with the names of all the cards that the R-8m can accept. When you select one of those options another uiCombo is repopulated with all the patches from the selected card? |
Beta Was this translation helpful? Give feedback.
-
|
Hi John, The 13 entries in the uiCombo "Media" are needed, because with this uiCombo, the uiCombo "Instruments" were set, when a SysEx dump is received. Please, have look at the panel. |
Beta Was this translation helpful? Give feedback.
-
|
CTRL Version: 5.6.30 |
Beta Was this translation helpful? Give feedback.
-
|
I downloaded you panel - it looks like you have already achieved what you are trying to do? |
Beta Was this translation helpful? Give feedback.
-
|
But unfortunately only for one PCM slot. |
Beta Was this translation helpful? Give feedback.
-
|
You probably need to use tables with lists of each set to load. It's central to lua programming anyway. In my opinion uicombos are unstable, at least in 5.3.201 so I try to use Popups for complex stuff. Take a look here at what can be done, but it's a lot more complex to code! It’s difficult to understand what you want to do. If you can rephrase the question more succinctly I can maybe help. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for the links! I'll try it. |
Beta Was this translation helpful? Give feedback.
-
|
Let me know if you have any questions. |
Beta Was this translation helpful? Give feedback.
-
|
Hi John, With the table function, I can delete the current position of the three uiButtons and insert the current values in the table. But I have two problems, example1: PCMCard1 Name :SN-R8-09 uiButton Media: example2: PCMCard1 Name :SN-R8-09 uiButton Media: example3: PCMCard1 Name :SN-R8-01 uiButton Media: wrong: „INTERNAL“ is deleted PCMCard1 Name :SN-R8-01 uiButton Media: wrong: „INTERNAL“ is deleted PCMCard1 Name :EMTY uiButton Media: The second problem is… —table —uiButton I would be very happy, if you could give me a tip for my old head :-) selectPCMCards2 = function(--[[ CtrlrModulator --]] mod, --[[ number --]] value, --[[ number --]] source) -- For instance, if a is the array {10, 20, 30}, after the call table.insert(a, 1, 15) a will be {15, 10, 20, 30} -- mediaSelect with correct PCM-Card positions -- example for correct syntax for uiComboContent! -- wrong -> uiComboContent="" ! end |
Beta Was this translation helpful? Give feedback.
-
|
"EMPTY" ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, From panel:getComponent(selectMedia):setProperty("uiComboContent", mediaSelect, true) |
Beta Was this translation helpful? Give feedback.
-
|
Hi Peter, I am glad you sorted out the previous problem. Smoke was coming out my ears trying to decipher it! Here is code to populate a TOT=11
fillButton = function(--[[ CtrlrComponent --]] comp --[[ MouseEvent --]], event)
local t = {}
for i = 1, TOT do
table.insert(t, mediaSelect[i])
selectMedia:setProperty("uiButtonContent", table.concat(t, "\n"), false)
end
end
ms = {}
ms.__index = function(t, k)
t[k] = "(" .. k .. ") EMPTY"
return t[k]
end
mediaSelect = {"OFF", "INTERNAL"}
setmetatable(mediaSelect, ms)
This is a good situation in which to use a rather more advanced lua feature called but you can also do something like: fillButton = function(--[[ CtrlrComponent --]] comp --[[ MouseEvent --]], event)
selectMedia:setProperty("uiButtonContent", table.concat({"OFF", "INTERNAL","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"","EMPTY"},"\n"),false)
end
Simpler is better unless you want to reuse code, in which case, for me, the metatable option becomes easier to manage in fact |
Beta Was this translation helpful? Give feedback.
-
|
Hi John, Ctrlr Panel (PCMCard -> Media Select -> Key# Instruments)_1_0_2024-09-03_17-24.panel.zip |
Beta Was this translation helpful? Give feedback.
-
|
The code looks very neat and orderly and your are using tables efficiently I think! Well done! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your help!!! |
Beta Was this translation helpful? Give feedback.
-
Hello to everyone,
btw. the Roland R-8m is is a parameter monster, so it makes sense to be able to set the parameters clearly with a panel, instead of using 6 buttons for every key note… uuuaaahhhh :-)
Roudabout 800 parameter or more for one patch, including 4* Performance and possibly additionally
8 * Feel Patches. I really hope, that CTRL can manage this :-)
So far the panel works as I wanted, but before I continue I have a question to the LUA experts of you.
All parameters are directly sent from the modulators via sysex, including the Roland checksum, also those that send negative values. All works perfekt! :-)
All mods are set to the correct values per sysex patch receive.
Except!!! all the modulators with negative values…(disabled at the moment) :-(
Sure, I also searched the old ctrl forum and various panels too. But, unfortunately, always affects to be „send“ the negative values, but not what to do via Lua, when receiving this values per SysEx, splitted in lsb and msb bytes.
How can I set these values to the correct modulator values? I just can't figure it out :-(
I'm sure, someone of you has an idea for me. That would be really, really helpful for me.
The modulator "Pitch" has a value range from -480 to 480, where the "0" value is at position "480".
Example for a received SysEx string: Pitch for Key C2 (24h) Instrument:
F0 41 00 36 12 01 24 02 20 39 F7 LSB -480 (Mod Value must be = 0 to set)
F0 41 00 36 12 01 24 03 7C 5C F7 MSB -480 (Mod Value must be = 0 to set)
F0 41 00 36 12 01 24 02 00 59 F7 LSB 0 (Mod Value must be = 480 to set)
F0 41 00 36 12 01 24 03 00 58 F7 MSB 0 (Mod Value must be = 480 to set)
F0 41 00 36 12 01 24 02 60 79 F7 LSB 480 (Mod Value must be = 960 to set)
F0 41 00 36 12 01 24 03 03 55 F7 MSB 480 (Mod Value must be = 960 to set)
Kind regards and many, many thanks for your help
Peter
Beta Was this translation helpful? Give feedback.
All reactions