ComfortableInClouds

Hello, I am having strange problems with this beatslicer I am tryiing to build. I believe it's due to my lack of familiarity with the poly~ object. Attached in the zip is 3 files:

beatSlicer.pat is the main patch for beat slicing.

polysliceDebug.pat is me trying to debug polyslice.pat

However, here's what gets me: i don't do anything different in the polysliceDebug.pat from the polyslice.pat file. All I did was add number boxes to check that I was getting the right values. This is what leads me to believe it must that I'm doing something wrong with poly~, however I've kept my handling of poly incredibly simple so I don't really know where I'm going wrong.

polyslice.pat is the poly~ file
beatSlicer.pat is the main patch for beat slicing.
polysliceDebug.pat is me trying to debug polyslice.pat

poly-trouble-with-my-elementary-beatslicer

I forgot to include that the debug patch WORKS, and does exactly what I want the poly patch to do (even though I didn't change anything from the poly patch).

They really should allow us to edit our messages more than 60 seconds after we post. Even if it was just like 5 minutes, instead of 1, it would be much better. I do not understand why this is not allowed. What's so bad about correcting yourself?

i think the problem here is the math you are doing inside the poly~. let me look at the patch.

hello,
i think the problem here is the math you are doing inside the poly~. let me look at the patch.

I think i have a solution for you. hope you have max 5.

thanks for the patch, icedragon. however, my intention was to play a single slice from the sample, while your patch plays from the beginning each time for a length determined by the multislider. my idea was that the mutlsider would determine the slice #, so if the sample is divded into 12 part, a multislider value of 8 would play from 7/12ths of the sample to 8/12ths of the sample.

After looking at your patch I got mine to work by having a separate counter for target. Thanks for that bit of wisdom. I guess target is where I was going wrong. I also added a "gate" time, so you can play smaller fractions of the sample if you so choose.

I'm glad i help, the target message tells poly~ which voice must be created and active, while the line~ don't kill it.

I found a problem on your new version, which is the Dial object Must Float Output in the properties menu, or else max crashes, at least here, on max 5.0.5. If you really want to play only slices from your sample, why don't you check slice~ object it will play only the slice you choose.

http://www.naotokui.com/2002/02/maxmsp-objects-2002/

hello,
I'm glad i help, the target message tells poly~ which voice must be  created and active, while the line~ don't kill it.
I found a problem on your new version, which is the Dial object Must Float Output in the properties menu, or else max crashes, at least here, on max 5.0.5. If you really want to play only slices from your sample, why don't you check slice~ object it will play only the slice you choose.
http://www.naotokui.com/2002/02/maxmsp-objects-2002/

yes, i understand what target does. i'm currently using max 4 so i wasn't aware of that bug, but am happy you found a solution. i think i "really" am playing slices from my sample, no need for an external object.

i made a patch where the crash can be reproduced. how can i send it to support? thanks

Poly~ Trouble With My Elementary Beatslicer