Hello everybody.
I’m not able to use the ‚triglinseg‘ opcode. is it not part of Csound anymore?
It’s listed in the manual:
https://csound.com/docs/manual/triglinseg.html
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
GitHub · Where software is built
Discussions of bugs and features can be posted here
Hi Philipp,
I just used it the other day. I'm on a Linux install of Csound 6.18. It may be part of the Csound plugins package, if you're install has them separated.
Best wishes,
Jeanette
It's part of Csound core opcodes, but it may be packaged in different ways depending on your platform and version.
Prof. Victor Lazzarini
Maynooth University
Ireland
It’s named trigLinseg (note the upper case L) - I guess we could add an alias?
we should.
Prof. Victor Lazzarini
Maynooth University
Ireland
Mar 11 2025, Rory Walsh has written:
It's named trigLinseg note the upper case L - I guess we could add an
alias?
Hm, it seems that my Csound ignores that. There are a few other opcodes with capital letters and them I use, but I never did with triglinseg. Strange...
The problem may be that in its Manual page, the opcode is spelled all in lower case except in the example, where the L is capitalized. Assuming the capitalization is important, the Manual perhaps should be corrected, or at least made consistent?
Art H.
Csound mailing list Send bugs reports to Discussions of bugs and features can be posted here
Csound will definitely mind that difference
Prof. Victor Lazzarini
Maynooth University
Ireland
At least Webcsound does not accept low case trigLinseg.
I’m +1 for creating an aliases with only lower case letters. I don’t know what the idea behind the opcode name ’trigLinseg’ was, but, in my opinion, this makes Csound inconsistent. Out of my head a can’t remember a other opcode with upper case letters.
All the best,
Philipp
The aliases have already been added to Csound7. There are plenty of examples of Csound opcodes that use uppercase, but I agree that it’s not good practice. In my defence, I wrote these opcodes as external opcodes, and purposely used the upper case to distinguish them from Csound internal opcodes. But I should have changed them back earlier. We have been discussing the lack of consistency among opcode names recently. It would be great to define a style guide, be it snake case, camel case, or whatever for all opcodes.
Great! Can’t wait to move to Csound7.
Sorry, i did not want to sound harsh. Thank you for your work!
Not at all, it’s a very good point. Nothing stopping you from moving to csound7 right now. There are binaries available on the github page, you just need to log in to access them.