The post about the perl script today got me thinking in general terms about
the score statements, & i think there is an obvious one thats missing.

anyway, the "missing statement" is one that sets "bar markers" but in an
accumulative, rather than absolute sense.

In my hypothetical example below, it is the "c" statement ("a" would have
been better, but it's taken - could "b+" be a possibility?)

the example score below is also expressed synonymously using the b
statement, & comparing the 2 should make it pretty clear what the difference
is.

in terms of organising large scores from smaller elements, without the need
for external scripting or parseing (which of course i now do 99.99% of the
time, but anyway...), i think it's the missing link.

is there any reason not to consider implementing this? 

it would also make copy & paste repetitions a lot easier & faster.....

actually, surely someone thought of this already... is there some technical
reason why it can't be done?


;;; "c" means advance the clock (rather than 'set' the clock with "b") 
;;; (& the existing "a" would of course just skip the bar altogether...)

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

c 4 

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

c 4

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

etc

**being == to

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

b 4

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

b 8

i 1 0 1
i 1 1 1
i 1 2 1
i 1 3 1

etc

-- 
View this message in context: http://www.nabble.com/new-score-statement-proposal-tp14494147p14494147.html
Sent from the Csound - General mailing list archive at Nabble.com.

The problem with your c is what is the current value of the clock?  The 
score is sorted and can be presented in any order within a section.  I am 
not saying that we cannot crete a semantics, but I suspect it is harder 
that you imply.
   Will look at it more closely later
==John ff

i guess you just declare it when you need to

"g 0" ;;; global time == 0 (or whatever time u want ....)

but i know (well, sense, sort of) what you mean - in as far as what im doing
assumes some sort of "order" that the csound score parser does not know to
be the case? (or something...)

this is basically what i do via python now with my custom score anyway. I
just wondered if the "accumulative" approach could be applied in csound
score itself.....

like with the + p2 statement. you have a reference point & off you go.....

no sweat from me if it can't be done. but if it can, great!

merry xmas mr ff (& everybody else... )


root-77 wrote:
> 
> The problem with your c is what is the current value of the clock?  The 
> score is sorted and can be presented in any order within a section.  I am 
> not saying that we cannot crete a semantics, but I suspect it is harder 
> that you imply.
>    Will look at it more closely later
> ==John ff
> 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/new-score-statement-proposal-tp14494147p14494674.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi Jeff

Could this be a macro var instead? Putting it in the pre-parser should 
make it possible, syntax might differ. The work-around of course is to 
use blue.

Michael

Tim Mortimer wrote:
> i guess you just declare it when you need to
>
> "g 0" ;;; global time == 0 (or whatever time u want ....)
>
> but i know (well, sense, sort of) what you mean - in as far as what im doing
> assumes some sort of "order" that the csound score parser does not know to
> be the case? (or something...)
>
> this is basically what i do via python now with my custom score anyway. I
> just wondered if the "accumulative" approach could be applied in csound
> score itself.....
>
> like with the + p2 statement. you have a reference point & off you go.....
>
> no sweat from me if it can't be done. but if it can, great!
>
> merry xmas mr ff (& everybody else... )
>
>
> root-77 wrote:
>   
>> The problem with your c is what is the current value of the clock?  The 
>> score is sorted and can be presented in any order within a section.  I am 
>> not saying that we cannot crete a semantics, but I suspect it is harder 
>> that you imply.
>>    Will look at it more closely later
>> ==John ff
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>     
>
>