[Csnd] OSC in Csound 7
| Date | 2025-12-02 04:17 |
| From | Adam Willetts |
| Subject | [Csnd] OSC in Csound 7 |
Hi,
Is it currently only possible to use OSC via the UDP server in Csound 7?
Thanks,
Adam
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 |
| Date | 2025-12-02 06:54 |
| From | Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
|
yes, see
https://csound.com/manual/overview/udp-server/
Prof. Victor Lazzarini
Maynooth University
Ireland
On 2 Dec 2025, at 04:18, Adam Willetts <adam@ethermap.org> wrote:
|
| Date | 2025-12-03 00:52 |
| From | Adam Willetts |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
| Hi Tarmo and Victor, Thanks for your replies. Tarmo, trying to use the OSCinit opcode in Csound 7 results in “error: Unable to find opcode with name: OSCinit” so my understanding is that the UDP server is currently the only way to start an OSC server and create a port. Victor, are there plans to eventually include all the old OSC opcodes in Csound 7, either directly or as part of the optional plugins repository? I’ve been using the UDP server and really like how much extra OSC functionality it adds. The main reason for my question is that I find there is a subtle difference in the way Csound sounds with and without the UDP server. It’s a small enough difference that I sometimes think I’m just imagining it because it sounds good either way and I think this is mostly just a case of me overthinking things. The UDP server is fantastic and adds a lot of very useful features to Csound so I’m certainly not complaining about its sound quality. However, particularly if I’m working with very short sounds, I subjectively prefer the way Csound sounds without the UDP server so I just wanted to confirm what the current options are for working with OSC. Thanks, Adam
|
| Date | 2025-12-03 06:42 |
| From | Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
|
Hi Adam,
yes, the OSC plugin opcodes are not in the beta releases, but the plans are to include them as before. It just needs to be added to the CI script.
best
Prof. Victor Lazzarini
Maynooth University
Ireland
On 3 Dec 2025, at 00:53, Adam Willetts <adam@ethermap.org> wrote:
|
| Date | 2026-01-12 03:09 |
| From | Adam Willetts |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
| Hi, Thank you for including the OSC plugin opcodes in a recent beta release. I’ve just tried the first overload of the plugin version of OSClisten and it doesn’t seem to work if Csound 7 variable syntax is used for the xdata/output variables. The input variables all work with Csound 7 syntax and everything works fine if the old variable syntax is used for the xdata/output variables. Thanks, Adam
|
| Date | 2026-01-12 06:41 |
| From | vlz |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
The OSClisten with outputs is only used with the UDP server OSC (it doesn't take a handle), the OSC opcodes from libosc.dylib have not changed. The idea was to make the new version distinct. Prof. Victor Lazzarini Maynooth University Ireland On 12 Jan 2026, at 03:09, Adam Willetts <adam@ethermap.org> wrote:
|
| Date | 2026-01-14 22:50 |
| From | Adam Willetts |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
| Hi, Yes, that’s one of several ways the UDP server OSClisten improves on the plugin versions and I agree about keeping the new version distinct. My first email wasn't very clear, sorry. I was talking about the first overload of the plugin version of OSClisten that, unlike most other opcodes, places outputs on the right hand side of the operation like inputs. In the manual they are shown as [, xdata1, xdata2, …]. These variables only seem to work using the old variable syntax. In the following example instr 1 works but instr 2 causes a segmentation fault with the error message: INIT ERROR in instr 2 (opcode OSClisten) line 24: argument list inconsistent with format string oscport@global:i = OSCinit(10000) instr 1 k1 init 0 status:k = OSClisten(oscport, "/controller", "f", k1) endin instr 2 one:k init 0 status:k = OSClisten(oscport, "/controller", "f", one) endin ;schedule(1, 0, -1) schedule(2, 0, -1) Thanks, Adam
|
| Date | 2026-01-14 23:42 |
| From | vlz |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
Thanks for letting me. It shouldn't be the case, let me have a look at what's going on. Prof. Victor Lazzarini Maynooth University Ireland On 14 Jan 2026, at 22:50, Adam Willetts <adam@ethermap.org> wrote:
|
| Date | 2026-01-15 00:07 |
| From | Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
yes, the code had never been updated to use the type system to check the argument types. It still relied on variable names for that (it must be something like 20-year old code that was never touched). I’ve sent in a PR with a fix. ======================== Prof. Victor Lazzarini Maynooth University Ireland > On 14 Jan 2026, at 22:50, Adam Willetts |
| Date | 2026-01-16 04:43 |
| From | Adam Willetts |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
| Hi Victor, Thanks for the quick fix. Everything is working as expected now. Thanks, Adam
|
| Date | 2026-01-16 06:38 |
| From | Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE> |
| Subject | Re: [Csnd] [EXTERNAL] [Csnd] OSC in Csound 7 |
|
Thanks for confirming, that's great. Prof. Victor Lazzarini
Maynooth University
Ireland
On 16 Jan 2026, at 04:43, Adam Willetts <adam@ethermap.org> wrote:
|