Hi, I was hoping to improve my use of the Csound instrument naming conventions, I still use integer numbers most of the time, but I realise the 6.12 manual doesn't say more than the use of integers. I'm aware you can use strings, but also you can use decimals right? What are the complete rules? Are they in the manual somewhere other than in the entry for "instr"?

And are there rules to what the strong can contain if you use a string? Can it contain non-alphernumeric characters?

A bit of experimenting suggests that you can't enclose a string in quotes when naming an instrument with a string, so you also can't use non alphanumeric characters in the name string, aside from "_" as far as I can tell. Names with "_" are fine in the orchestra, but don't seem to work when called from the score.

On Sun, 12 May 2019, 16:59 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:

Hi, I was hoping to improve my use of the Csound instrument naming conventions, I still use integer numbers most of the time, but I realise the 6.12 manual doesn't say more than the use of integers. I'm aware you can use strings, but also you can use decimals right? What are the complete rules? Are they in the manual somewhere other than in the entry for "instr"?

And are there rules to what the strong can contain if you use a string? Can it contain non-alphernumeric characters?

Names and numbers behave differently.

Fractional numbers, e.g. 1.1, 1.2, indicate different "instances" of
the instrument. These can be used to realize tied notes, etc. In other
words:

i 1.1 1 2 3 4
i 1.1 2 2 5 6

ties 1.1 at time 1 to 1.1 at time 2. "Tieing" means the release
segment of the envelope is not activated for the first note in the tie
(I think), and the init stage of the second note in the tie should be
skipped using tigoto. See the manual page for the "i" statement for
more details. Note that tieing doesn't work for MIDI performance.

Names are one name for all instances. Therefore there is no advantage
to declaring multiple names in one instr statement.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Sun, May 12, 2019 at 12:29 PM Peter Burgess
<pete.soundtechnician@gmail.com> wrote:
>
> Also, how are the multiple instrument decelerations meant to work? Like "instr foo, bar, etc". It seems when I declare "instr foo, bar", the processing definition is only "bar", the last name... How is this meant to be used and what is the advantage of declaring multiple instr names at once? I feel like this could potentially be something really useful I've previously overlooked, but I'm not sure what it is yet
>
> On Sun, 12 May 2019, 17:19 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>
>> A bit of experimenting suggests that you can't enclose a string in quotes when naming an instrument with a string, so you also can't use non alphanumeric characters in the name string, aside from "_" as far as I can tell. Names with "_" are fine in the orchestra, but don't seem to work when called from the score.
>>
>> On Sun, 12 May 2019, 16:59 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>>
>>> Hi, I was hoping to improve my use of the Csound instrument naming conventions, I still use integer numbers most of the time, but I realise the 6.12 manual doesn't say more than the use of integers. I'm aware you can use strings, but also you can use decimals right? What are the complete rules? Are they in the manual somewhere other than in the entry for "instr"?
>>>
>>> And are there rules to what the strong can contain if you use a string? Can it contain non-alphernumeric characters?
>
> 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

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

Fractional numbers are allowed in any events that are not MIDI-originated. They do no necessarily need to be from the score.

RT events or events scheduled in the orchestra can use them too.

In fact, it is possible to parse MIDI and schedule fractional instruments as required.

There is an example in the manual in one of the fluid opcode pages.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 13 May 2019, at 16:43, Peter Burgess <pete.soundtechnician@gmail.com> wrote:

Oh I see, thanks a lot. I didn't realise the instr number decimals were only in the score. That makes sense, and I can already see me making use of that. I'll read more about it when I get home.

So the fact you can pass multiple comma separated strings when defining an instrument is interesting... It feels like it could be repurposed for something good... Like for instance, has there ever been consideration for adding namespaces within the orchestra + score? Or is this already possible maybe?

On Sun, 12 May 2019, 18:25 Michael Gogins, <michael.gogins@gmail.com> wrote:

Names and numbers behave differently.

Fractional numbers, e.g. 1.1, 1.2, indicate different "instances" of
the instrument. These can be used to realize tied notes, etc. In other
words:

i 1.1 1 2 3 4
i 1.1 2 2 5 6

ties 1.1 at time 1 to 1.1 at time 2. "Tieing" means the release
segment of the envelope is not activated for the first note in the tie
(I think), and the init stage of the second note in the tie should be
skipped using tigoto. See the manual page for the "i" statement for
more details. Note that tieing doesn't work for MIDI performance.

Names are one name for all instances. Therefore there is no advantage
to declaring multiple names in one instr statement.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Sun, May 12, 2019 at 12:29 PM Peter Burgess
<pete.soundtechnician@gmail.com> wrote:
>
> Also, how are the multiple instrument decelerations meant to work? Like "instr foo, bar, etc". It seems when I declare "instr foo, bar", the processing definition is only "bar", the last name... How is this meant to be used and what is the advantage of declaring multiple instr names at once? I feel like this could potentially be something really useful I've previously overlooked, but I'm not sure what it is yet
>
> On Sun, 12 May 2019, 17:19 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>
>> A bit of experimenting suggests that you can't enclose a string in quotes when naming an instrument with a string, so you also can't use non alphanumeric characters in the name string, aside from "_" as far as I can tell. Names with "_" are fine in the orchestra, but don't seem to work when called from the score.
>>
>> On Sun, 12 May 2019, 16:59 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>>
>>> Hi, I was hoping to improve my use of the Csound instrument naming conventions, I still use integer numbers most of the time, but I realise the 6.12 manual doesn't say more than the use of integers. I'm aware you can use strings, but also you can use decimals right? What are the complete rules? Are they in the manual somewhere other than in the entry for "instr"?
>>>
>>> And are there rules to what the strong can contain if you use a string? Can it contain non-alphernumeric characters?
>
> 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

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

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

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

That's an excellent example for study.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 13 May 2019, at 18:16, Dave Seidel <dave.seidel@gmail.com> wrote:

Yes, this is something I do in my Implication Organ -- I generate fractional instrument numbers on the fly based on the incoming MIDI note. This makes it easy to find and turn off the proper instance when I receive the MIDI release. See  https://github.com/DaveSeidel/music-src/tree/master/implication-organ  

On Mon, May 13, 2019 at 1:11 PM Victor Lazzarini <Victor.Lazzarini@mu.ie> wrote:

Fractional numbers are allowed in any events that are not MIDI-originated. They do no necessarily need to be from the score.

RT events or events scheduled in the orchestra can use them too.

In fact, it is possible to parse MIDI and schedule fractional instruments as required.

There is an example in the manual in one of the fluid opcode pages.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 13 May 2019, at 16:43, Peter Burgess <pete.soundtechnician@gmail.com> wrote:

Oh I see, thanks a lot. I didn't realise the instr number decimals were only in the score. That makes sense, and I can already see me making use of that. I'll read more about it when I get home.

So the fact you can pass multiple comma separated strings when defining an instrument is interesting... It feels like it could be repurposed for something good... Like for instance, has there ever been consideration for adding namespaces within the orchestra + score? Or is this already possible maybe?

On Sun, 12 May 2019, 18:25 Michael Gogins, <michael.gogins@gmail.com> wrote:

Names and numbers behave differently.

Fractional numbers, e.g. 1.1, 1.2, indicate different "instances" of
the instrument. These can be used to realize tied notes, etc. In other
words:

i 1.1 1 2 3 4
i 1.1 2 2 5 6

ties 1.1 at time 1 to 1.1 at time 2. "Tieing" means the release
segment of the envelope is not activated for the first note in the tie
(I think), and the init stage of the second note in the tie should be
skipped using tigoto. See the manual page for the "i" statement for
more details. Note that tieing doesn't work for MIDI performance.

Names are one name for all instances. Therefore there is no advantage
to declaring multiple names in one instr statement.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Sun, May 12, 2019 at 12:29 PM Peter Burgess
<pete.soundtechnician@gmail.com> wrote:
>
> Also, how are the multiple instrument decelerations meant to work? Like "instr foo, bar, etc". It seems when I declare "instr foo, bar", the processing definition is only "bar", the last name... How is this meant to be used and what is the advantage of declaring multiple instr names at once? I feel like this could potentially be something really useful I've previously overlooked, but I'm not sure what it is yet
>
> On Sun, 12 May 2019, 17:19 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>
>> A bit of experimenting suggests that you can't enclose a string in quotes when naming an instrument with a string, so you also can't use non alphanumeric characters in the name string, aside from "_" as far as I can tell. Names with "_" are fine in the orchestra, but don't seem to work when called from the score.
>>
>> On Sun, 12 May 2019, 16:59 Peter Burgess, <pete.soundtechnician@gmail.com> wrote:
>>>
>>> Hi, I was hoping to improve my use of the Csound instrument naming conventions, I still use integer numbers most of the time, but I realise the 6.12 manual doesn't say more than the use of integers. I'm aware you can use strings, but also you can use decimals right? What are the complete rules? Are they in the manual somewhere other than in the entry for "instr"?
>>>
>>> And are there rules to what the strong can contain if you use a string? Can it contain non-alphernumeric characters?
>
> 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

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

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

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

--

http://mysterybear.net

https://soundcloud.com/mysterybear

https://mysterybear.bandcamp.com

https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA

http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz

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

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