Forums > Max For Live

FAO: ddg


pid
August 27, 2011 | 2:44 pm

dear mr ddg,

just wanna say THANKS for your new chucker~ in 5.1.9 – it is a completely awesome rewrite. these new fade modes rock. completely excellent addition to all my chucker~ patches i been playing round with today. also everything working solid.

p.s. – please say thanks to your buddy mr poletti for the polettification of the ‘big three’. fantastic. although he might wanna take a look at your buffershuffler again as i am sure the clicking/smoothing is not exactly the way it used to be. (and surely you should put access to your new fademodes in buffershuffler device now?).

p.p.s. – will we finally have official support for step.overplay and zeropoint~ in max6? we really should! step.overplay works quite painlessly in my patching but zeropoint~ is a bit hard to tame.


August 29, 2011 | 12:14 am

Thanks, Mr. pid!

I’m glad to hear that it’s working well for you. It took a little while to really nail this one, but I think the results are worth both the time and the effort. The fade modes are a favorite for me, too, since it really opens up some of the functionality of the object for working with new kinds of source material.

Manuel did an excellent job of patch cleanup for me – when I originally did the Big Three, I was under the gun for getting them done, and sometimes the patching suffered for it. I think it really went well. I’ll look at the smoothing access to make sure things are still kosher.

Putting the fade mode into the device would change the presets, and would probably screw with people’s saved projects. We are talking about how to add this (and some other) functionality to the devices, but it won’t happen soon.

Of course, it wouldn’t be hard for anyone to make a Buffer Shuffler variant that exposed the fade modes. This is a case where users perhaps have more power than I do!

I’ll look into documenting step.overplay, but zeropoint~ is a really tricky one. The thing to realize is that it was created specifically for Loop Shifter, where the access into a buffer is "virtualized" into 1000 points. By doing this virtualization, we are able to allow breakpoint settings to stay the same even if you use wildly different sample clips. So, it’d be a little hard to make that one official…

Thanks again for the props, and rock out those patches!

[ddg]



pid
August 29, 2011 | 8:11 am

thanks for big info cool reply to my cheeky post!
of course i already modify all the devices for me, i just like the idea of completism.
looking forward to developments…
(p.s. – who do i talk to for requests for rewriting [techno~] now?!…)


June 11, 2012 | 10:36 pm

Is there some documentation coming for step.overplay? I was just studying the M4L Step Sequencer device that’s part of the standard M4L install and came across this object and saw it has no help file. I’m guessing it’s like a poly object to allow multiple simultaneous sequences?


Viewing 4 posts - 1 through 4 (of 4 total)