[Csnd] csound~ blowing up in Max 6 on invalue
Date | 2012-09-17 06:45 |
From | Jim Aikin |
Subject | [Csnd] csound~ blowing up in Max 6 on invalue |
In doing a preliminary test of csound~ with Max 6.0.7 in MacOS 10.6.8, using Csound 5.18.02, I'm finding a bad thing. Namely, invalue causes Max to crash. My simple instrument has this: kfreq init 220 kfreq invalue "osc1freq" If I comment out the 2nd line, the instrument plays, producing a nice sine wave, when I bang the csound~ object to compile and start playback of my one-note score. But if I uncomment that line, Max hangs with the spinning beach ball, or sometimes just quits abruptly. It's not even a matter of sending a message using a Max message box -- Max crashes immediately, without managing to compile the orch. I kinda think this is a bug, not user error, but I've been wrong about such things from time to time. Can anyone else confirm this result? --JA -- View this message in context: http://csound.1045644.n5.nabble.com/csound-blowing-up-in-Max-6-on-invalue-tp5715895.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2012-09-17 06:47 |
From | Jim Aikin |
Subject | [Csnd] Re: csound~ blowing up in Max 6 on invalue |
Fortunately, chnget works. -- View this message in context: http://csound.1045644.n5.nabble.com/csound-blowing-up-in-Max-6-on-invalue-tp5715895p5715896.html Sent from the Csound - General mailing list archive at Nabble.com. |
Date | 2012-09-17 11:58 |
From | peiman khosravi |
Subject | Re: [Csnd] Re: csound~ blowing up in Max 6 on invalue |
Mhh I've never experienced this. Must be max6, which I haven't really had time to play around with yet. P On 17 September 2012 06:47, Jim Aikin |
Date | 2012-09-17 21:38 |
From | Takahiko Tsuchiya |
Subject | Re: [Csnd] Re: csound~ blowing up in Max 6 on invalue |
Hi Jim, I'm on the same versions of software / OS and I can confirm this. If you use QuteCsound, there's a handy function that replaces all invalues to chngets with one click, under Edit menu.
Takahiko On Mon, Sep 17, 2012 at 6:58 AM, peiman khosravi <peimankhosravi@gmail.com> wrote: Mhh I've never experienced this. Must be max6, which I haven't really |