[Csnd] Triggering action after arbirary delay
| Date | 2019-02-27 15:24 |
| From | "Jeanette C." |
| Subject | [Csnd] Triggering action after arbirary delay |
Hey hey,
I'd like to trigger an action - using a conditional statement - after an
arbitrary delay. I can see two basic methods: is there perhaps something more
efficient?
1. Query absolute time and compare to desired time (using timek or times).
2. Generate a control-rate impulse, delay it with delayk and use if directly
or changed. (How to best generate that impulse?)
This is for a single action (so no metronome). Did I miss something obvious?
Best wishes and thanks,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s
... And that I know you're out there and I know that you still care <3
(Britney Spears)
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 |
| Date | 2019-02-27 15:29 |
| From | Tarmo Johannes |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
Hi, Or put the action to separate instrument and call it with desired start time (p2)? Tarmo K, 27. veebruar 2019 16:24 Jeanette C. <julien@mail.upb.de> kirjutas: Hey hey, |
| Date | 2019-02-27 15:29 |
| From | Rory Walsh |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
You could also wrap the event in a dedicated instrument and then schedule it using schedule or the event opcodes? On Wed, 27 Feb 2019 at 15:24, Jeanette C. <julien@mail.upb.de> wrote: Hey hey, |
| Date | 2019-02-27 15:35 |
| From | "Jeanette C." |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
Feb 27 2019, Rory Walsh has written:
> You could also wrap the event in a dedicated instrument and then schedule
> it using schedule or the event opcodes?
...
Hi Rory and Johannes,
thanks for your quick reply. Alas, that won't be possible. This code
will probably have to go within a UDO. I should have said, my apologies.
Best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s
... And that I know you're out there and I know that you still care <3
(Britney Spears)
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 |
| Date | 2019-02-27 15:48 |
| From | Rory Walsh |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
Putting it in a UDO shouldn't make any difference. Or am I missing something? I often trigger other instruments from UDOs. On Wed, 27 Feb 2019 at 15:35, Jeanette C. <julien@mail.upb.de> wrote: Feb 27 2019, Rory Walsh has written: |
| Date | 2019-02-27 20:40 |
| From | "Jeanette C." |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
Feb 27 2019, Rory Walsh has written:
> Putting it in a UDO shouldn't make any difference. Or am I missing
> something?
...
It's just that I'd like the UDO to be independent, to be used within any
kind of orchestra. But it's an interesting point, I never thought of
triggering instruments from within a UDO. It's definitely a capability
to keep in mind.
Best wishes and thanks,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s
E-mail my heart and say our love will never die... <3
(Britney Spears)
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 |
| Date | 2019-02-27 21:33 |
| From | Oeyvind Brandtsegg |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
A trick I recently learned from Iain is to use relative instr numbers in these cases. If you use e.g. event "i", p1+1, 0, ... then you will always start the instrument number one higher than the instrument containing the trigger code, and this make it a bit more general. Den ons. 27. feb. 2019 kl. 21:40 skrev Jeanette C. <julien@mail.upb.de>: Feb 27 2019, Rory Walsh has written: Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://crossadaptive.hf.ntnu.no http://gdsp.hf.ntnu.no/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp |
| Date | 2019-02-27 21:43 |
| From | "Jeanette C." |
| Subject | Re: [Csnd] Triggering action after arbirary delay |
Feb 27 2019, Oeyvind Brandtsegg has written: > A trick I recently learned from Iain is to use relative instr numbers in > these cases. > If you use e.g. > event "i", p1+1, 0, ... ... Nice one! Thanks! Best wishes, Jeanette > then you will always start the instrument number one higher than the > instrument containing the trigger code, > and this make it a bit more general. > > Den ons. 27. feb. 2019 kl. 21:40 skrev Jeanette C. |