Hi Leafcutter, I'm also very interested by building/finding a CDP/MAX front-end. I saw on the shell topic that you already worked on, would you share your work ? I'm available for work on too and could help.
Wow - so, it's available for free now!?
I can remember hearing some amazing stuff made with CDP many years ago, but then being put off by the price.
Must have a good look at this again - and a Max front end would be very cool,
I just checked out that forum post. It was just a discussion as far as I could tell. No patch posted, links or anything, just the photo.
I am going to start working on this tomorrow. With an end goal of a max, and a M4L front end. I do a lot of my work in live, running cdp operations and putting the file right into live sounds incredible.
Looks like the project may have stalled, but it might be worth e-mailing the the original poster as it looks like they are using java to communicate with CDP which could be interesting. I've attached the exploritory work I did yesterday.
a max front end could be fun! did you make mr matrix? i remember that having pretty nice ergonomics. a front end like that for the CDP processes would be wicked - it'd be like super turbo synth 2 haha.
i never really got into soundloom. offline batch process scripting with CDP is what makes CDP to me. (i still like step time entry on sequencers too) you can run a process / series of processes 10s, 100s of times, get stuff that would either overload your cpu, be tedious to do by hand, it's much less carpal tunnel making to generate cool rhythmic envelopes than it is to draw them all by hand. :) or since it can actually process faster than realtime it's potentially quicker than working real time for big effect chains. not to mention CDP sounds nice. :)
a process style of working never felt all that fluid to me with soundloom even over text scripts and i don't find scripting all that conductive to playing around! max patching works great for process style working by being able to freely make connections though. it could be be a good fit.
i mean, i can patch weirder, cooler stuff in max, that i can actually understand after i do it, because i can make connections between elements that are "far apart", while if i'm working with text and scripts i'm forced to be way more orderly... and when i try to interconnect elements i end up breaking things anyway, haha. it's like, supposedly gotos are bad programming, but that's what max patching does for me and i find it super useful!
btw, how are you with gen? i've been poking around at the cdp source to see what can be adapted to gen, but i'm new to gen and it's harder for me to convert from c to gen than it is to either mess with the c on it's own or to just start from an idea in gen and build up.
Thank you for posting your first few patches. I altered one to use the envel extract function. It extracts the amplitude envelope of a sample and reads it into the breakpoint object. I'll post more as I continue to explore CDP.
"i never really got into soundloom. offline batch process scripting with CDP is what makes CDP to me."
I don't understand this comment. Working with a front end to CDP, such as Sound Loom, does not preclude the sort of batch processing described here. I much prefer SoundShaper, though, and regret tremendously that it is Windows only.
it's not max, but a few people have created a *very* capable renoise front-end for CDP. I still use scripts to extract data from large collections of sound (envelope, formant, etc) but it really is amazing! still would love to see a front-end for max though!