[CM] How to send udp bundles from Grace on Linux?

[Forrest Curo]

I've used (and know of others using) -L; it's a good fast way to control
csound. Tthanks for the code example re accessing it from Grace.

Haven't really worked with juce (or c++) so far; but next time I need to
network to csound I can [probably] put in & recompile with that
InterprocessConnection class.

Thanks all!

On Fri, Mar 6, 2020 at 4:54 AM Taube, Heinrich K <taube at illinois.edu> wrote:

> many years ago i  had a connection to realtime csound using the juce
> InterprocessConnection class
> https://docs.juce.com/master/classInterprocessConnection.html.  Its not
> in the code base anymore (no one ever used it) but thats the way i would do
> it.
>
>
> On Mar 5, 2020, at 8:16 PM, Forrest Curo <treegestalt at gmail.com> wrote:
>
> Um, a more graceful possibility:
>
> Adapt the c++ code from the Csound Api examples. Simply run instances of
> csound within Grace.
>
> (?)
>
> On Thu, Mar 5, 2020 at 6:05 PM Forrest Curo <treegestalt at gmail.com> wrote:
>
>> Grace is sending valid osc messages.
>>
>> If these were going to Supercollider, that's how they'd be handled.
>>
>> Received by the csound udp server, valid osc is not valid realtime score
>> events.
>>
>> Since JUCE is largely a C++ compiler... I should be able to
>> #include<system.h> and add code to either write csound score lines to a
>> fifo, or call bash's 'nc' to udp them to another computer. (?)
>>
>> Those approaches wouldn't be graceful, but they are ways I could
>> (eventually) do it for myself.
>>
>>
>>
>>
>>
>> On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K <taube at illinois.edu>
>> wrote:
>>
>>> im pretty sure grace is sending valid osc messages, i cant tell what
>>> going on from the information you are giving me
>>>
>>> On Mar 5, 2020, at 6:14 PM, Forrest Curo <treegestalt at gmail.com> wrote:
>>>
>>> Put in a header; csound objects.
>>> Leave it out; Grace calls an error.
>>>
>>> On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo <treegestalt at gmail.com>
>>> wrote:
>>>
>>>> Supercollider is set up to accept udp formatted as OSC messages.
>>>>
>>>> Csound 'expects' score events instead. I'd know how to format these if
>>>> I knew how to specify a string and send it from, Grace.
>>>>
>>>> On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo <treegestalt at gmail.com>
>>>> wrote:
>>>>
>>>>> cm says "OSC send test succeeded"
>>>>> & csound says:
>>>>> error: syntax error, unexpected '/'  (token "/") line 7:
>>>>> >>>/ <<<
>>>>> Parsing failed due to invalid input!
>>>>> Stopping on parser failure
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo <treegestalt at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> syntax for sending a string to a port?
>>>>>>
>>>>>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K <taube at illinois.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> You should be able to send OSC to any port you want,  look in the
>>>>>>> Audio menu for the OSC Connections… command.
>>>>>>> I haven’t tested OSC yet on this release...
>>>>>>>
>>>>>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo <treegestalt at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I have csound running & set to receive udp  (i.e.  --port=4567 )
>>>>>>>
>>>>>>> ( https://csound.com/docs/manual/udpserver.html )
>>>>>>>
>>>>>>> I can send lines it lines for immediate output from pure data:
>>>>>>> [send scoreline_i "i 2 0 3 440 .5" (
>>>>>>> |
>>>>>>> [netsend -u ]
>>>>>>>
>>>>>>> likewise channel values:
>>>>>>>
>>>>>>> [send @valu 330 (
>>>>>>> |
>>>>>>> [netsend -u ]
>>>>>>>
>>>>>>> but in Grace the OSC examples are based on sending to an established
>>>>>>> TCP connection to Supercollider.
>>>>>>>
>>>>>>> What to do?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Cmdist mailing list
>>>>>>> Cmdist at ccrma.stanford.edu
>>>>>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>> Cmdist mailing list
>>> Cmdist at ccrma.stanford.edu
>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>>>
>>>
>>> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/mailman/private/cmdist/attachments/20200306/5973cb05/attachment.html>