Score sections (s), and reverb
| Date | 2017-02-16 18:06 |
| From | Sam Smalley |
| Subject | Score sections (s), and reverb |
Hi CSounders,
I'm a relatively new user of CSound, and was wondering how to get reverb (or any signal, really) to carry over between score sections. Here's what my score looks like:
s
t 0 90 2.5 125
;instr Start Dur Amp Freq
i 1 0 0.5 0.2 7.03
i. + . . 7.02
i. . . . 7.03
i. . . . 6.07
i. . . . 6.08
i. . . . 6.00
i. . 0.5 . 5.10
i. . . 0
i. . . 0.2 7.02
i. . . 0
i. . . 0.2 6.07
i. . . 0
i 99 0 6 ;Reverb
/*the reverb gets truncated in order to maintain rhythm, or the rhythm gets elongated
in order to maintain the reverb tail. In this case, the reverb has been truncated*/
s
t 0 90 2.5 125
;instr Start Dur Amp Freq
i 1 0 0.5 0.2 7.00
i . + . . 6.11
i . . . . 7.00
i . . . . 6.03
i . . . . 6.05
i . . . . 5.08
i . . . . 5.07
i . . . . 6.02
i . . . . 6.07
i . . . . 7.00
i . . . . 6.11
i . . . . 7.00
i 99 0 6 ;Reverb
In order to keep rhythmic continuity, I have to truncate the reverb tail. I'm wondering if there is a way to allow the reverb signal to either run in parallel with the score or to ignore score sections so I can add the reverb onto the entire score as a sort of global mix element, rather than having it be confined to a section by section parameter.
Thanks, and let me know if this post is confusing or formatted wrong.
-Sam
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 | 2017-02-16 18:34 |
| From | Emmett Palaima |
| Subject | Re: Score sections (s), and reverb |
You should use global variables. With global variables you can set up the Csound equivalent of a send track, where instruments can pass audio to another instrument which can create the reverb. Check out How to Work with Global Audio Variables in this article: http://write.flossmanuals.net/csound/b-local-and-global-variables/ Hope this helps! On Thu, Feb 16, 2017 at 1:06 PM, Sam Smalley <ssmalley@berklee.edu> wrote: Hi CSounders, |
| Date | 2017-02-16 19:46 |
| From | Oeyvind Brandtsegg |
| Subject | Re: Score sections (s), and reverb |
Agreed, but AFAIK no instrument events can span section boundaries. One way for you would be to render an audio file without reverb, keeping the sections as you wish, then run a separate "add reverb" pass using this audio file as input. Or try organize the score without using sections. 2017-02-16 10:34 GMT-08:00 Emmett Palaima |
| Date | 2017-02-16 20:24 |
| From | Tarmo Johannes |
| Subject | Re: Score sections (s), and reverb |
Or have an alwayson instrument for reverb (you can find it in many examples). Tarmo 16.02.2017 21:46 kirjutas kuupäeval "Oeyvind Brandtsegg" <oyvind.brandtsegg@ntnu.no>: Agreed, |
| Date | 2017-02-16 20:57 |
| From | joachim heintz |
| Subject | Re: Score sections (s), and reverb |
yes, something like:
instr ...
(called by the score)
instr Reverb
...
endin
schedule("Reverb",0,999)
this should work, i guess.
joachim
On 16/02/17 21:24, Tarmo Johannes wrote:
> Or have an alwayson instrument for reverb (you can find it in many
> examples).
>
> Tarmo
>
> 16.02.2017 21:46 kirjutas kuupäeval "Oeyvind Brandtsegg"
> |
| Date | 2017-02-16 21:06 |
| From | Oeyvind Brandtsegg |
| Subject | Re: Score sections (s), and reverb |
Oh I did not know alwayson could actually span across score sections, but tested now and it works. Nice. 2017-02-16 12:24 GMT-08:00 Tarmo Johannes |
| Date | 2017-02-16 21:08 |
| From | Oeyvind Brandtsegg |
| Subject | Re: Score sections (s), and reverb |
... tested that too, and unfortunately, this will extend the first
section for the duration of the scheduled event, then play the next
section, but it will work as expected if you use a negative duration.
schedule("Reverb",0,-1)
2017-02-16 12:57 GMT-08:00 joachim heintz |
| Date | 2017-02-17 10:38 |
| From | thorin kerr |
| Subject | Re: Score sections (s), and reverb |
Or, you can use the b score statement instead of s. Thorin On 17 Feb 2017 7:08 AM, "Oeyvind Brandtsegg" <oyvind.brandtsegg@ntnu.no> wrote: ... tested that too, and unfortunately, this will extend the first |
| Date | 2017-02-17 10:56 |
| From | Emmett Palaima |
| Subject | Re: Score sections (s), and reverb |
Seems like you could also just use the turnon opcode in the orchestra. I am not too familiar with the use of sections in the score since I mostly use Csound for audio processing and instrument design, but it seems like this would work, since it is not tied to score events. Correct me if I am wrong. EG: <CsInstruments> ..... turnon "reverb" instr reverb ..... endin ..... </CsInstruments> <CsScore> ..... On Fri, Feb 17, 2017 at 5:38 AM, thorin kerr <thorin.kerr@gmail.com> wrote:
|
| Date | 2017-02-17 11:58 |
| From | John ff |
| Subject | Re: Score sections (s), and reverb |
Sections last until all notes finish so if I understand correctly reverb cannot span sections. Personally I do not use sections but rather use the b score opcode.
Sent from TypeApp
On 17 Feb 2017, at 10:58, Emmett Palaima <epalaima@BERKLEE.EDU> wrote:
|
| Date | 2017-02-17 13:20 |
| From | Victor Lazzarini |
| Subject | Re: Score sections (s), and reverb |
|
it can't, but you can add a parameter to s to wait until reverb finishes.
Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland
|
| Date | 2017-02-17 13:24 |
| From | joachim heintz |
| Subject | Re: Score sections (s), and reverb |
thanks for testing — good to know!
j
On 16/02/17 22:08, Oeyvind Brandtsegg wrote:
> ... tested that too, and unfortunately, this will extend the first
> section for the duration of the scheduled event, then play the next
> section, but it will work as expected if you use a negative duration.
> schedule("Reverb",0,-1)
>
> 2017-02-16 12:57 GMT-08:00 joachim heintz |