Csound Csound-dev Csound-tekno Search About

[Csnd] A new score parsing glitch

Date2019-05-28 00:47
FromPete Goodeve
Subject[Csnd] A new score parsing glitch
AttachmentsNone  

Date2019-05-28 01:07
FromJohn ff
SubjectRe: [Csnd] A new score parsing glitch
I know of that bug -- just not adtie to chase it.  At present s needs a blank line after it

⁣Sent from TypeApp ​

On May 28, 2019, 00:48, at 00:48, Pete Goodeve  wrote:
>As I said, I seem to be a magnet (:-)), or maybe a canary in this case,
>as this one seems to be brand new.
>
>[Not sure if it's preferable to post this sort of thing to the
>development
>list?]
>
>With the posts yesterday about morphing and PVS etc., I went to play
>with pvsanal.csd from the examples.  I was surprised that I was only
>hearing two events in each section, despite there being three in
>the score!  With some playing around this seemed to be a function
>of the 's' statements in the score, so I made a short test file that
>shows the same effect (below).
>
>I was doing this in Haiku, so to make sure I took the file over to
>Linux -- where it played perfectly!  Then I realized that Haiku is
>currently 6.13, but Linux runs the 6.12 distribution.  I do have a
>6.13 compiled on Linux, though, so I tried that, and -- sure enough --
>I lost the same notes!  My two Linux versions are:
>
> OK:
> --Csound version 6.12 (double samples) Nov 27 2018
> [commit: 25f21b66c9e22a80089bf0ab5b8db3bf4331876a]
>
> Misses note:
> --Csound version 6.13 beta (double samples) Mar 13 2019
> [commit: 779ff35e1cd9cc8be23b365adb60d90350b9bd35]
>
>
>So something has changed pretty recently.  To be more specific
>with my tests, I find that the 's' statement kills the immediately
>following note, *provided* that there is no intervening newline,
>and no comment to the statement.
>
>Here's my stupid test file.  In 6.13, the first note of the second
>section is lost.  (Note the protecting comment on the first 's'.)
>
>
>
>
>-odac -d
>
>
>
>sr = 48000
>ksmps = 480
>nchnls = 1
>
>giSine0  ftgen 1, 0, 16384, 10, 1
>
>instr 1
>  icps = cpspch(p5)
>  kamp linen p4, 0.01, p3-0.02, 0.01
>
>  a1 oscil kamp, icps, giSine0
>  out a1
>endin
>
>
>
>
>
>s	;first section
> i1    0.000    1.000    8100.00    9.07
> i1    1.000    1.000    8100.00    9.09
> i1    2.000    1.000    8100.00    9.05
>
>s
> i1    0.000    1.000    8100.00    9.07
> i1    1.000    1.000    8100.00    9.09
> i1    2.000    1.000    8100.00    9.05
>
>
>
>
> 
>
>Thanks,
>
>	-- Pete --
>
>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

Date2019-05-28 16:02
Fromjohn
SubjectRe: [Csnd] A new score parsing glitch
Now fixed n github devekop branch.  Mea culpa.

On Mon, 27 May 2019, Pete Goodeve wrote:

> As I said, I seem to be a magnet (:-)), or maybe a canary in this case,
> as this one seems to be brand new.
>
> [Not sure if it's preferable to post this sort of thing to the development
> list?]
>
> With the posts yesterday about morphing and PVS etc., I went to play
> with pvsanal.csd from the examples.  I was surprised that I was only
> hearing two events in each section, despite there being three in
> the score!  With some playing around this seemed to be a function
> of the 's' statements in the score, so I made a short test file that
> shows the same effect (below).
>
> I was doing this in Haiku, so to make sure I took the file over to
> Linux -- where it played perfectly!  Then I realized that Haiku is
> currently 6.13, but Linux runs the 6.12 distribution.  I do have a
> 6.13 compiled on Linux, though, so I tried that, and -- sure enough --
> I lost the same notes!  My two Linux versions are:
>
> OK:
> --Csound version 6.12 (double samples) Nov 27 2018
> [commit: 25f21b66c9e22a80089bf0ab5b8db3bf4331876a]
>
> Misses note:
> --Csound version 6.13 beta (double samples) Mar 13 2019
> [commit: 779ff35e1cd9cc8be23b365adb60d90350b9bd35]
>
>
> So something has changed pretty recently.  To be more specific
> with my tests, I find that the 's' statement kills the immediately
> following note, *provided* that there is no intervening newline,
> and no comment to the statement.
>
> Here's my stupid test file.  In 6.13, the first note of the second
> section is lost.  (Note the protecting comment on the first 's'.)
>
> 
>
> 
> -odac -d
> 
>
> 
> sr = 48000
> ksmps = 480
> nchnls = 1
>
> giSine0  ftgen 1, 0, 16384, 10, 1
>
> instr 1
>  icps = cpspch(p5)
>  kamp linen p4, 0.01, p3-0.02, 0.01
>
>  a1 oscil kamp, icps, giSine0
>  out a1
> endin
>
> 
>
> 
>
> s	;first section
> i1    0.000    1.000    8100.00    9.07
> i1    1.000    1.000    8100.00    9.09
> i1    2.000    1.000    8100.00    9.05
>
> s
> i1    0.000    1.000    8100.00    9.07
> i1    1.000    1.000    8100.00    9.09
> i1    2.000    1.000    8100.00    9.05
>
> 
>
> 
>
>
> Thanks,
>
> 	-- Pete --
>
> 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

Date2019-05-28 19:19
Frompete.goodeve@COMPUTER.ORG
SubjectRe: [Csnd] A new score parsing glitch
AttachmentsNone