[Csnd] triglinseg and trigexpseg inconsistency

The Csound Mailinglist
1

Hey hey,
the triggered linseg and expseg opcodes have a name inconsistency and slight mismatch in the manual.

The manual describes the two is "triglinseg" and "trigexpseg", which is whas I would expect. Having had errors with those, I ran csound -z and found:
trigLinseg and trigExpseg .

Either one could be changed to match the other, but I'd personally wish the manual to be correct with the all lowercase spelling. :slight_smile:

Best wishes,

Jeanette

2

What does the manual example use?

3

I think lowercase is the way to go for these. I can fix this and make a PR

4

who’s the author?

Prof. Victor Lazzarini
Maynooth University
Ireland

5

Aug 29 2021, Victor Lazzarini has written:

What does the manual example use?

It uses the capitalised version:
aEnv trigLinseg kTrig, 0, .2, 1, .2, .5, .2, .7, .2, 0
...

Best wiishes,

Jeanette

6

+1

7

So if we change this now we might break people's code.

8

i think it is very recent code and as jeanette mentioned it is written in lowercase in the manual:
https://csound.com/docs/manual/indexframes.html

or having an alias trigExpseg -> trigexpseg?

9

The manual is wrong I think. Should be lower case.

10

Well the manual differs from the manual example, so I don’t know.

11

My bad, I think changing the opcodes to lowercase is a good idea. These aren’t on the wild long…

12

Could just have both, as is done with Butterworth filters

⁣Sent from TypeApp ​

13

That’s also possible. Whatever you think is best. I went be able to anything until tomorrow. :+1:

14

best solution.

Prof. Victor Lazzarini
Maynooth University
Ireland