#283

Real bastard that error.
Are you on Max6 or Max7?
Has it ways happened throughout whatever betas you’ve tried?
(Are you on beta5?)

I’ve made tons of changes to the code (though not the core monomeControl stuff) as it’s kind of closer to TPV2 now, and I’m currently away from my monome (the 128 anyways) so I can’t try figuring other ways around it, but I might just try to sum those two lists “manually” to see if that changes anything.

Actually, try this out. I have basically taken the vexpr that I remember throwing up the errors and removed it, instead I’m manually unpacking the lists, summing the individual components, and then repacking the lists. Pretty awful/clunky/sloppy, but it might work. Either way it’s worth testing (I can’t at the moment).

If this works I’ll tidy it up and push it forward into the more recent version.

monomeControl.maxpat (530.1 KB)

#284

Max7, beta5, and thank you for caring that totally worked!

1 Like
#285

Oooh, promising. @lintfresh can you download it and have a test as well to see if that fixes your problem? If so we can call that bug (inelegantly) fixed!

1 Like
#286

dude this shit kicks so much ass holy hell

2 Likes
#287

whoa whoa whoa… whoa!

#288

Yo!
I’ll check it out tonight and report back.

#289

I think I figured out the serialosc drop down menu problem! Inside the serialosc bpatcher I put a loadbang into the 0 0 message box in the top left corner. Seems to have fixed it, but I really don’t know max so someone more competent should try it out

Wooooooooo

#290

Rodrigo, Am I missing a link to an updated TPV somewhere in this thread? The github link from the top of the page shows no changes for the last two years.

#291

There’s “Block Party”, which is kind of a party van 1.5.

The info and download link are in this post:

#292

As always Rodrigo, you are the man. I’ve been meaning to get my mk128 out to play for a while now and get back to music, hoping this might be the tool/inspiration to start noodling again.

1 Like
#293

Hell yes, @Rodrigo!! It works great now.

So, what’s the best way to share this little amxd? Do I need to bundle it/consolidate it or anything?

#294

Sweet! I’ll tidy it up then.

I made a project out of it, but then I had to manually drag all the files as it doesn’t seem to find dependencies well, and that should be it. The MuBu thing for the concat had it’s own extra dependency but from what I remember you’re not adding that bit.

Actually even easier would be just to take the shared Block Party project, and take the ‘Externals’ folder from that and just copy that over.

#295

Just a random bump here to say that I bought a couple of Myo controllers that I will be incorporating (at least one of) into TPV2.

Was in Montreal for a couple of weeks working on music stuff and one of the guys involved in the project (Patrick Saint-Denis) uses the Myos a bunch, so I was able to try his out, and test some mapping ideas, etc…

The gesture recognition stuff is slow, but I was able to get instant triggering from the EEGs by summing the absolute of all of them, and taking a scmitt-ed threshold of that. The cool thing is that while playing drums I could consistently trigger something in Max just by squeezing the stick tightly for a second. This didn’t impact actual stick playability either, which is exciting.

Long story short, Myo support coming in TPV2.

IMG_6330.JPG3264×2448 1.83 MB

3 Likes
#296

Oh! Could already think of a lot of ideas about how to implement that in a live set. That’s a very exciting news!

#297

oh wowowow… i am so late to the block party. just had a go with it and i’m completely delighted. thank you so much!

@Rodrigo i’ve gathered that the primary focus behind this instrument is free-form, asynchronous sampling, but do you have any thoughts on sync capabilities in the future? even just quantized record start/stop would be enough for me - though i could see some interesting clock div/mult going on with the tilt settings.

4 Likes
#298

A core/philosophical conceit in the underlying karma~ is such that is that it’s an asynchronous object. Since it functions by taking messages rather than signals even if you trigger two karma objects at the same time, they very likely won’t be in sync (in a “sample accurate” sense), which might not really mean anything significant but could create weird phasing issues with certain types of material.

That being said, one of the changes to karma~ will eventually be having a sync output (like the groove~ object) allowing karma~ to act as a transport for other playback objects (though not other karma~'s!).

BUT, I do plan on adding Fugue-like playback where each karma_core can access the same buffer and be “kind of” in sync, and at different speeds. In that context the sample accurate-ness isn’t so critical, so it should be ok.

(@RABID has been working on a looper object that’s all about sync stuff too, so perhaps I’ll take a look at that when it comes out and swap out the core playback objects when someone goes into ‘sync’ modes or something.

6 Likes
#299

[quote=“Rodrigo, post:298, topic:247”]
(@RABID has been working on a looper object…
[/quote]i love how you just drop that in there like it’s not incredibly huge news on rhe horizon

awesome

7 Likes
#300

I hope it wasn’t a secret!

1 Like
#301

This sounds amazing. I’ve been thinking that it would be nice to have a sort of “doubling” selector for each row where the double is an octave up or down, but full on Fugue would be even crazier.

Also, I made a github repo for BP, so that I can have the versioning safety-net of git for my own changes to the project, which seem to be growing.

Let me know if any other language around “who wrote what” needs to be in the readme (I realize putting the externals and impulse responses up there may violate someone’s license, but maybe that can also be resolved with readme language). I’m definitely not trying to take any credit for anyone’s work, but I do want a place to keep snapshots while I break everything trying to add my tweaks :wink:

1 Like
#302

It won’t be as super slick as Fugue, but the idea is that you can have each karma_core access any of the four buffers (TPV2 will have 4 karma cores, instead of 8). I’ll probably then integrate some kind of cross-row binary “fingering” to do common combinations (normal + octave down in reverse etc…).

Awesome. Thanks for putting a repo together. I’ve totally not gotten around to making an official repo as it’s still in a non-functional state since the UI rebuild. Rather, it works, but it’s just 1 channel at the moment.

(Although in thinking about it, what I’m actually working on now is really TPV2, so the BP repo you’ve made is as current as I have too in that sense. Once I get further into TPV2 there won’t really be a BP anymore, as it will just be TPV2.)

(And on that note what I should really do, though my git chops aren’t that great for this kind of thing, is create an experimental branch of the existing TPV repo and do the revision tracking for TPV2 (formerly BP) there.)

The readme and stuff looks fine. One thing to be mindful of is that pushing externals through github tends to break them. I don’t remember the specifics, but it turns the .mxos into ‘containers’ (or rather exposes them as containers, as that’s what they are), which has ramifications in terms of the underlying permissions. I don’t know if you’ve done something to mitigate that, but when I tried doing this for Cut Glove whenever someone downloaded the externals this way (mainly karma~.mxo) it wouldn’t work. So I added all of the externals to the gitignore and just included them in the zip download.

2 Likes