Hi,

I think the precision of score time values depends on kr, as score
events are processed at the start of control periods (I might be wrong,
so I'd appreciate correction), so if you use kr = sr then you will get a
precision of 1/sr.

Cheers,
Andrés

El jue, 21-02-2008 a las 11:18 -0600, Jeff Taylor escribió:
> In my compositions I often use an instrument to generate line segments
> that are sent via zak to another instrument.  Usually I call this
> instrument several times in succession to create a more complex
> signal, basically like a break point line that is being defined with
> score statements.  These instruments are very simple, generally in the
> form of something like:
> 
> intsr 2
> kout linseg p4, p3, p5
> zkw kout, 0
> endin
> 
> instr 1
> kin zkr 0
> ;do something here
> endin
> 
> That has been working well for me in the past where I use this
> technique to make slower moving signals.  However, in a recent
> composition, one with an upbeat tempo and short line segments, I found
> I was getting discontinuities between the individual score events with
> this setup.  More specifically, the signal drops to 0, only a few
> samples in length at maximum.  Strangely, these discontinuities are
> not always present depending on where the line segments are started.
> Using the same events with the same lengths and relative positions but
> shifted to a different spot gives different results.
> 
> My suspicion is that there is a limit the how precise the score
> statements can be causing rounding errors.  Right now I am using
> positions and lengths with 3 numbers after the decimal point at about
> 130 bpm.  Statements such as the following are typical:
> 
> i2    8.125    .625    0    .3
> i2    8.75      .125    .3   .93
> i2    8.875    .25      .93 1
> 
> If it makes any difference, I am not currently making use of + and .
> score elements with these particular line generating instruments (I am
> using another piece of software to generate the events) but the
> positions and lengths do add up to being back to back with no space in
> between them.
> 
> So, is there a maximum precision for score events as i am suspecting
> that would be within the ranges I indicated above or should I be
> looking for a different culprit?
> 
> Thanks.
> 
> -- 
> Electronically,
> Jeff Taylor

Yes, the resolution of score events, notes starting and stopping is always 
based on kr
==John ff

Jeff my python based score generating environment (& accompanying orc
designs) function in basically the same way - except i use gk & ga rate
variables instead of zak channels...

what is the "other piece of software" that u are using to generate score? Do
you have any links or information? I'm always keen to see where my ideas are
overlapping with existing tools or processes that perhaps i am not yet aware
of.

If this is something you have designed, or are working on, can I / we hear a
bit more about it?

many thanks

Tim


Jeff Taylor-5 wrote:
> 
> 
> 
> i2    8.125    .625    0    .3
> i2    8.75      .125    .3   .93
> i2    8.875    .25      .93 1
> 
> If it makes any difference, I am not currently making use of + and . score
> elements with these particular line generating instruments (I am using
> another piece of software to generate the events) but the positions and
> lengths do add up to being back to back with no space in between them.
> 
> So, is there a maximum precision for score events as i am suspecting that
> would be within the ranges I indicated above or should I be looking for a
> different culprit?
> 
> Thanks.
> 
> -- 
> Electronically,
> Jeff Taylor
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 


-----
*******************
www.phasetransitions.net
hermetic music * python * csound * possibly mindless ranting
various werk in perpetual delusions of progress....

-- 
View this message in context: http://www.nabble.com/Minimum-resolution-for-score-statements-tp15616480p15622812.html
Sent from the Csound - General mailing list archive at Nabble.com.