| The tempoval opcode returns the current tempo (e.g. as set by tempo or -t). That is unchanged at 60, the
t statement in the score does not change it.
Instead it basically pre-processes the start times/durations given in the score and presents those changes to
Csound. The tempo as detected by tempoval is unchanged, but the timing of the score events is modified.
I know it’s confusing, but it is what it is. The t preprocessing has been there since the start, then tempo/tempoval
were added later on top of it. You can only use one or the other (if you use -t all tempo preprocessing is disabled).
If you were to ask me, I think the score is a very antiquated/old-fashioned controller interface. I rarely use it
outside of testing/demonstrating it.
> On 27 Feb 2025, at 12:35, poppordelia <00000c641a512f08-dmarc-request@LISTSERV.HEANET.IE> wrote:
>
> im sorry. still don't figure out how tempoval works.
> in this exemple im trying to get the -t value from an instrument and even with printk2 i still get only 60 even if my -t starts with another value.
>
> thanks !
>
>
>
> -odac
> --sample-rate=48000
> --nchnls=2
>
>
>
>
> instr 1
>
> ktempo tempoval
> printk2 ktempo
>
> endin
>
>
>
> t 0 25 5 61
> i 1 0 5
> e
>
>
>
> 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 |