No subject

instead of silencing all notes at once and then jump to
a new position, it leaves the current notes to fade out
on their own, thus allowing for a smoother transition.
This involves scanning the track for note off events or
the end of the track, to see when the notes would have
been turned off.

I don't know what the unit of time measurement is, so I
don't know what are reasonable values and what aren't,
but when the track loops the time_left parameter is
somewhere around 10000, and it only has to scan a few
events ahead to figure that out.

Which makes the following calls to hangingNote(), which
I captured during one test run, look rather suspicious
to me:

hangingNote(11, 67, 8099928, 0)
hangingNote(11, 71, 8615520, 0)
hangingNote(11, 74, 16625052, 0)
hangingNote(1, 35, 72028872, 0)
hangingNote(2, 67, 78392304, 0)
hangingNote(6, 67, 104966496, 0)

Not only that, but it had to scan hundreds - maybe
thousands - of events ahead to find them.


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=418820&aid=775654&group_id=37116