am i the only one who finds the “binary” notation for fingering pretty revolutionary?

i’m not a fan of most systems because they arent able to balance flexibility and simplicity…
this just makes sense

1 Like

Perhaps i am using an outdated version. I downloaded PartyVan from the Github, but as soon as i turn it on it crashes max7. Is there an updated version. I am trying to grok the devel going on but i admit i am a bit lost. I am on a mac with max 7 and a 64 grid

Thank you

It doesn’t run in Max7, have to use it in Max6. Depending on what you want to do with it, there’s “Block Party” (posted above) that’s kind of like The Party Van 1.5 (at least the core sampler bits).

THANKS!
I;ll give it ago with Max6 then

@Rodrigo

another proposal for the empty space in BP: magnify the mini VU/ocsilloscope

Currently playing with some new UI layout ideas that will remove the need for having such a wide/empty layout.

I’m basically going to resize most components to 169px tall, so I can easily port stuff to M4L devices (finally!). So I’m gonna try to compress a whole karma_core module into something around this size (maybe even smaller) with an even simpler/cleaner interface.

Also note the in/out/bus routing options, and playback modes:

karma = as-is
glitch = chocolate grinder style random position/window variation + digital clicks at jump
lofi = wtpa sampler emulation with really gritty sounding lofi textures at slower playback speeds
mlr = no switch&ramp declicking + quantize
vinyl = ramp up/down when starting + some filtering/saturation/noise
tape = tape-deck style dirty start/stop + saturation/noise + light wow/flutter

the modes won’t really have any tweakable parameters, or maybe I’ll build a single parameter that varies per mode selected (e.g. mlr gives you an option for quantize size, glitch gives you an option for “glitchiness” etc…).

12 Likes

yes

w&f param for tape
aux busses

new ui

it’s all looking great

Cool! I was just poking around the other night with porting a very stripped down core module to M4L. I’d like to use just the looping/granular features for an upcoming project. I’ve never built anything in M4L before though so I didn’t get very far.

I’ve not built anything fancy before, so I don’t know how MIDI learn and automation are handled, but I think as far as sticking it in there, it’s just a matter of using plugin~/plugout~ for audio and that’s it, although the size of the old module is not ideal for a M4L object.

Actually a few M4L objects will probably pop out before I make TPV2 as well (I’m thinking of calling them “Party Favors”). There will be the core thing, and then all the individual effects too.

3 Likes

Ha. Love the name.

I guess I was more unsure about how to handle the osc/monome portion in Live. I’m new to the grid and OSC in general, in addition to M4L. For instance, would I have to make a separate device for the monome/OSC stuff and then have it communicate somehow remotely to the Karma core devices on the audio tracks? Agreed that it does seem simple to get the audio portion of TBP working though…

It’d be harder to get all of TPV into M4L since everything is so intertwined. Plus I’m not sure how sending OSC stuff around like that works in M4L (can you send from one device to another?)

There’s terms, which is probably worth looking at, as it’s a bunch of monome M4L devices, all packaged together.

Ah, Terms. I wish I could get it to install on my system. Live kept rejecting it as an “invalid Live Pack” or something so I gave up.

I did, however, dig around in Re:Mix a bit (which is structured similarly to how TBP would probably need to be, with multiple M4L devices talking to each other) but still couldn’t figure out how data was being passed around. It may be as simple as using good old send and receive objects.

Maybe I should take a look again without drinking that bottle of wine first. :dizzy_face:

Anyway, sorry for all the asides. I should look into it more on my own first before I derail your thread any further.

just tried TPV 1.1 for the first time… whooot this is amazing work @Rodrigo
everything seems to work fine, but i get these errors in my max window:

descriptors~: descriptors~: No such object
descriptorsrt~: descriptorsrt~: No such object
morphfilter~: morphfilter~: No such object
morphfilter~: morphfilter~: No such object
multiconvolve~: multiconvolve~: No such object
Jitter initialized
sigmund~: sigmund~: No such object
dynamicdsp~: dynamicdsp~: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
entrymatcher: entrymatcher: No such object
dynamicdsp~: dynamicdsp~: No such object
udpreceiver: binding to port 12005
binding to port 17812
udpreceiver: binding to port 8000
udpreceiver: binding to port 7000
sigmund~: sigmund~: No such object
dynamicdsp~: dynamicdsp~: No such object
sigmund~: sigmund~: No such object
entrymatcher: entrymatcher: No such object
descriptorsrt~: descriptorsrt~: No such object
multiconvolve~: multiconvolve~: No such object
multiconvolve~: multiconvolve~: No such object
multiconvolve~: multiconvolve~: No such object
multiconvolve~: multiconvolve~: No such object
descriptors~: descriptors~: No such object
entrymatcher: entrymatcher: No such object
descriptors~: descriptors~: No such object
entrymatcher: entrymatcher: No such object
udpreceiver: binding to port 27769
serialosc.maxpat: 2014-may
udpreceiver: binding to port 25011
serialosc.maxpat: 2014-may
Gen working in runtime mode

i’m on max runtime 6.1, os x 10.6.8
installed the externals as described

am i missing something?

externals are definitely not working.
did you restart Max after putting the externals in the right place?
are you in 32 or 64bit mode? (right click Max and make sure it’s opening in 32bit mode)

And since this thread got bumped anyways, I just wanted to say that I’ve been working on the different karma~ modes (while brainstorming the architecture/routing), and am really really happy with how they’re sounding. I think @glia specifically will enjoy them as the tape/lofi modes (the ones I’ve gone through so far) are pretty detailed and flavorsome. I’ve sampled my old shitty dictaphone start/stop noise, hiss/hum, and nailed a sweet sounding wow/flutter.

I’m even modelling the start/stop speed warbles so it’s random each time, but still following the general pitch contour of start/stopping a crappy tape deck.

And rather than have all sorts of different parameter controls, there are presets within each mode, each with its own different set of ‘stanks’.

lofi mode choices:

Casio SK-1 // 8-bit 9.38kHz + aggressive compression + bandpass EQ + crackle noise
Ensoniq Mirage // 8-bit 12kHz + light compression + bandpass EQ + crackle noise
Akai S900 // 12-bit 30kHz + white noise
Akai MPC60 // 12-bit 40kHz + saturation
WTPA // dynamic bit/sample (based on karma pitch) + saturation + crackle noise + clicks

I’ve spent a laughable amount of time on the different types of noise/clicks/crackles for each mode preset…lol.

tape mode choices:

dictaphone // start/stop clicks + noise + wow/flutter + eq + compression + saturation
4-track // hiss + wow/flutter (less) + compression (fast) + saturation + eq
15 ips // white noise + same but less of everything
30 ips // little white noise + same but less of everything

6 Likes

Rodrigo
I just wanted to ask you one more question, I just traded an MI elements for a Shbobo Shnth and watched the wonderful mini doc from the workshop and curiously enough I studied JI and raga or (Shraga as might be what the cool kids say) :slight_smile: since 1995 so I am loving the SHNTH and shlisp and fish. Does Party Van work with the SHNTh?

Yeah he’s an amazing guy, and I don’t use my shnth nearly enough.

TPV1 works with the shnth by using it as a controller. In the setup window there’s a section where you can map all the different barres/butts/corps to different TPV1 fx controls.

indeed

i am salivating

very nice, thanks for the reply!

alright i figured it out, very stupid but i had a max 6 folder and a max 6.1 folder… guess what, i copied the externals in the max 6 folder path and tried to run TPV with max 6.1… after putting things in the right folder the max window was very happy again :slight_smile:

1 Like