[maxmsp] Re: Bad curve~ arguments
volker böhm
vboehm at gmx.ch
Sun Oct 21 08:56:23 MDT 2007
- Previous message: [maxmsp] Re: Bad curve~ arguments
- Next message: [maxmsp] Re: OpenGL version problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 20 Oct 2007, at 20:36, Adam wrote: > 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! > <fence_var.pat> hi, i just had a quick look at your patch - a little too convoluted to be easily debugged. and your screen is obviously a lot bigger than mine... but the patch seems to work over here. loadbanging the dac is problematic. wouldn't do that, or at least delay it a little bit. don't know why you want to use curve~ instead of linear playback, but you'll have your reasons. the number of repeats is not correct because of the ">=" in the [if] statement - use ">" instead. apart from that, it seems fine. vb
- Previous message: [maxmsp] Re: Bad curve~ arguments
- Next message: [maxmsp] Re: OpenGL version problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
