score durations #647
Comments
|
excellent
*- Dr.B*
*Dr. Richard Boulanger*
Professor
Electronic Production and Design
*Berklee College of Music*
Professional Writing & Technology Division
On Sun, Oct 16, 2022 at 12:09 PM Menno Knevel ***@***.***>
wrote:
… put something somewhere somehow in the manual regarding this:
I should have completed: it will run forever like in the first example.
Why?
1 - in the first example, there is no numeric score, Csound runs forever. The scheduled instr 1 with p3=-1 will
run forever.
2 - in the second example, the first instr 1 with p3=-1 instance is immediately replaced by the instance with p3=1
3 - in the third example, the score runs to the end before any performance can be run.
4 - in the fourth example the score requires to run an f statement at time z (which is the end of times as far as we are concerned)
so Csound has to run until then. The i1 0 -1 then turns instrument 1 indefinitely on.
========================
Prof. Victor Lazzarini
Maynooth University
Ireland
> On 16 Oct 2022, at 16:39, Victor Lazzarini ***@***.******@***.***)> wrote:
>
> If you run one single instance of instr 1 with -1 it will run until Csound stops running. So the CSD
>
> <CsoundSynthesizer>
> <CsOptions>
> -odac
> </CsOptions>
> <CsInstruments>
> instr 1
> out oscili(0dbfs, A4)
> endin
> schedule(1,0,-1)
> </CsInstruments>
> <CsScore>
> </CsScore>
> </CsoundSynthesizer>
>
> Will run forever playing a 440Hz sine wave at full amplitude. But in this one
>
> <CsoundSynthesizer>
> <CsOptions>
> -odac
> </CsOptions>
> <CsInstruments>
> instr 1
> out oscili(0dbfs, A4)
> endin
> schedule(1,0,-1)
> schedule(1,0,1)
> </CsInstruments>
> <CsScore>
> </CsScore>
> </CsoundSynthesizer>
>
> the second instance will take over and run for 1 second.
>
> Equally
>
> <CsoundSynthesizer>
> <CsOptions>
> -odac
> </CsOptions>
> <CsInstruments>
> instr 1
> out oscili(0dbfs, A4)
> endin
> </CsInstruments>
> <CsScore>
> i1 0 -1
> </CsScore>
> </CsoundSynthesizer>
>
> will not even run because the performance will end immediately. But if you add f0 z
>
>
> <CsoundSynthesizer>
> <CsOptions>
> -odac
> </CsOptions>
> <CsInstruments>
> instr 1
> out oscili(0dbfs, A4)
> endin
> </CsInstruments>
> <CsScore>
> f0 z
> i1 0 -1
> </CsScore>
> </CsoundSynthesizer>
>
> ========================
> Prof. Victor Lazzarini
> Maynooth University
> Ireland
—
Reply to this email directly, view it on GitHub
<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvaXNzdWVzLzY0Nw==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=VmFTMkZtRzMybGJqcmE3VnBBcjBoZS96U24vWTN0SFo2ZE5vTlhjZCtLST0=&h=0c1af01d2aff4bf98d0deeeb7ebead7b&s=AVNPUEhUT0NFTkNSWVBUSVZ+CzEl059Ym1RlqwKl3ZhNfC+dR2N5IDL9CUAdMA/6tA==>,
or unsubscribe
<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQUxXWUZRRDdQQVdESTVMRE1TUUtCVFdEUVNDNUFOQ05GU002QUFBQUFBUkdNNzZJRQ==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=YldWMHJJaUFTZWdNTGhURURIVlJsb3pxS3FORU5OdkdaNHdLMERjaEVjdz0=&h=0c1af01d2aff4bf98d0deeeb7ebead7b&s=AVNPUEhUT0NFTkNSWVBUSVZ+CzEl059Ym1RlqwKl3ZhNfC+dR2N5IDL9CUAdMA/6tA==>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
The best place to integrate this knowledge would be the on the manual page of the 'i statement': https://csound.com/manual/i.html Look into: links from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
put something somewhere somehow in the manual regarding this:
The text was updated successfully, but these errors were encountered: