Csound Csound-dev Csound-tekno Search About

is there a limit in the number of event_i statements allowed in a performance?

Date2016-02-03 19:01
FromKarin Daum
Subjectis there a limit in the number of event_i statements allowed in a performance?
As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language. 

In order to put the small sound fragments together I intend to use the event_i statement like this

ipnt		= irnd+giMaxVow*irnd1
ibegin	+= iend
itablen 	= ftlen(giVow[ipnt])
iend		= itablen/sr
	event_i	"i",2,ibegin,iend,0.1,itablen,ipnt,1
the next event will be triggered when the previous has finished
I just tested it and it works as it should. 

Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?    

Cheers,

Karin

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

Date2016-02-03 19:22
Fromjpff
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?
I have not tried this but I expet no problems
==John


On Wed, 3 Feb 2016, Karin Daum wrote:

> As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language.
>
> In order to put the small sound fragments together I intend to use the event_i statement like this
>
> ipnt		= irnd+giMaxVow*irnd1
> ibegin	+= iend
> itablen 	= ftlen(giVow[ipnt])
> iend		= itablen/sr
> 	event_i	"i",2,ibegin,iend,0.1,itablen,ipnt,1
> the next event will be triggered when the previous has finished
> I just tested it and it works as it should.
>
> Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?
>
> Cheers,
>
> Karin
>
> 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

Date2016-02-03 19:35
FromGuillermo Senna
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?
Recently I did something with Midi and loops. Every key pressed on a 
Midi controller would trigger a loop that counted to 128 and in every 
pass it would chnget a bunch of channels and then execute an event_i 
with the gathered data.

In the end I realized my problem was CPU power. If I pressed more than 
10 keys simultaneously (10*128), sound would stop and CPU use would 
escalate to 100%. This was with an Intel i3 4150 CPU.

I know this is not what you've asked really, but maybe it serves as a 
reference to someone reading this regarding event_i events.

On 03/02/16 16:22, jpff wrote:
> I have not tried this but I expet no problems
> ==John
>
>
> On Wed, 3 Feb 2016, Karin Daum wrote:
>
>> As my first exercise with Csound I'm writing something like a "word 
>> and phrase generator" by using a library of short sound files for the 
>> vocals and consonants stored in function tables. These pieces of 
>> sound will then be randomly combined to "words"  which then will be 
>> combined to "sentences"... This is nothing you can do with speech 
>> programs because these words are in general not existing in a given 
>> language - They will only follow certain statistics of a language.
>>
>> In order to put the small sound fragments together I intend to use 
>> the event_i statement like this
>>
>> ipnt        = irnd+giMaxVow*irnd1
>> ibegin    += iend
>> itablen     = ftlen(giVow[ipnt])
>> iend        = itablen/sr
>>     event_i    "i",2,ibegin,iend,0.1,itablen,ipnt,1
>> the next event will be triggered when the previous has finished
>> I just tested it and it works as it should.
>>
>> Per second this means about 6-8 consecutive event_i statement or for 
>> a performance of 30 minutes I would need something like 10000-20000 
>> event_i statement. Is this a problem?
>>
>> Cheers,
>>
>> Karin
>>
>> 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

Date2016-02-03 20:05
FromRory Walsh
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?

I've hit CPU issues when triggering about 50 or so instruments a second. 6-8 should be fine I think.

On 3 Feb 2016 19:36, "Guillermo Senna" <gsenna@gmail.com> wrote:
Recently I did something with Midi and loops. Every key pressed on a Midi controller would trigger a loop that counted to 128 and in every pass it would chnget a bunch of channels and then execute an event_i with the gathered data.

In the end I realized my problem was CPU power. If I pressed more than 10 keys simultaneously (10*128), sound would stop and CPU use would escalate to 100%. This was with an Intel i3 4150 CPU.

I know this is not what you've asked really, but maybe it serves as a reference to someone reading this regarding event_i events.

On 03/02/16 16:22, jpff wrote:
I have not tried this but I expet no problems
==John


On Wed, 3 Feb 2016, Karin Daum wrote:

As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language.

In order to put the small sound fragments together I intend to use the event_i statement like this

ipnt        = irnd+giMaxVow*irnd1
ibegin    += iend
itablen     = ftlen(giVow[ipnt])
iend        = itablen/sr
    event_i    "i",2,ibegin,iend,0.1,itablen,ipnt,1
the next event will be triggered when the previous has finished
I just tested it and it works as it should.

Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?

Cheers,

Karin

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

Date2016-02-03 20:08
FromKarin Daum
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?
thanks, Then I will start the real coding 

Karin

On 3 Feb 2016, at 21:05, Rory Walsh <rorywalsh@EAR.IE> wrote:

I've hit CPU issues when triggering about 50 or so instruments a second. 6-8 should be fine I think.

On 3 Feb 2016 19:36, "Guillermo Senna" <gsenna@gmail.com> wrote:
Recently I did something with Midi and loops. Every key pressed on a Midi controller would trigger a loop that counted to 128 and in every pass it would chnget a bunch of channels and then execute an event_i with the gathered data.

In the end I realized my problem was CPU power. If I pressed more than 10 keys simultaneously (10*128), sound would stop and CPU use would escalate to 100%. This was with an Intel i3 4150 CPU.

I know this is not what you've asked really, but maybe it serves as a reference to someone reading this regarding event_i events.

On 03/02/16 16:22, jpff wrote:
I have not tried this but I expet no problems
==John


On Wed, 3 Feb 2016, Karin Daum wrote:

As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language.

In order to put the small sound fragments together I intend to use the event_i statement like this

ipnt        = irnd+giMaxVow*irnd1
ibegin    += iend
itablen     = ftlen(giVow[ipnt])
iend        = itablen/sr
    event_i    "i",2,ibegin,iend,0.1,itablen,ipnt,1
the next event will be triggered when the previous has finished
I just tested it and it works as it should.

Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?

Cheers,

Karin

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


Date2016-02-03 20:39
FromVictor Lazzarini
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?
It depends on how simple these are, and your CPU power. I have run recursive code generating over 500 events per second in realtime.

On 3 Feb 2016, at 20:05, Rory Walsh <rorywalsh@EAR.IE> wrote:

I've hit CPU issues when triggering about 50 or so instruments a second. 6-8 should be fine I think.

On 3 Feb 2016 19:36, "Guillermo Senna" <gsenna@gmail.com> wrote:
Recently I did something with Midi and loops. Every key pressed on a Midi controller would trigger a loop that counted to 128 and in every pass it would chnget a bunch of channels and then execute an event_i with the gathered data.

In the end I realized my problem was CPU power. If I pressed more than 10 keys simultaneously (10*128), sound would stop and CPU use would escalate to 100%. This was with an Intel i3 4150 CPU.

I know this is not what you've asked really, but maybe it serves as a reference to someone reading this regarding event_i events.

On 03/02/16 16:22, jpff wrote:
I have not tried this but I expet no problems
==John


On Wed, 3 Feb 2016, Karin Daum wrote:

As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language.

In order to put the small sound fragments together I intend to use the event_i statement like this

ipnt        = irnd+giMaxVow*irnd1
ibegin    += iend
itablen     = ftlen(giVow[ipnt])
iend        = itablen/sr
    event_i    "i",2,ibegin,iend,0.1,itablen,ipnt,1
the next event will be triggered when the previous has finished
I just tested it and it works as it should.

Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?

Cheers,

Karin

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

Date2016-02-03 23:07
FromRory Walsh
SubjectRe: is there a limit in the number of event_i statements allowed in a performance?
That's true. Some of the instruments I was using weren't that simple. 

On 3 February 2016 at 20:39, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
It depends on how simple these are, and your CPU power. I have run recursive code generating over 500 events per second in realtime.

On 3 Feb 2016, at 20:05, Rory Walsh <rorywalsh@EAR.IE> wrote:

I've hit CPU issues when triggering about 50 or so instruments a second. 6-8 should be fine I think.

On 3 Feb 2016 19:36, "Guillermo Senna" <gsenna@gmail.com> wrote:
Recently I did something with Midi and loops. Every key pressed on a Midi controller would trigger a loop that counted to 128 and in every pass it would chnget a bunch of channels and then execute an event_i with the gathered data.

In the end I realized my problem was CPU power. If I pressed more than 10 keys simultaneously (10*128), sound would stop and CPU use would escalate to 100%. This was with an Intel i3 4150 CPU.

I know this is not what you've asked really, but maybe it serves as a reference to someone reading this regarding event_i events.

On 03/02/16 16:22, jpff wrote:
I have not tried this but I expet no problems
==John


On Wed, 3 Feb 2016, Karin Daum wrote:

As my first exercise with Csound I'm writing something like a "word and phrase generator" by using a library of short sound files for the vocals and consonants stored in function tables. These pieces of sound will then be randomly combined to "words"  which then will be combined to "sentences"... This is nothing you can do with speech programs because these words are in general not existing in a given language - They will only follow certain statistics of a language.

In order to put the small sound fragments together I intend to use the event_i statement like this

ipnt        = irnd+giMaxVow*irnd1
ibegin    += iend
itablen     = ftlen(giVow[ipnt])
iend        = itablen/sr
    event_i    "i",2,ibegin,iend,0.1,itablen,ipnt,1
the next event will be triggered when the previous has finished
I just tested it and it works as it should.

Per second this means about 6-8 consecutive event_i statement or for a performance of 30 minutes I would need something like 10000-20000 event_i statement. Is this a problem?

Cheers,

Karin

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
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