[maxmsp] Re: Bad curve~ arguments
Adam
nanoarchae at gmail.com
Sat Oct 20 12:36:11 MDT 2007
- Previous message: [maxmsp] Bad curve~ arguments
- Next message: [maxmsp] Re: Bad curve~ arguments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks, volker. Your suggestion worked. But now I'm experiencing some other strange behavior. The patch only works if I retoggle dac~. Particularly, curve~ won't produce any signal until I disblae dac~ and then re-enable it. I tried moving the dac~ and buffer~ load to the bottom right so it would be evaluated first but no dice. Strange... I will attach the patch so you can all see my abysmal code, heh. (It will prompt you for a wav on load. The message at the top beginning with 'cym' will trigger the patch. The dac~ object is located at the bottom right.) Suggestions appreciated! -------------- next part -------------- A non-text attachment was scrubbed... Name: fence_var.pat Type: application/octet-stream Size: 3561 bytes Desc: not available Url : http://www.cycling74.com/pipermail/maxmsp/attachments/20071020/531d66e8/fence_var.obj
- Previous message: [maxmsp] Bad curve~ arguments
- Next message: [maxmsp] Re: Bad curve~ arguments
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
