Hi,
we are using OSCsend to control Ardour. Ardour is running on another
machine. Both machines run Linux Mint.

I started using the liblo tools, to find out how we could control Ardour on
the second machine. For example, to stop the moving playhead, we use:
oscsend osc.udp://192.168.1.xxx:3819 /transport_stop
These instructions can be found in the Ardour manual:
http://manual.ardour.org/using-control-surfaces/controlling-ardour-with-osc/

Empirically i found out that in Csound i needed to stop the playhead of
Ardour with:
OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop", "i", 1
instead of 
OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop"
that i was expecting because of the oscsend util.

Other OCS commands did not work either, but finally i found enough Csound
OSCsend commands to be able to play, stop and move the playbackhead of
Ardour to another marker - all of these commands quite differ from those
using the oscsend utility.

A program called WireShark was used to check what the OSCsend opcode was in
fact sending to the machine running Ardour.
As it turns out, according to WireShark, the command with the oscsend
utility is following the OSC protocol but the protocol send by OSCsend from
Csound uses something called POWERLINK/UDP. So it is another protocol, not
the OSC protocol.

It is confusing because i cannot follow the OSC directions from the Ardour
manual, so it is trial and error from now on?
Can someone please clarify?





--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

As far as I know, OSC is a protocol on top of UDP or TCP. So it is not 
strange that you see UDP in Wireshark, but that is a layer below the OSC 
layer.

Richard


On 24/12/17 15:04, Menno Knevel wrote:
> Hi,
> we are using OSCsend to control Ardour. Ardour is running on another
> machine. Both machines run Linux Mint.
>
> I started using the liblo tools, to find out how we could control Ardour on
> the second machine. For example, to stop the moving playhead, we use:
> oscsend osc.udp://192.168.1.xxx:3819 /transport_stop
> These instructions can be found in the Ardour manual:
> http://manual.ardour.org/using-control-surfaces/controlling-ardour-with-osc/
>
> Empirically i found out that in Csound i needed to stop the playhead of
> Ardour with:
> OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop", "i", 1
> instead of
> OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop"
> that i was expecting because of the oscsend util.
>
> Other OCS commands did not work either, but finally i found enough Csound
> OSCsend commands to be able to play, stop and move the playbackhead of
> Ardour to another marker - all of these commands quite differ from those
> using the oscsend utility.
>
> A program called WireShark was used to check what the OSCsend opcode was in
> fact sending to the machine running Ardour.
> As it turns out, according to WireShark, the command with the oscsend
> utility is following the OSC protocol but the protocol send by OSCsend from
> Csound uses something called POWERLINK/UDP. So it is another protocol, not
> the OSC protocol.
>
> It is confusing because i cannot follow the OSC directions from the Ardour
> manual, so it is trial and error from now on?
> Can someone please clarify?
>
>
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Recently - at my request - Victor made the type argument and value optional.
So i now was expecting to see the same commands as found in the Ardour
manual, so without   the type argument and value...
>From your answers, it must have something to do with the UDP - confusing is
getting greater at this at of the line :)

How to convert Csound OSCsend opcode text to Ardour text - ?



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

UDP is the uncertain one,
TCP can be relied upon...

There once was a protocol,

Whose parameters where known by all,

.....

On 24 Dec 2017 5:33 p.m., "Dave Seidel" <dave.seidel@gmail.com> wrote:

That's a good analogy. Another one: UDP is the envelope, OSC is the message within the envelope. Internet Protocol (IP)  is the postal service.

On Sun, Dec 24, 2017 at 11:24 AM, Justin Smith <noisesmith@gmail.com> wrote:

If I may risk an analogy - if you tried to send a limerick but got your syllables and rhymes wrong, it would be called "english text" - the problem isn't something with english necessarily, it's that by not following the rules for a limerick you fall into a looser category

On Sun, Dec 24, 2017 at 7:24 AM Dave Seidel <dave.seidel@gmail.com> wrote:

Nothing to do with UDP at all. It's just the underlying network transport. Perhaps still an issue with how Csound is forming the OSC messages.

On Sun, Dec 24, 2017 at 9:54 AM, Menno Knevel <magknevel@gmail.com> wrote:

Recently - at my request - Victor made the type argument and value optional.
So i now was expecting to see the same commands as found in the Ardour
manual, so without   the type argument and value...
From your answers, it must have something to do with the UDP - confusing is
getting greater at this at of the line :)

How to convert Csound OSCsend opcode text to Ardour text - ?

--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

--

http://mysterybear.net

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com

http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

--

http://mysterybear.net

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com

http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

as far as I know yes.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 24 Dec 2017, at 14:40, Dave Seidel  wrote:
> 
> Menno, the issue here is that apparently the OSCsend opcode requires a type argument ("i") and at least one value argument ("1"), even when the target server doesn't require them. This may have been fixed in 6.10. Victor?
> 
> On Sun, Dec 24, 2017 at 9:38 AM, Dave Seidel  wrote:
> This correct - OSC is a higher-level protocol (like HTTP, FTP, etc.), and requires UDP or TCP for the network transport. Typically, people use UDP because it is simpler and thus has lower latency.
> 
> On Sun, Dec 24, 2017 at 9:29 AM, Richard  wrote:
> As far as I know, OSC is a protocol on top of UDP or TCP. So it is not strange that you see UDP in Wireshark, but that is a layer below the OSC layer.
> 
> Richard
> 
> 
> 
> On 24/12/17 15:04, Menno Knevel wrote:
> Hi,
> we are using OSCsend to control Ardour. Ardour is running on another
> machine. Both machines run Linux Mint.
> 
> I started using the liblo tools, to find out how we could control Ardour on
> the second machine. For example, to stop the moving playhead, we use:
> oscsend osc.udp://192.168.1.xxx:3819 /transport_stop
> These instructions can be found in the Ardour manual:
> http://manual.ardour.org/using-control-surfaces/controlling-ardour-with-osc/
> 
> Empirically i found out that in Csound i needed to stop the playhead of
> Ardour with:
> OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop", "i", 1
> instead of
> OSCsend     1, "192.168.1.xxx", 3819, "/transport_stop"
> that i was expecting because of the oscsend util.
> 
> Other OCS commands did not work either, but finally i found enough Csound
> OSCsend commands to be able to play, stop and move the playbackhead of
> Ardour to another marker - all of these commands quite differ from those
> using the oscsend utility.
> 
> A program called WireShark was used to check what the OSCsend opcode was in
> fact sending to the machine running Ardour.
> As it turns out, according to WireShark, the command with the oscsend
> utility is following the OSC protocol but the protocol send by OSCsend from
> Csound uses something called POWERLINK/UDP. So it is another protocol, not
> the OSC protocol.
> 
> It is confusing because i cannot follow the OSC directions from the Ardour
> manual, so it is trial and error from now on?
> Can someone please clarify?
> 
> 
> 
> 
> 
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> 
> 
> 
> -- 
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> 
> 
> 
> -- 
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I'm afraid none of these reactions - although some quite entertaining - could
help me solve this puzzle, so i filed an issue to the issue tracker.




--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Victor fixed it. 
OSCsend now agrees with the OSC messages that Ardour expects:
http://manual.ardour.org/using-control-surfaces/controlling-ardour-with-osc/osc-control/

Thank you, Victor.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here