Hi All,

Menno notified me a few months back that the examples in my Tied Notes
article for the Csound Journal
(http://www.csounds.com/journal/2005fall/tiedNotes.html) had some
problems. I have fixed up the following issues in the blue project and
CSD file:

-delay was not skipping initialization
-amplitude value was not smoothed
-glissandi cloud example was generating tied conflicting fractional
instrument numbers (ex. 3.1 and 3.10)

The mp3 for that article has been updated and fixed, and the archive
for that issue has been updated with the latest examples.

Thanks to Menno for pointing out the problem!
steven


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"

I'm curious about one thing. In the code example for your article, you use
the reserved word ithen in your UDO. The meaning of this is obvious ... but
(a) it doesn't seem to be mentioned in the Canonical Manual, and (b)
replacing it with plain old 'then' seems to have no deleterious effect.

Am I missing something here? Is there a reason why ithen is used in the UDO?
Thanks for any tips.

--Jim Aikin

--
View this message in context: http://csound.1045644.n5.nabble.com/Updated-Examples-for-Tied-Notes-Article-tp4626451p4633741.html
Sent from the Csound - General mailing list archive at Nabble.com.


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"

Hi Jim,

There's actually three then statements: then, kthen, and ithen.  As
far as I remember, these are analogous to goto, kgoto, and igoto, and
the parser rewrites the if-thens to use those goto opcodes (or similar
internal ones like cngoto, which is only used internally and not used
by users).

For myself, I tend to use kthen and ithen more often than then as they
are more explicit.  It reminds me that I'm doing an init-pass
conditional or performance-time conditional.  Using "then" in this UDO
may well work just fine, but I think it's a a habit of mine to use the
more explicit versions.

Hope that helps!
steven

On Tue, Jul 26, 2011 at 2:08 AM, Jim Aikin  wrote:
> I'm curious about one thing. In the code example for your article, you use
> the reserved word ithen in your UDO. The meaning of this is obvious ... but
> (a) it doesn't seem to be mentioned in the Canonical Manual, and (b)
> replacing it with plain old 'then' seems to have no deleterious effect.
>
> Am I missing something here? Is there a reason why ithen is used in the UDO?
> Thanks for any tips.
>
> --Jim Aikin
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Updated-Examples-for-Tied-Notes-Article-tp4626451p4633741.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> 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"
>
>


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"

> There's actually three then statements: then, kthen, and ithen.

I was sort of guessing that. As far as I can see, kthen and ithen are
completely undocumented. I'll play around with them a little.

--JA


--
View this message in context: http://csound.1045644.n5.nabble.com/Updated-Examples-for-Tied-Notes-Article-tp4626451p4640764.html
Sent from the Csound - General mailing list archive at Nabble.com.


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"