| I had thought to do something similar as you mentioned for blue, but
would have had blue generate the values that would have written to a
global k-sig and the notes would have been written for the tempo
instrument would have been processed by the t-statement itself. I
think it's good to get the times in an envelope as you mentioned and
have the values processed by t-statement, then have the opcode for
getting the tempo.
Best to save this until after 5.17 though, as it's a bit late now, IMO.
On Thu, Mar 15, 2012 at 10:06 AM, Tito Latini wrote:
> Dr. Richard Boulanger wrote:
>
>> PS. Tito and I were exploring some of the "issues" associated with the tempo command in the score - perhaps he
>> +would want to share these with the list. There are
>> some confusing things there too.
>
> I think that the developers know this (and better) but alpha=0xff
> for the transparency; here is my answer to the question about
> "a simple value converter that the pre-processor/parser would be able
> to interpret and convert to values in seconds based on set tempo and beat".
>
> On Sun, Mar 11, 2012 at 7:08 PM, Tito Latini wrote:
>
>> The problem is to get the tempo from the score. We see an example:
>>
>> t 0 135 11 90 22 96
>>
>> i1 0 1
>> i1 10 .
>> i1 20 .
>>
>> after scsort, we have
>>
>> w 0 135 11 90 22 96
>> i 1 0.000000 0.000000 1.000000 0.454545
>> i 1 10.000000 5.454545 1.000000 0.656566
>> i 1 20.000000 11.957702 1.000000 0.630682
>> e
>>
>> the tempo has been applied and the w-statement contains the old
>> temporal references (in the example 0, 11 and 22).
>
> errata corrige: w-statement contains the temporal references in beats (like t-stmt)
>
>>
>> A possible but complex solution is to change the score parser for the
>> w-statement:
>>
>> 1) insert the time envelope in a buffer (also to change the CSOUND struct)
>>
>> 2) rescale the times of the envelope
>>
>> 3) write an opcode to get the score tempo interpolating the value of
>> the current time in the envelope
>>
>> The simplest solution is a filter like `csbeats' for the new notation,
>> usable with ; whatever command with the syntax
>>
>> command infile outfile
>>
>> can be used as a score filter in
>>
>> It is the point: to change CSOUND struct, score parser and add an opcode
>> or to simply write a filter for the score. I think that the second
>> doesn't cause flames.
>>
>> tito
>>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |