| I'm testing the new score opcodes. I find them very useful when using macro arithmetic.
I'd like an opcode which terminates the loop cycle without terminating a section, in order
to allow using more loops at the same time. Unfortunately at present time only 's', 'e'
and a new 'r' can be used to terminate the loop cycle, which make impossible to begin a
concurrent loop. There is a way to avoid this? That is, I'd like a terminator (such as 's'
opcode) that doesn't reinit the time clock and doesn't obbligate to place all the new
notes after the end of the previous section. Could it be possible?
jpff@maths.bath.ac.uk wrote:
>
> Message written at 13 Jan 1999 09:18:36 +0000
> --- Copy of mail to g.maldonado@agora.stm.it ---
> In-reply-to: <369B921F.E7B20132@agora.stm.it> (message from Gabriel Maldonado
> on Tue, 12 Jan 1999 19:19:11 +0100)
> References: <369B921F.E7B20132@agora.stm.it>
>
> This is all explained in my chapter in Richard Boulanger's book, the
> chapter entitled "Language Extentions" (ch 5 I think)
>
> However as you may not have a copy of the book to hand....
>
> b Resets the base clock for textually following events. I use
> it for repeated sections where I want an overlap with previous version
> as it does not start a new section. It is textual, and is expanded
> before sorting.
>
> v Sets a scaling on the speed of the clock, again textually until
> the end of the section or the next v command. I use it for phase
> music, where there is 1 theme played twice simultaneously at different
> speeds. As it is textual it is local unlike the t command
>
> m Sets a mark in the score which can be referenced by later n
> directives
>
> n repeat a named section (ie from m to end of section).
> Designed to simplify verse+chorus structures.
>
> w is totally different and is used internally related to t
> directives. There is no reason to understand it as it shoudl not be
> used. Alternatively, read the cod if you want to know!
>
> ==John ffitch
--
Gabriel Maldonado
|