Csound Csound-dev Csound-tekno Search About

[Csnd] Event and event_i opcodes

Date2011-09-19 19:51
FromJohn Clements
Subject[Csnd] Event and event_i opcodes
Am I correct in assuming that event creates score events at krate, with k-parameters?  And that event_i does this at i-rate?  I noticed that instruments activated by event_i within another instrument will activate at initialization and stay on (when containing ihold).  I am trying to turn on the instrument from an incoming signal, which works, but when I use event and ihold, it only passes the first k-rate signal it receives, and when I use event_i the instrument turns on at initialization.  Does anyone have any suggestions and pointers to share on using instruments to activate others with event?  

 Will an instrument, activated by event_i, sustained by ihold, be able to pass on statements at krate, using event, to another instrument?  

Thank you so much for any help on this. 

John Clements

Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


Date2011-09-19 19:55
FromAdam Puckett
SubjectRe: [Csnd] Event and event_i opcodes
Hi John,

Yes, your assumption is correct. You could try using the reinit opcode
to change even i-signals at k-rate.

On 9/19/11, John Clements  wrote:
> Am I correct in assuming that event creates score events at krate, with
> k-parameters?  And that event_i does this at i-rate?  I noticed that
> instruments activated by event_i within another instrument will activate at
> initialization and stay on (when containing ihold).  I am trying to turn on
> the instrument from an incoming signal, which works, but when I use event
> and ihold, it only passes the first k-rate signal it receives, and when I
> use event_i the instrument turns on at initialization.  Does anyone have any
> suggestions and pointers to share on using instruments to activate others
> with event?
>
>  Will an instrument, activated by event_i, sustained by ihold, be able to
> pass on statements at krate, using event, to another instrument?
>
> Thank you so much for any help on this.
>
> John Clements
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2011-09-19 23:24
FromJohn Clements
SubjectRe: [Csnd] Event and event_i opcodes
Thanks Adam, very helpful, indeed... So it is event that is holding my kvalues back, similar to schedkwhen...

Event_i does not do this, but it starts my instrument at init pass, which is not desirable since I intend to start/stop it with another instrument that is listening for control signal.  As I would be using reinit for krate signals, rather than any audio generating instruments, discontinuity on reinit should not cause issues, right?

Thank you very much,

John Clements

On Sep 19, 2011, at 2:55 PM, Adam Puckett  wrote:

> Hi John,
> 
> Yes, your assumption is correct. You could try using the reinit opcode
> to change even i-signals at k-rate.
> 
> On 9/19/11, John Clements  wrote:
>> Am I correct in assuming that event creates score events at krate, with
>> k-parameters?  And that event_i does this at i-rate?  I noticed that
>> instruments activated by event_i within another instrument will activate at
>> initialization and stay on (when containing ihold).  I am trying to turn on
>> the instrument from an incoming signal, which works, but when I use event
>> and ihold, it only passes the first k-rate signal it receives, and when I
>> use event_i the instrument turns on at initialization.  Does anyone have any
>> suggestions and pointers to share on using instruments to activate others
>> with event?
>> 
>> Will an instrument, activated by event_i, sustained by ihold, be able to
>> pass on statements at krate, using event, to another instrument?
>> 
>> Thank you so much for any help on this.
>> 
>> John Clements
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>> 
>> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


Date2011-09-20 00:36
From"Colman O'Reilly"
SubjectRe: [Csnd] Event and event_i opcodes
John, you could probably do something like this:

if (gkevent == 1) then

gkevent = 7

event "i", 2, 0, 60000

endif



So, from your other instrument you would 'trigger' a value of "gkevent" as 1 - and then by immediately setting it to another value it would avoid additional event statements from being written on other k cycles.


If your controlling instrument is sending 0 and 1 values, you could also substitute the "event" statement with a "turnoff2" line, so if "gkevent == 0" that would effectively do the 'one shot' on and off I think you're looking for (if I read what you are asking correctly).


Hope that helped!

C



On Mon, Sep 19, 2011 at 6:24 PM, John Clements <jclements77@gmail.com> wrote:
Thanks Adam, very helpful, indeed... So it is event that is holding my kvalues back, similar to schedkwhen...

Event_i does not do this, but it starts my instrument at init pass, which is not desirable since I intend to start/stop it with another instrument that is listening for control signal.  As I would be using reinit for krate signals, rather than any audio generating instruments, discontinuity on reinit should not cause issues, right?

Thank you very much,

John Clements

On Sep 19, 2011, at 2:55 PM, Adam Puckett <adotsdothmusic@gmail.com> wrote:

> Hi John,
>
> Yes, your assumption is correct. You could try using the reinit opcode
> to change even i-signals at k-rate.
>
> On 9/19/11, John Clements <jclements77@gmail.com> wrote:
>> Am I correct in assuming that event creates score events at krate, with
>> k-parameters?  And that event_i does this at i-rate?  I noticed that
>> instruments activated by event_i within another instrument will activate at
>> initialization and stay on (when containing ihold).  I am trying to turn on
>> the instrument from an incoming signal, which works, but when I use event
>> and ihold, it only passes the first k-rate signal it receives, and when I
>> use event_i the instrument turns on at initialization.  Does anyone have any
>> suggestions and pointers to share on using instruments to activate others
>> with event?
>>
>> Will an instrument, activated by event_i, sustained by ihold, be able to
>> pass on statements at krate, using event, to another instrument?
>>
>> Thank you so much for any help on this.
>>
>> John Clements
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>


Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




--




Date2011-09-20 03:57
FromJohn Clements
SubjectRe: [Csnd] Event and event_i opcodes
Thanks Colman!  This is very helpful... actually having a problem with the instrument triggered by event -- it only passes the first krate value, and then stays constant.  Event_i allows the krate variables to update properly, but triggers the event_i instantly when in an always on or turned on instrument...even when in an if-then condition that is activated by outside controller.  The control instrument... Wondering if gating the control instrument would be my next step... Has anyone else experienced this behavior with event and event_i when used in a similar way?

Still puzzling 

John Clements

On Sep 19, 2011, at 7:36 PM, "Colman O'Reilly" <colma noreilly@gmail.com> wrote:

John, you could probably do something like this:

if (gkevent == 1) then

gkevent = 7

event "i", 2, 0, 60000

endif



So, from your other instrument you would 'trigger' a value of "gkevent" as 1 - and then by immediately setting it to another value it would avoid additional event statements from being written on other k cycles.


If your controlling instrument is sending 0 and 1 values, you could also substitute the "event" statement with a "turnoff2" line, so if "gkevent == 0" that would effectively do the 'one shot' on and off I think you're looking for (if I read what you are asking correctly).


Hope that helped!

C



On Mon, Sep 19, 2011 at 6:24 PM, John Clements <jclements77@gmail.com> wrote:
Thanks Adam, very helpful, indeed... So it is event that is holding my kvalues back, similar to schedkwhen...

Event_i does not do this, but it starts my instrument at init pass, which is not desirable since I intend to start/stop it with another instrument that is listening for control signal.  As I would be using reinit for krate signals, rather than any audio generating instruments, discontinuity on reinit should not cause issues, right?

Thank you very much,

John Clements

On Sep 19, 2011, at 2:55 PM, Adam Puckett <adotsdothmusic@gmail.com> wrote:

> Hi John,
>
> Yes, your assumption is correct. You could try using the reinit opcode
> to change even i-signals at k-rate.
>
> On 9/19/11, John Clements <jclements77@gmail.com> wrote:
>> Am I correct in assuming that event creates score events at krate, with
>> k-parameters?  And that event_i does this at i-rate?  I noticed that
>> instruments activated by event_i within another instrument will activate at
>> initialization and stay on (when containing ihold).  I am trying to turn on
>> the instrument from an incoming signal, which works, but when I use event
>> and ihold, it only passes the first k-rate signal it receives, and when I
>> use event_i the instrument turns on at initialization.  Does anyone have any
>> suggestions and pointers to share on using instruments to activate others
>> with event?
>>
>> Will an instrument, activated by event_i, sustained by ihold, be able to
>> pass on statements at krate, using event, to another instrument?
>>
>> Thank you so much for any help on this.
>>
>> John Clements
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>


Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




--




Date2011-09-20 04:32
Frommatt ingalls
SubjectRe: [Csnd] Event and event_i opcodes
are you saying you want the p-fields of the triggered instrument to change at k-rate, controlled by the first instrument?
you could try subinstr opcode (at at least one one time allowed you to this)

or probably better is just make a user-defined opcode


On Sep 19, 2011, at 7:57 PM, John Clements wrote:

Thanks Colman!  This is very helpful... actually having a problem with the instrument triggered by event -- it only passes the first krate value, and then stays constant.  Event_i allows the krate variables to update properly, but triggers the event_i instantly when in an always on or turned on instrument...even when in an if-then condition that is activated by outside controller.  The control instrument... Wondering if gating the control instrument would be my next step... Has anyone else experienced this behavior with event and event_i when used in a similar way?

Still puzzling 

John Clements

On Sep 19, 2011, at 7:36 PM, "Colman O'Reilly" <colmanoreilly@gmail.com> wrote:

John, you could probably do something like this:

if (gkevent == 1) then
gkevent = 7
event "i", 2, 0, 60000
endif


So, from your other instrument you would 'trigger' a value of "gkevent" as 1 - and then by immediately setting it to another value it would avoid additional event statements from being written on other k cycles.

If your controlling instrument is sending 0 and 1 values, you could also substitute the "event" statement with a "turnoff2" line, so if "gkevent == 0" that would effectively do the 'one shot' on and off I think you're looking for (if I read what you are asking correctly).

Hope that helped!
C


On Mon, Sep 19, 2011 at 6:24 PM, John Clements <jclements77@gmail.com> wrote:
Thanks Adam, very helpful, indeed... So it is event that is holding my kvalues back, similar to schedkwhen...

Event_i does not do this, but it starts my instrument at init pass, which is not desirable since I intend to start/stop it with another instrument that is listening for control signal.  As I would be using reinit for krate signals, rather than any audio generating instruments, discontinuity on reinit should not cause issues, right?

Thank you very much,

John Clements

On Sep 19, 2011, at 2:55 PM, Adam Puckett <adotsdothmusic@gmail.com> wrote:

> Hi John,
>
> Yes, your assumption is correct. You could try using the reinit opcode
> to change even i-signals at k-rate.
>
> On 9/19/11, John Clements <jclements77@gmail.com> wrote:
>> Am I correct in assuming that event creates score events at krate, with
>> k-parameters?  And that event_i does this at i-rate?  I noticed that
>> instruments activated by event_i within another instrument will activate at
>> initialization and stay on (when containing ihold).  I am trying to turn on
>> the instrument from an incoming signal, which works, but when I use event
>> and ihold, it only passes the first k-rate signal it receives, and when I
>> use event_i the instrument turns on at initialization.  Does anyone have any
>> suggestions and pointers to share on using instruments to activate others
>> with event?
>>
>> Will an instrument, activated by event_i, sustained by ihold, be able to
>> pass on statements at krate, using event, to another instrument?
>>
>> Thank you so much for any help on this.
>>
>> John Clements
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>


Send bugs reports to the Sourceforge bug tracker
           https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




--





Date2011-09-20 08:19
Fromjoachim heintz
SubjectRe: [Csnd] Event and event_i opcodes
hi john -

yes, i work a lot with this triggering (both with event_i and with
event). perhaps i can help. i must admit that i do not exactly
understand your problem. can you send us a csd as illustration?

best -

	joachim

Am 20.09.2011 04:57, schrieb John Clements:
> Thanks Colman!  This is very helpful... actually having a problem with
> the instrument triggered by event -- it only passes the first krate
> value, and then stays constant.  Event_i allows the krate variables to
> update properly, but triggers the event_i instantly when in an always on
> or turned on instrument...even when in an if-then condition that is
> activated by outside controller.  The control instrument... Wondering if
> gating the control instrument would be my next step... Has anyone else
> experienced this behavior with event and event_i when used in a similar way?
> 
> Still puzzling 
> 
> John Clements
> 
> On Sep 19, 2011, at 7:36 PM, "Colman O'Reilly"  > wrote:
> 
>> John, you could probably do something like this:
>>
>> if (gkevent == 1) then
>>
>> gkevent = 7
>>
>> event "i", 2, 0, 60000
>>
>> endif
>>
>>
>>
>> So, from your other instrument you would 'trigger' a value of
>> "gkevent" as 1 - and then by immediately setting it to another value
>> it would avoid additional event statements from being written on other
>> k cycles.
>>
>>
>> If your controlling instrument is sending 0 and 1 values, you could
>> also substitute the "event" statement with a "turnoff2" line, so if
>> "gkevent == 0" that would effectively do the 'one shot' on and off I
>> think you're looking for (if I read what you are asking correctly).
>>
>>
>> Hope that helped!
>>
>> C
>>
>>
>>
>> On Mon, Sep 19, 2011 at 6:24 PM, John Clements
>> <jclements77@gmail.com
>> > wrote:
>>
>>     Thanks Adam, very helpful, indeed... So it is event that is
>>     holding my kvalues back, similar to schedkwhen...
>>
>>     Event_i does not do this, but it starts my instrument at init
>>     pass, which is not desirable since I intend to start/stop it with
>>     another instrument that is listening for control signal.  As I
>>     would be using reinit for krate signals, rather than any audio
>>     generating instruments, discontinuity on reinit should not cause
>>     issues, right?
>>
>>     Thank you very much,
>>
>>     John Clements
>>
>>     On Sep 19, 2011, at 2:55 PM, Adam Puckett
>>     <adotsdothmusic@gmail.com
>>     > wrote:
>>
>>     > Hi John,
>>     >
>>     > Yes, your assumption is correct. You could try using the reinit
>>     opcode
>>     > to change even i-signals at k-rate.
>>     >
>>     > On 9/19/11, John Clements
>>     <jclements77@gmail.com
>>     > wrote:
>>     >> Am I correct in assuming that event creates score events at
>>     krate, with
>>     >> k-parameters?  And that event_i does this at i-rate?  I noticed
>>     that
>>     >> instruments activated by event_i within another instrument will
>>     activate at
>>     >> initialization and stay on (when containing ihold).  I am
>>     trying to turn on
>>     >> the instrument from an incoming signal, which works, but when I
>>     use event
>>     >> and ihold, it only passes the first k-rate signal it receives,
>>     and when I
>>     >> use event_i the instrument turns on at initialization.  Does
>>     anyone have any
>>     >> suggestions and pointers to share on using instruments to
>>     activate others
>>     >> with event?
>>     >>
>>     >> Will an instrument, activated by event_i, sustained by ihold,
>>     be able to
>>     >> pass on statements at krate, using event, to another instrument?
>>     >>
>>     >> Thank you so much for any help on this.
>>     >>
>>     >> John Clements
>>     >>
>>     >> Send bugs reports to the Sourceforge bug tracker
>>     >>          
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     >> Discussions of bugs and features can be posted here
>>     >> To unsubscribe, send email
>>     sympa@lists.bath.ac.uk
>>      with body "unsubscribe
>>     >> csound"
>>     >>
>>     >>
>>     >
>>     >
>>     > Send bugs reports to the Sourceforge bug tracker
>>     >          
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     > Discussions of bugs and features can be posted here
>>     > To unsubscribe, send email
>>     sympa@lists.bath.ac.uk
>>      with body "unsubscribe csound"
>>     >
>>
>>
>>     Send bugs reports to the Sourceforge bug tracker
>>              
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     Discussions of bugs and features can be posted here
>>     To unsubscribe, send email
>>     sympa@lists.bath.ac.uk
>>      with body "unsubscribe csound"
>>
>>
>>
>>
>> -- 
>> Colman O'Reilly
>> | colman@csoundforlive.com
>>  |
>> www.colmanoreilly.com
>> 
>>
>>
>>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"