Hey hey,
is there a way to start a score, written with schedule in the orchestra, at a 
certain point? Consider this:

instr Scorer
   schedule "Tone" 0 1 330
   schedule "Tone" 3 1 440
   schedule "Noise" 5 1
endin

Is there an easy, short way to start this score with the Noise instrument at 5 
seconds?

If I'm barking up the wrong tree, this is the scenario. I am developing a long 
piece, mostly created from shorter notes. I'd like to validate the score/piece 
as it develops. For that purpose I don't need to hear the whole piece, but 
only the last few events (instrument calls).

I use schedule inside the orcestray, so global variables can be passed as 
parameters to instruments, thus making the code more readable and manageable.

Thanks for any hints and best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * SoundCloud: https://soundcloud.com/jeanette_c
  * Twitter: https://twitter.com/jeanette_c_s
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

When you need someone, you just turn around and I will be there <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

Hi Jeanette,

There is not away I'm aware of directly since the Csound doesn't know
what you'll do at runtime for event generation.  What I've been
recommending is:

1. Use score generating instruments in the orchestra for composing
soundobjects, phrases, parts, sections, etc.
2. Use notes in the score to schedule larger time organizations
(phrases, parts, sections)
3. Keep -+skip_seconds=xxx in CsOptions and modify if you want to
start rendering from a given start time.

Using just score is handy because -+skip_seconds can be advance like
one would expect in a DAW.  But using score generating instrument is
great for organization and algorithmic composition. Also, if you have
a live coding setup, you can edit and trigger parts and sections
easily while things are running to iterate faster than having to
restart the CSD. I actually found live coding for composing (rather
than performance) made working on a few pieces really pleasant and I
could jump between sections or hear just parts by evaluating code for
parts I wanted to hear.

Hope that helps!
Steven




On Thu, Oct 17, 2019 at 9:01 AM Jeanette C.  wrote:
>
> Hey hey,
> is there a way to start a score, written with schedule in the orchestra, at a
> certain point? Consider this:
>
> instr Scorer
>    schedule "Tone" 0 1 330
>    schedule "Tone" 3 1 440
>    schedule "Noise" 5 1
> endin
>
> Is there an easy, short way to start this score with the Noise instrument at 5
> seconds?
>
> If I'm barking up the wrong tree, this is the scenario. I am developing a long
> piece, mostly created from shorter notes. I'd like to validate the score/piece
> as it develops. For that purpose I don't need to hear the whole piece, but
> only the last few events (instrument calls).
>
> I use schedule inside the orcestray, so global variables can be passed as
> parameters to instruments, thus making the code more readable and manageable.
>
> Thanks for any hints and best wishes,
>
> Jeanette
>
> --
>   * Website: http://juliencoder.de - for summer is a state of sound
>   * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
>   * SoundCloud: https://soundcloud.com/jeanette_c
>   * Twitter: https://twitter.com/jeanette_c_s
>   * Audiobombs: https://www.audiobombs.com/users/jeanette_c
>   * GitHub: https://github.com/jeanette-c
>
> When you need someone, you just turn around and I will be there <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

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

Hi Steven,
thanks for your remarks. For the current organisation of code your manner of 
working is not applicable, but it is something to keep in mind.

Do I remeber correctly that you did live-coding using vim? Searching for 
live-coding and Csound comes up with web-based and highly graphical 
approaches, which are - alas - impossible for me.

Best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * SoundCloud: https://soundcloud.com/jeanette_c
  * Twitter: https://twitter.com/jeanette_c_s
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

When you need someone, you just turn around and I will be there <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

I put together an example in case others might be interested. The
example just plays some arpeggios that start at different times. For
convenience I set the tempo to 120 to make skip_seconds easy to work
with. You can try rendering this as-is, then modifying -+skip_seconds
value to 2, 4, 6, etc. to jump ahead.

For live coding and Vim I use this plugin:

https://github.com/kunstmusik/csound-repl

Documentation is accessible within vim and available to read at:

https://github.com/kunstmusik/csound-repl/blob/master/doc/csound-repl.txt

Sidenote: Forrest has been contributing some great changes for running
Csound from Visual Studio Code. I imagine adding live coding features
in VS Code won't be too difficult.


On Thu, Oct 17, 2019 at 10:12 AM Jeanette C.  wrote:
>
> Hi Steven,
> thanks for your remarks. For the current organisation of code your manner of
> working is not applicable, but it is something to keep in mind.
>
> Do I remeber correctly that you did live-coding using vim? Searching for
> live-coding and Csound comes up with web-based and highly graphical
> approaches, which are - alas - impossible for me.
>
> Best wishes,
>
> Jeanette
>
> --
>   * Website: http://juliencoder.de - for summer is a state of sound
>   * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
>   * SoundCloud: https://soundcloud.com/jeanette_c
>   * Twitter: https://twitter.com/jeanette_c_s
>   * Audiobombs: https://www.audiobombs.com/users/jeanette_c
>   * GitHub: https://github.com/jeanette-c
>
> When you need someone, you just turn around and I will be there <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

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