<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Paul, John,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I have been using the X32 for some time now, and managed several gigs with it. The fact the console is entirely remote controllable using a wired or wifi connection, handling multiple simultaneous clients (i.e. sound engineer, stage musician, etc.) and now has several clients on android, iOS, Linux, Mac and PC is pretty damned good. I don’t think this would have been possible without the adoption of OSC. Nevertheless the initial documentation for it was quite … thin and it took serious effort to get access to all that was coded there.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>It now sounds like several manufacturers are following that path.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>It is also true OSC is a protocol format [only] standard. The contents of the data exchanged between clients and server (the console) is not forced/imposed, which is good and bad. Some will find it good because it enables manufacturers to develop their own stuff (quite standard practice in the music electronics industry), while others would prefer to have a single language for all, ensuring interoperability between devices. I am not trying to debate here.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>OSC is simple to code, easy to operate and quite effective (speed), thanks to fast networks; I found it quite reliable too.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>X32Reaper which I initially developed for my own studio needs is using OSC, and is acting as a middle man between the X32 and REAPER, based on the standard REAPER config file specifying what REAPER expects and sends in terms of OSC. The latest port runs great even on a Raspberry Pi (old version) enabling to the 32 channels of the X32 to control REAPER tracks, and vice versa: changes made at the audio workstation program are reflected on the X32. Easy to use and quite user friendly.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I was just hoping to find something similar (better in fact) from Ardour “</span><span style='font-family:"Calibri","sans-serif"'>probably one of the most OSC-controllable audio applications around”. While this may be the case from Ardour to its clients, the other way around doesn’t seem so (i.e. what is the receiving port for Ardour?).<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>-Patrick<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Paul Davis [mailto:paul@linuxaudiosystems.com] <br><b>Sent:</b> vendredi 5 juin 2015 20:23<br><b>To:</b> John Emmas<br><b>Cc:</b> ardour-dev mailing list<br><b>Subject:</b> Re: [Ardour-Dev] Ardour-Dev Digest, Vol 134, Issue 1<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Jun 5, 2015 at 1:32 PM, John Emmas <<a href="mailto:johne53@tiscali.co.uk" target="_blank">johne53@tiscali.co.uk</a>> wrote:<o:p></o:p></p><p class=MsoNormal>On 05/06/2015 14:54, Paul Davis wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br>There's not much point testing OSC support with the X32 without the active support of a developer working directly on OSC code. [...] OSC is a useful protocol but because it is completely non-standardized, both ends of the OSC exchange have to understand the same set of messages, and there is no standard set of messages.<o:p></o:p></p><p class=MsoNormal><br>Hmm... that seems like a pretty major drawback! Is OSC effectively a dead protocol now? I took a look at the Issue Tracker but there've been no posts for nearly 4 years!!<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>The notion of a standardized message set isn't part of the design spec or goals for OSC. People seem to completely misunderstand what OSC is. It is really just a specification of a message *format*. Not the mesage contents, or even the transport protocol. The messages consist of strings, with the first string being a set of 1 or more slash-separated words, optionally followed by arguments also passed as strings<o:p></o:p></p></div><div><p class=MsoNormal> /this/is/a/valid/message<o:p></o:p></p></div><div><p class=MsoNormal> /so/is/this 12 abd 19.78<o:p></o:p></p></div><div><p class=MsoNormal> /1871/akk1/a91991/a/ soIsThis<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'> /whatever/the/hell/you/want/to/use/it/is/ok/with/OSC<o:p></o:p></p></div><div><p class=MsoNormal>OSC doesn't specify anything else, really. So unless to two ends of the connection understand that /foo/bar/baz means "stop the transport", then it is meaningless.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-bottom:12.0pt'><br>Patrick - what gives you the impression that OSC is better for your purposes? For example, is X32Reaper based around OSC perhaps?<o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>the X32 OSC protocol specification does allow some stuff that isn't possible with generic MIDI. but to use it you need something that understands the X32 OSC messages.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>