The problem seems to occur with the current CVS sources, but apparently
not with the 5.00.0 release. So, a bug may have been introduced since
then. It may not have to do anything with the fluid opcodes - those
have not been changed at all since the release, but I did make changes
in sensevents() to fix a problem where a very short note at the end of
the score or a section could result in a hang. Thus, it is very likely
that the bug was introduced by the changes to sensevents(); I will have
a look at this and try fixing the problem.

On Thursday 23 February 2006 07:38, Steven Yi wrote:

> I'm having a strange issue and wonder if it's a bug in Csound or in my
> own code.  I've pasted in output from rendering and a CSD for testing.
>  So far I'm seeing:
> 
> -if I have one fluid note or two, Csound will stop at the end of that
> note, even though the instrument with fluidEngine should continue to
> render
> 
> -if I have three or more fluid notes, Csound will stop rendering at
> the end of the second to last note (as in the example below)
> 
> I've tried with a few different SoundFonts and don't believe it to be
> that.  I have CS5 compiled from CVS on Fedora Core 4, gcc 4.0.2, and
> fluidSynth version 1.0.6.
> 
> Oh, also, if I have other Csound notes from other instruments that are
> longer than the fluidEngine instrument note, things will continue to
> render as expected, so it seems to only happen when there's only fluid
> things going on.
> 
> I'm still looking at fluidOpcodes.c but haven't found anything yet. Any ideas?


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net