[proton]

Hi, I checked the Utility panel on the right to see all the available properties and no, sorry, I am still at work and will have to stay longer today so maybe on the weekend I will try the string thing. Let us know how is the progress, cheers!

[proton]

Hi fundorin, use variation of this in your method to switch stuff:

panel:getProperty(“panelOSCEnabled”)
panel:setPropertyString(“panelOSCEnabled”,”0″)
—–/// 0 = OFF, 1 = ON ///—–

panel:getProperty(“panelOSCPort”)
panel:setPropertyString(“panelOSCPort”,”7777″)
—–/// 7777 = port number to listen on ///—–

panel:getProperty(“panelOSCProtocol”)
panel:setPropertyString(“panelOSCProtocol”,”4″)
—–/// 0 = Default, 1 = UDC, 2 = UNIX/LOCAL, 3 = TCP ///—–

[proton]

Hahaha, yes, sure the page wasn’t refreshing so I couldn’t see Possemo already took initiative!
Glad we could help.

BTW – Thanks for the OSC tip, all is working now I just had OSC monitor using the same port as Ctrlr hence the trouble but once I switched it off all is good.
Will check the string issue later today.
Cheers!

• This reply was modified 7 years, 4 months ago by proton.

[proton]

in CC = “B0”
“B” is the code for CC and “0” is channel Nr.1
same as 90 would be 9 – NoteOn massage and 0 channel 1
or 82 would be 8 – Note Off massage and 2 – means channel 3

clear?

[proton]

— Called when a modulator value changes
— @mod http://ctrlr.org/api/class_ctrlr_modulator.html
— @value new numeric value of the modulator
—
sendTest = function(–[[ CtrlrModulator –]] mod, –[[ number –]] value, –[[ number –]] source)

transport = 10
oscValue = 10
channel= 10

CC = “B0”
midiMsg = string.format(“%.2x”, transport)
midiValue = string.format(“%.2x”, oscValue)
midiChannel = string.format(“%.2x”, channel)

panel:sendMidiMessageNow(CtrlrMidiMessage(“f0”..CC..midiMsg..midiValue..channel..”f7″))

end

[proton]

it works OK here:

https://s27.postimg.org/mgqce5dur/sysex.png

[proton]

Sysex start and end are missing and by oscValue you mean midiValue

midiMsg = string.format(‘%.2x’, transport[5])
midiValue = string.format(‘%.2x’, oscValue)
midiChannel = string.format(‘%.2x’, channel)

panel:sendMidiMessageNow(CtrlrMidiMessage(“f0”..midiMsg..midiValue..midiChannel..”f7″))

• This reply was modified 7 years, 4 months ago by proton.
• This reply was modified 7 years, 4 months ago by proton.

[proton]

Hmm, sure, this is what I did but still nothing comes into Ctrlr when I send OSC to it.
Are you using Ctrlr in stand-alone mode or you test it as a VST or AU plugin?
Do I need to do pay attention to something more than port I send to?
I thought “Slider1” will receive and move as soon as it gets values on the proper channel and from a proper Address. One thing I just realize is that “Slider1” in that particular case is sending integers and Reaper or Lemur are sending floats. Can this be the issue? Thanks!

[proton]

Thank you Atom, you rule!
From what I understand only the additional LUA 5.3 features are in question here not the regular stuff we have used before LUA 5.3 was implemented.
Thanks for the heads up and wish you luck with the issues!
Cheers!

[proton]

Hi fundorin,
can you please guide me how you are getting/setting OSC into Ctrlr? I would like to look into your problem but for some reason I can only send OSC from Ctrlr but am not receiving anything. I tried Reaper, Lemur and Touch OSC to send on different ports (even 9999 using your version of the OSC-Demo panel) but no luck. Since you are able to see incoming OSC messages in console I’m pretty sure I am doing something wrong and not the software.
Thanks!

[proton]

Hi,
on the programming side – no problem – buttons sending midi messages is nothing special
BUT
the honeycomb buttons might be hard to implement since Ctrlr uses objects that are rectangles and not hexagons.
If anyone knows how to program shapes other than rectangles please chime in since I would also be interested in some other shapes as buttons (mostly circles in my case).
Cheers!

[proton]

Hi Atom,
you read in my mind! 😉
This would be awesome if this option will find its place in Ctrlr.
I will start testing things here and there and prepare myself mentally for this to be available at a certain time!
Take your time thou, no hurry, we are sooo grateful that you invest so much of your free time to develop this monster, hats off Sir!
Have a great evening everybody!
Cheers!

[proton]

Hi dasfaker, and thank you for the input!

yes, I plan to generate chords that will be triggered by pressing a button (no problem here) or automatically on a beat (every 2 bars for example, or every quarter) and for that bpm input is a must I think.
I use LUA for generating the chords structure/voicing and when I set the tempo using a temposlider and play them against the same tempo in my DAW all stays in perfect sync for many many minutes – tested already. The problem is the communication and syncing between both but maybe the MIDI thru option you’ve mentioned is worth exploring. Thank you for that!
If there are more ideas – feel free to spill them all 😉
Cheers!

[proton]

Hi Atom,
after the installation of the newest Win build Ctrlr-5.4.11.exe the Help>About still shows Version = 5.3.201 and Build date = March.30th
Am I doing something wrong or is this how it should be?
Cheers!

[proton]

Awesome news atom!
Keep rockin’ this awesome piece of software!
Cheers,

[proton]

Ok, so I can trigger a LUA script now every time there is a MIDI coming IN but I am struggling with one more crucial thing: how to distinguish not only if there is a MIDI IN activity but to recognize what pitch or its velocity was played?
I would like to react differently to different pitches ev. to different values/velocities. Is there a way to check for the incoming pitch (something like get midiMessageCtrlrNumber)?
Thanks in advance!

UPDATE:

For now I use this solution and it works great:

local MIDIdata = midi:getLuaData()
local byte0 = MIDIdata:getByte(0)
local byte1 = MIDIdata:getByte(1)
local byte2 = MIDIdata:getByte(2) …

I’m pretty sure it will get more complicated down the line but this is enough for now.

Cheers!

• This reply was modified 7 years, 10 months ago by proton.

[proton]

Hi Puppeteer,
Thank You for chiming in!
I tried your way and so far so good – modulators are reacting to incoming midi data! Thank you!
I will have few more questions the deeper I go with my panel but for now this works, have a great evening!
Cheers!

[proton]

Hi Roman!
No need to apologize!
I think we all can understand and wish You all the best and a smooth transition in whatever You have going on. You did already much more for us than You had to so take care and focus on more important things right now.
All the best to You!!!

[proton]

Hi,
that would also be of interest to me.
I had this font problems for quite some time until after many tests I decided to use only “Trebuchet MS” font since this one looks exactly the same on both platforms.
Embedding a font into a panel resources would be the easiest solution anyways!
I hope we can find a solution for that.
Have a good one!

[proton]

Yap, same here, both systems, same builds as you mentioned.
All panels load properly but the “image resource” column in the modulator list and .xml file are blank. I suppose it has to do with the latest build.
Atom?

EDIT: All good with the previous version 5.3.196 for PC.
Going back a version might be a workaround for now.

• This reply was modified 8 years, 1 month ago by proton.

[Author]

Posts