Csound Csound-dev Csound-tekno Search About

[Cs-dev] [ csound-Bugs-3031342 ] bug in score sorting w/legato instruments (negative p3)

Date2010-07-19 09:51
From"SourceForge.net"
Subject[Cs-dev] [ csound-Bugs-3031342 ] bug in score sorting w/legato instruments (negative p3)
Bugs item #3031342, was opened at 2010-07-18 22:50
Message generated for change (Comment added) made by jpff
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=564599&aid=3031342&group_id=81968

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: csound
>Group: csound5
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: John ffitch (jpff)
Summary: bug in score sorting w/legato instruments (negative p3)

Initial Comment:
I found a bug with a sample legato instrument score that uses the negative p3 trick to indicate a legato note which is to be tied to the next note event from the same instrument. Here's the input score:


t 0 120 
i201.0 0.000 .5  0.66  1  0.5  1 
i202.0 0.000 .5  0.66  1  0.5  1  1 .5 .6 8000
i10.0 1.5   -.5  0.66  261.62557  0.5  1  0.8
i10.0 2     -.5  0.66  391.26571  0.5  1  0.8
i10.0 2.5    .5  0.66  357.79083  0.5  1  0.8
i10.0 4     -.5  0.66  305.95299  0.5  1  0.8
i10.0 4.5   -.5  0.66  327.17991  0.5  1  0.8
i10.0 5      .5  0.66  327.17991  0.5  1  0.8

The results of the command 'scsort < legatotest.sco' are:

w 0 120
i 201.0 0.000000 0.000000 0.500000 0.250000 0.66 1 0.5 1
i 202.0 0.000000 0.000000 0.500000 0.250000 0.66 1 0.5 1 1 .5 .6 8000
i 10.0 1.500000 0.750000 -0.500000 -0.250000 0.66 261.62557 0.5 1 0.8
i 10.0 2.500000 1.250000 0.500000 0.250000 0.66 357.79083 0.5 1 0.8
i 10.0 2.000000 1.000000 -0.500000 -0.250000 0.66 391.26571 0.5 1 0.8
i 10.0 4.000000 2.000000 -0.500000 -0.250000 0.66 305.95299 0.5 1 0.8
i 10.0 5.000000 2.500000 0.500000 0.250000 0.66 327.17991 0.5 1 0.8
i 10.0 4.500000 2.250000 -0.500000 -0.250000 0.66 327.17991 0.5 1 0.8

As you can see, the p2 (event onset) times are not correctly sorted in order, and the audible result is screwed up big time. For example the event that falls on 2.5 beats comes before the one on 2 beats....what's going on here? I don't know why, but this is only something I've noticed in the CVS version I compiled on the 14th of July.

Thanks, 
Aaron Krister Johnson

----------------------------------------------------------------------

>Comment By: John ffitch (jpff)
Date: 2010-07-19 09:51

Message:
Corrected in CVS

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=564599&aid=3031342&group_id=81968

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net