Random distribution of speed. The reason I’d tie it to tilt is to keep the randomness within sensible bounds - otherwise you could have everything squeezed into one segment with the others taking up the slack. So use the tilt division of speed betweeen segments, then distribute it randomly.

Ah right. That’d be much harder to pull off as I start with a known ease in/out formula, calculate all the possible step divisions of that, then compensate (invert) it to handle the monome visualization. Plus given the ‘time-line’ nature of this kind of mlr display, if it was herky-jerky, it wouldn’t really communicate a ‘playhead’.

Thinking about it, it would be more possible to combine the ease in/out functions so you have kind of S-shaped curves, and there’s lots of possible combinations of that, but then it becomes difficult to manage how to navigate that. As it is, there’s even more aggressive in/out functions, but I picked the first three in each direction.

This is a really good idea!
I worry that it might get too nested in terms of legibility, but a good solution to that would have whatever choice you pick (for the gradient area) be ‘sticky’. So unless you want to go and change a different thing, you don’t have to engage with that part of the menu.

I’ll think about how to best incorporate this idea, but I definitely like having a multi-purpose gradient area with different visual signifiers.

In TPV2 I was going to move the tilt stuff into a more global alt setting area, and figure out something else to do with a row-specific alt menu, but maybe all of that can get folded into one, especially since I plan on moving the slice/grain/combine/pattern out of there, and into the fingering system.

edit…
Actually splitting this into “configuration” stuff, which can go in a global alt menu, and “performance” stuff, which will go into a local alt menu is a good solution I think.
So things like overdub vs replace, playback mode (karma, mlr, tgc, tbl), mute groups, buffer select can go in the global config alt, and things like pitch, volume, tilt, can go in the local perform alt.

4 Likes

However this might happen, this would be my number one feature request.

I like the sound of a global alt menu for configuration and a local alt menu for performance.

do you have the full version of max?

i’ll take a look soon but working on another project first

Ok, beta3.

Pattern recorded is implemented now, so feel free to give that a spin. Also added individual volume controls for each karma core (built into the actual GUI), fixed a couple little bugs, and tidied up the code some more.

http://www.rodrigoconstanzo.com/party/blockv01_beta3.zip

7 Likes

Acted oddly when I first loaded, closed it, and reopened… and everything seems to be working fine! The first time I opened it, I loaded a clip into a slot, and it played back really fast… not sure why! However, everything seems to be working fine now! Love it! Is there any way you can add something in alt menu to start and stop pattern recording?

The live recording feature is acting oddly… It records really fast… and a very short 3 second or so clip… Not sure if I’m doing something wrong? Also, when I try to load in a new clip over a recorded clip, it will not replace it. It acts like, once I use a track for recording, it stays that way… Also, the live mic in stays on after stopping clip record?

I was also wondering about a added feature… maybe a button on each track that will open a window to files that I want to load in the tracks?

This program is absolutely dope though! Awesome work man!

wow just on a lark and assuming it wouldn’t work (as I’m on a 10.6.8 machine) I tried out the beta and it worked just fine
I have no grid at the moment but all the module controls worked

thank you for more inspiring work

1 Like

I suspect what might be happening is you’ve dragged a (short) audio sample onto one of the players and then tried to record on top of that?

The way the ‘dropfile’ thing works is that it resizes the buffer to whatever file you drag in, and it’s a one-time-deal, so if you drag a small file in, your buffer is now small. I hope to change this with an update to karma~, but since it wasn’t really built for that kind of thing, this is the short-term compromise.

Similarly, not currently way to load a buffer in manually (other than dragging it). I might change that in the future, but would have to see where I would put that.

1 Like

Cool! Keep,up,the good work and I look forward to tpv2! Thanks for the write back!

Correct. GUI button seems to freeze in its “play” state but it’s not playing, and no pressing on either the monome or GUI button will change its state.

Yep. Buffer data remains intact both in sound and visually.

GAAAAH. Weirdly enough, as I was just typing this post it sprung back into action and is now working perfectly. I wonder if I have a dogdy grid? I’ve had some weird led glitches recently and it seems like I’m the only one having this problem? Shoudn’t effect the GUI though…

EDIT: This is in beta3, btw. Also haven’t had the “playhead” disappearing glitch happen yet in beta3.

I think this probably has to do with the same karma~ bug I mention above. It could still be slipping through. I’ll extend the delays between things for the next beta while the bug is getting looked at.

https://soundcloud.com/zunaito/407b

beta 2 and 3 look nice but wont recognize my grid (this test is made with 1)
reverse fingering is not usually recognized…everything else i checked is slick

4 Likes

Weird, none of the monome/serialosc stuff has changed for any of the versions.

I have noticed that with my desktop computer, and the latest serialosc version, if I quit any monome app, when I open another one, my grid wont show up in serialosc at all (until I restart Max). Does it show up if you quit/restart?

Just dove into this thread for the first time. Going to give a go at block party.

It’s been so long since I used a max app that wan’t m4l.

Is anyone using this with ableton 9? I’d like to use block party in conjunction with virta in ableton for vocals.

I’m fond of SoundFlower for routing audio between apps.

3 Likes

yep thanks for the tip

hey @wednesdayayay

have you tried shnth mapping with this yet?

I do plan on rebuilding a bunch of the bits of TPV into M4L modules. Actually currently figuring out how to do the audio/fx routing, and I may go with an M4L-ish layout/size for fx, which would mean refactoring stuff into M4L-ish stuff sooner rather than later.

As a side note on that, really really revamping the fx/routing options, so it’s going to be an almost DAW-like amount of fx slots, in multiple places in the audio chain and stuff.

I just looked at the code, and it looks like the shnth stuff won’t work because it’s hardwired to controlling the fx modules…which aren’t there yet. I thought I had it so you could map it to control the wtpa modules, but it’s only fx stuff. Whoops!

3 Likes