[fundorin]

I’ve found that “arguments” type is table and “arguments[0]” type is userdata, which is seems to be C type data.
Now I’m trying to find out how to convert userdata into string, depending of whether text (string) agrument of the OSC message was received or number (float).
Any help would be appreciated.

P.S. To be clear, my goal is to make midi<>osc bridge with Ctrlr, so I could send MIDI commands from Novation SL MkII controller to Ctrlr, convert them into OSC commands and send them to Reaper. Then, OSC feedback from Reaper would be converted into MIDI commands and fed to SL MkII.

[fundorin]

I’m stuck, trying to get string value from received arguments table on receiving OSC message.
In demo OSC panel it’s set to output arguments as float numbers.
I’ve commented output to panel monitor and only trying to get the right output to console.

onOSCMessage = function(path, types, arguments)
	console ("OSC: " .. path .. " types: " .. types)
	--console (string.format ("float: %.2f",arguments[0].f))
	console (tostring(arguments[0].f))

--	log = panel:getLabel("oscMonitor")
--	if log:getText():length() > 300 then
--		log:setText("")
--	end
--	log:append(path):append(", "):append(types):append("\n")
--	for i=0,#arguments do
--		log:append(string.format(" %.2f [%d]", arguments.f, arguments.i))
--	end
--	log:append("\n")
end

I get normal output of values, that are numbers, but when the argument is a text (like host’s track name), I get this output to Lua console:

LUA>> OSC: /track/2/name types: s
LUA>> 1.825356e+31

where second line should print “sdfsdh”, instead of 1.825356e+31.
Each time I try to access “arguments” a different way, Ctrlr crashes either when compiling script or when OSC message is received. I wonder how this arguments table is constructed and how to get a needed value out of it?

[fundorin]

Deleting C:\Users\your_user_name\AppData\Roaming\Ctrlr\temp_folder_name helped.

[fundorin]

.crash contents:

Ctrlr crash at: 3 Dec 2016 23:43:36
Stack trace:
3: UnhandledExceptionFilter + 0x157
4: memset + 0x239b
5: _C_specific_handler + 0x96
6: _chkstk + 0x11d
7: RtlImageNtHeaderEx + 0x483
8: RtlRaiseException + 0x2d9
9: RaiseException + 0x68
28: BaseThreadInitThunk + 0x14
29: RtlUserThreadStart + 0x21

[fundorin]

My siuation:
Controller – Novation SL MkII 61.
DAW – Cockos Reaper.

Reaper cannot provide feedback from host and plugins via midi. But it have OSC feedback.
Novation can’t do OSC. Only MIDI (with some nuances, actually).
I would like to setup multiple layouts for SL inside Ctrlr, with shift modifiers.
So Reaper will send OSC feedback to Ctrlr. Controller will convert it to midi (and sysex) and then send it to SL’s LEDs (param values) and LCD (track, fx, param names and values.
The same goes from SL to Reaper.

I’ve seen many threads from people who can’t hook up their midi controllers or keyboards (old and new) to different DAWs and struggling with programming scripts on PureData, Max for Live, Bome and OSCII-bot. Trying to emulate Mackie (MCU and HUI).
Most of them are giving up and ending by switching to iPad apps like Lemur or TouchOSC.
Physical controls are always better for controlling DAW than touchscreen. Feedback from DAW to your encoders, mechanical faders and LCDs is also good. That’s why we need OSC support in Ctrlr.

To read about OSC you can visit the official site – opensoundcontrol.org/ which isn’t working for me today.
Wiki with the list of apps, that support OSC – https://en.wikipedia.org/wiki/Open_Sound_Control
Reaper forum and default configuration file – http://www.reaper.fm/sdk/osc/osc.php

Users can control their hardware synths from tablets and phones with OSC apps, via cable or wifi.

As for me, I recommend you to download Lemur editor and some templates to see what kind of data is used for OSC and how it’s implemented.
https://liine.net/en/downloads/lemur
https://liine.net/en/community/user-library/

Same with TouchOSC – http://hexler.net/software/touchosc#

It’s my dream to have some app sitting in tray of my PC and act like a highly customizable bridge for my controllers. Same as Automap concept, but not as bad as Automap. 🙂

• This reply was modified 8 years, 6 months ago by fundorin.

[fundorin]

Is there any plans to add OSC support at all? The only app capable of doing this is a script-text based osciibot from reaper, which is pain in the ass to configure.
Other apps like Bome and Ctrlr aren’t capable of handlind osc at all. From those two options I prefer Ctrlr to support OSC, so it would be possible to use hardware midi controllers in OSC-based software. Thanks in advance.
P.S. Tell me if OSC support planned in Ctrlr at all or not. Thanks in advance.

[Author]

Posts