I'm trying to control sooperlooper (1.0.8c) via OSC commands (all on the
same host), using the commandline utility sendOSC, found at
To (try to) listen to incoming messages from the sooperlooper OSC server
I use dumpOSC
But the sooperlooper OSC server doesn't seem to react to any other
command except /quit, (which makes it quit and after a while slgui pops
out a dialog saying "Lost connection with the SL engine")
On the sooperlooper-users ml (on which I am not subscribed) archives I
found a thread on (almost) the same problem (sooperlooper OSC server not
reacting to get requests or ping):
Jesse Chappel gave an example for ping command, but it doesn't work here..
According to http://essej.net/sooperlooper/doc_osc.html , the command
for i.e. starting to record on sooperlooper via OSC is
where # is the loop index (usually 0, or -1 to send the command to all
loops) and cmdname is a string, i.e record. It should issue the pressing
of "record" button.
So, with JACK running, and all from the same host:
I fire up sooperlooper (that listens from OSC commands on port 9951 by
default) and from another terminal slgui, to "see" what happens in the
From another one I start dumpOSC on port 11122;
From another one I send commands to sooperlooper with sendOSC:
If I do
sendOSC -h 127.0.0.1 9951 /quit
If I do
./sendOSC -h 127.0.0.1 9951 /sl/0/down record
it doesn't start to record. The same with "down" and "up" instead of
"hit" (to issue pressing and depressing of the record key)
Neither it responds (dumpOSC doesn't print anything) to
./sendOSC -h 127.0.0.1 9951 /ping osc.udp://127.0.0.1:11122 /iamhere
I think it should print iamhere...
I have tried to load a loop with
./sendOSC -h 127.0.0.1 9951 /sl/0/load_loop /home/salvuz/loop.wav
It neither loads the loop, nor sends the string sorry_ERROR to dumpOSC.
Does anyone know what am I doing wrong?
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---