[Bluemusic-users] nGen in Blue weirdness

[Menno K. <mag...@gm...>]

Hi

is someone using nGen for score generation? Then please, jump in the
conversation...

nGen can be used in Blue with the External Object. The command line :

      ngen $infile $outfile

and indeed, score values are sent back to Blue.
But there is something weird because the same nGen script used in Blue and
as a standalone produces a different result - which is undesirable.

Here is a screenshot where (nearly) all goes well:
double_values.png
<http://csound.1045644.n5.nabble.com/file/n5753550/double_values.png>  
There is an External Object of 10 seconds. You can see the nGen script on
the right. This script is used to produce the values a) directly from the
terminal (result in texteditor) and b) from within blue

Notice the double values at the end of the score from Blue. I'm sure it has
something to do with the weirdness that happens when i change the script a
bit ( p2 .1 ) and run this script from the terminal and Blue:
wierd_values.png
<http://csound.1045644.n5.nabble.com/file/n5753550/wierd_values.png>  
Now things are going crazy: the last 2 double values start at 90 seconds and
are well outside the External Object itself...

What could be the reason? What is happening in between the sending from Blue
to nGen and back that could be responsible for this changes?




--
View this message in context: http://csound.1045644.n5.nabble.com/nGen-in-Blue-weirdness-tp5753550.html
Sent from the Csound - Blue - User mailing list archive at Nabble.com.