Re: [Csnd] Send output to socket
| Date | 2011-08-08 11:35 |
| From | kelly hirai |
| Subject | Re: [Csnd] Send output to socket |
you could specify jack output and use netjack.
k.
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-08-08 21:19 |
| From | Roger Kelly |
| Subject | [Csnd] Send output to socket |
| Is there any way to send the outs opcode to a network socket instead of a file or audio card? |
| Date | 2011-08-08 21:48 |
| From | joachim heintz |
| Subject | Re: [Csnd] Send output to socket |
i think this is socksend(s), but i never used it myself.
joachim
Am 08.08.2011 22:19, schrieb Roger Kelly:
> Is there any way to send the outs opcode to a network socket instead of
> a file or audio card?
>
>
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-08-08 23:59 |
| From | zappfinger |
| Subject | [Csnd] Re: Send output to socket |
You could also use OSC. It uses sockets under the hood and it saves you the
trouble of socket programming (synchronous, asynchronous, etc).
Richard
--
View this message in context: http://csound.1045644.n5.nabble.com/Send-output-to-socket-tp4679110p4680111.html
Sent from the Csound - General mailing list archive at Nabble.com.
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-08-09 00:09 |
| From | Victor.Lazzarini@nuim.ie |
| Subject | Re: [Csnd] Re: Send output to socket |
| Attachments | None None |
| Date | 2011-08-09 08:35 |
| From | zappfinger |
| Subject | [Csnd] Re: Send output to socket |
You are right, not for audio. I should have read the question better..
Richard
--
View this message in context: http://csound.1045644.n5.nabble.com/Send-output-to-socket-tp4679110p4681088.html
Sent from the Csound - General mailing list archive at Nabble.com.
Send bugs reports to the Sourceforge bug tracker
https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
|
| Date | 2011-08-09 15:02 |
| From | Roger Kelly |
| Subject | Re: [Csnd] Send output to socket |
| "socksend" works fine using udp, but stsend (the TCP equivalent) never seems to bind to the listening port. Anyone have any ideas? UDP is not guaranteed to arrive in the correct order.
On Mon, Aug 8, 2011 at 3:48 PM, joachim heintz <jh@joachimheintz.de> wrote: i think this is socksend(s), but i never used it myself. |
| Date | 2011-08-09 15:30 |
| From | Roger Kelly |
| Subject | Re: [Csnd] Send output to socket |
| After digging around in the stsend opcode source, I am a bit clearer. It appears this opcode is doing a "listen" and is making csound a tcp server versus a client. I can connect to csound from a tcp client and and read data. I will try to get the entire orchestra output and try to reconstruct the wave file. The manual is not very clear about this. A reverse version of stsend that is similar to the socksend would be nice to have instead of a tcp server make it a tcp client. On Tue, Aug 9, 2011 at 9:02 AM, Roger Kelly <loraxman@gmail.com> wrote: "socksend" works fine using udp, but stsend (the TCP equivalent) never seems to bind to the listening port. Anyone have any ideas? UDP is not guaranteed to arrive in the correct order. |