| I think there's any be a glitches in my fix yesteray. Some up those morning thinking about it!
I suspect the change can be migrated to printks. Will look
But yes I think there is an oddity in the recording of time internally. Will discuss on developers list.
==John ff
Sent from TypeApp
On Jan 4, 2018, 11:34, at 11:34, Jan Jacob Hofmann wrote:
>Dear list,
>
>thanks for fixing it so quickly, John. Meanwhile I discovered that the
>same behavior applies to printks. Also its messages do not appear at
>the expected time - which makes me wonder if there is something wrong
>with the internal time management of Csound or the printing-opcodes in
>general. I guess it is a strange coincidence, that both of the opcodes
>show the same result. I am still at Csound version 6.09.1as I can not
>pull the latest fix that easily onto my mac, I guess. A new .csd for
>testing printks is below.
>
>All the best,
>
>Jan Jacob
>
>
>
>-n
>
>
>
>sr = 44100
>ksmps = 441
>nchnls = 2
>0dbfs = 1
>
>instr 1
>ktest line 0, p3, 1
>
>printk 1, ktest ; it should display „0“ at the first k-cycle and „1“ at
>time = 1
>printks „Here is a print of ktest: %f \\n“, 1, ktest ; print message ;
>it should display „0“ at the first k-cycle and „1“ at time = 1
>endin
>
>
>
>i1 0 1
>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 |