[Csnd-dev] bug in next-p?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[Csnd-dev] bug in next-p?

luis jure

hello,

I think I hit a bug in next-p. As far as I understand, the following code
should be perfectly legal:

; p2 p3 p4 p5
i1 0 1 60 np4
i1 1 1 64 60

but when compiling, I get these messages:

swrite: output, sect1 line2 p5 makes illegal reference to n p4 Zero
substituted
swrite: output, sect1 line3 p6 makes illegal reference to p4 Zero
substituted

Two things are wrong:

- in the first event it claims that the reference to np4 is illegal
- in the following event, it sees an inexistent p6

Please see attached a complete example csd.

I'm using:
--Csound version 6.12 beta (double samples) May 31 2018
[commit: bef59a7a9d4de7b211fe9e236f35b21cbd9948a9]

I think it was working in 6.10 or something.



--

bug_npx.csd (290 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] bug in next-p?

jpff
Oh dear!  Another aspect of the n character in a score.  Will think ont'it

On Fri, 1 Jun 2018, luis jure wrote:

>
> hello,
>
> I think I hit a bug in next-p. As far as I understand, the following code
> should be perfectly legal:
>
> ; p2 p3 p4 p5
> i1 0 1 60 np4
> i1 1 1 64 60
>
> but when compiling, I get these messages:
>
> swrite: output, sect1 line2 p5 makes illegal reference to n p4 Zero
> substituted
> swrite: output, sect1 line3 p6 makes illegal reference to p4 Zero
> substituted
>
> Two things are wrong:
>
> - in the first event it claims that the reference to np4 is illegal
> - in the following event, it sees an inexistent p6
>
> Please see attached a complete example csd.
>
> I'm using:
> --Csound version 6.12 beta (double samples) May 31 2018
> [commit: bef59a7a9d4de7b211fe9e236f35b21cbd9948a9]
>
> I think it was working in 6.10 or something.
>
>
>
> --
>
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] bug in next-p?

jpff
In reply to this post by luis jure
I believe this is fixed in git now -- it runs your program OK

...
sorting score ...
         ... done
Elapsed time at end of score sort: real: 0.003s, CPU: 0.003s
graphics suppressed, ascii substituted
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
writing 512-byte blks of shorts to test.wav (WAV)
SECTION 1:
new alloc for instr 1:
instr 1:  p4 = 60.000  p5 = 64.000
B  0.000 ..  1.000 T  1.000 TT  1.000 M:      0.0
instr 1:  p4 = 64.000  p5 = 60.000
B  1.000 ..  2.000 T  2.000 TT  2.000 M:      0.0
Score finished in csoundPerform().
inactive allocs returned to freespace
end of score.              overall amps:      0.0
            overall samples out of range:        0
0 errors in performance
Elapsed time at end of performance: real: 0.006s, CPU: 0.006s
256 512 sample blks of shorts written to test.wav (WAV)


==John ff

On Fri, 1 Jun 2018, luis jure wrote:

>
> hello,
>
> I think I hit a bug in next-p. As far as I understand, the following code
> should be perfectly legal:
>
> ; p2 p3 p4 p5
> i1 0 1 60 np4
> i1 1 1 64 60
>
> but when compiling, I get these messages:
>
> swrite: output, sect1 line2 p5 makes illegal reference to n p4 Zero
> substituted
> swrite: output, sect1 line3 p6 makes illegal reference to p4 Zero
> substituted
>
> Two things are wrong:
>
> - in the first event it claims that the reference to np4 is illegal
> - in the following event, it sees an inexistent p6
>
> Please see attached a complete example csd.
>
> I'm using:
> --Csound version 6.12 beta (double samples) May 31 2018
> [commit: bef59a7a9d4de7b211fe9e236f35b21cbd9948a9]
>
> I think it was working in 6.10 or something.
>
>
>
> --
>
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] bug in next-p?

luis jure
el 2018-06-01 a las 17:35 jpff escribió:

> I believe this is fixed in git now -- it runs your program OK

Yes! It's working OK now, thanks for the prompt fix, John!



--