posted 25 December 2008 05:10            

I've been looking through the Random trigger expressions examples on the Tweaky and trying out the examples but on any example that contains a deviation: argument I get the error:
HotVariables cannot perform the operation 'triggerName':deviation:.

I'm pasting the example code into a gate field of a sample player, I've tried substituting the hot variables for numbers but still no luck.
They dont seem to be able to be used in this context, I cant even send them a !KeyDown message without getting the error.

Have I got it wrong somehow or can anyone suggest an alternative approach?

posted 15 January 2009 14:27            

i am guessing that you have a conflict between using capytalk and smalltalk. without the exact expression i can't be sure and i am not in front of my capy at the moment. but the !hot variables cannot perform message ... is a message that frequently comes up for me if i have intertwined the two languages or if i have confused the smalltalk synthax or commands with capytalk.

as you are probably aware smalltalk can only use hot variables under very specific circumstances.

just a hunch.

posted 26 January 2009 02:21            

The expressions are as follows:

!sw01 brownianTrigger: !StartDur s
!sw01 brownianTrigger: !StartDur s deviation: !Dev s
!sw01 normalTrigger: !NormDur s
!sw01 normalTrigger: !NormDur s deviation: !Dev s
!sw01 randExpTrigger: !StartDur s
!sw01 randomTrigger: !AveDur s
!sw01 randomTrigger: !AveDur s deviation: !Dev s

When I paste anything with a "deviation: !Dev s" component it errors, anything without it works.

posted 26 January 2009 20:40            

!sw01 brownianTriggerStart: 1 s deviation: !Dev

!sw01 normalTriggerCenter: 1 s deviation: !Dev

!sw01 randomTriggerCenter: 1 s deviation:!Dev

posted 31 January 2009 19:24            

I'm using Firefox and on click on any of the above buttons it just hangs waiting for www.symbolicsound.com

posted 31 January 2009 19:35            

That's funny, I was just updating the page to reflect this conversation, and then I was trying to re-enter the page to change something else, but it said that you were editing the page!

But anyway, I think I did most of what needed to be done, changing the examples so that they use the expression that are being discussed.

For example, it said it was discussing randomTriggerCenter:deviation, but the example was

!sw01 randomTrigger: !AveDur s deviation: !Dev s

which I changed to read:

posted 03 February 2009 02:46            

I politely but strongly disagree with you SSC on this point.
Removing the s after the !Dev made the expression work for me rather than throwing an error message, which was the very reason for this post.

I agree with the idea of having the the s included in the explanations and notes for the expression but I cannot understand why an example expression should include content that makes it error, particularly when:

~~
Internally, Kyma adds the s units onto that argument whether or not you include it
~~~

I believe the examples with !Dev in them should read in the form shown earlier:
!sw01 brownianTriggerStart: 1 s deviation: !Dev
!sw01 normalTriggerCenter: 1 s deviation: !Dev
!sw01 randomTriggerCenter: 1 s deviation: !Dev

I really dont want to step on any toes here but unless SSC or someone else can give me a compelling reason 'not' to change the examples, I do intend to edit this Tweaky page, replacing the instances of "deviation: !Dev s |" with "deviation: !Dev |"

Example expressions should be able to be copied and pasted and work unless otherwise noted. Don't you agree?

I look forward to hearing people's views on this.

posted 03 February 2009 06:02            

The expression seems to work the same for me with our without the "s." What made the difference between the expressions working and not working for me were what I changed on the Tweaky page: "randomTriggerCenter:deviation:" instead of "randomTrigger:deviation," "brownianTriggerStart:deviation" instead of "brownianTrigger:deviation," etc.

Try cutting and pasting the expressions as they are from the Tweaky into a SoundToGlobalController and uncheck the "silent" box (and turn down your amplifier) to verify that they are working. They work for me now.

posted 05 February 2009 02:07            

I'm a bloody nong. I think I need to READ things a bit more carefully.

Thanks all and apologies for the brain fart