I think I know why this does not do what you want. In general, pv opcodes output only
after a new frame has been produced at the input, so if you loop, you will get the same
result. I can change this behaviour to get a new value if the bin is different. I never anticipated
this use. I will have a look at this tomorrow.
Victor
----- Original Message -----
From: Victor.Lazzarini@nuim.ie
Date: Monday, May 23, 2011 8:02 pm
Subject: Re: [Csnd] new problem with looping
To: csound@lists.bath.ac.uk
> Without a CSD to test, we can't diagnose. Please provide a minimal CSD showing the issue.
>
> Victor
>
> ----- Original Message -----
> From: Matti Koskinen <mjkoskin@kolumbus.fi>
> Date: Monday, May 23, 2011 7:20 pm
> Subject: [Csnd] new problem with looping
> To: Csound mailing list address <csound@lists.bath.ac.uk>
>
> > encountered another problem with looping. Looping pvsbin
> > fsig,kloopindx where kloopindx is incremented by 1
> > gives same kamp and kfr for all the bins. e.g. kamp,kfr
> > pvsbin fsig,10 and pvsbin fsig,11 gives different values for
> > kamp and kfr. running the orc from previous posts, changes kamp
> > and kfr after the loops have finished, all the values while in
> > the loop where kbins is incremented by 1 are the same.
> >
> > ??
> >
> > thanks
> >
> > -matti
> >
> >
> >
> > Send bugs reports to the Sourceforge bug tracker
> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
> > Discussions of bugs and features can be posted here
> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
> > "unsubscribe csound"
> >
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
National University of Ireland, Maynooth