#577

“Angela’s Confetti”…but it’s shortened to just “confetti” for colloquial use :wink:

5 Likes
#578

Hey Rod, How do I use the zxcv keys for psuedo arc button presses in TPV1.2? I see that they’re mentioned in the instructions, but don’t seem to work with just a key press. Perhaps I need to set something else up in Max? I’m using Max 6. Thanks for the help!

#579

I had to look it up since I’ve not really ever used the feature, but here’s the relevant bit of the code:

Screen Shot 2020-02-05 at 12.03.50 am
Screen Shot 2020-02-05 at 12.03.50 am1528×644 44.1 KB

So from the looks of it, it’s literally the “key” press from the arc.

In TPV1 this does different things in different places. On page1, for example, it scrolls through different options for each of the knobs, etc…

1 Like
#580

So I guess for some reason my key presses aren’t changing the hi-rez arc functions. I thought maybe I needed to have Max be “listening” for keyboard input. I’ll keep looking. Thanks so much!

#581

It should just ‘happen’, although Max needs to be the front-most window. (i.e. you can’t have a browser open and have that ‘on top’ of TPV).

When you press those keys, do you see the leds on the arc change?

#582

Will any of these, including the version of Tpv2 you released work with an older 256 walnut grid model by chance?!

#583

It will only show an 8x8 on the 256 (although it will work).

TPV2 is made for 128s only, since that appears to be the ‘standard’ monome size nowadays.

Because of how things were mapped/conceived, scaling up is kind of weird. Ages ago I started trying to make a 128 version of TPV, so you would basically see two pages at once. I never finished it, but that was my solution to that problem.

2 Likes
#584

Newbie here. TPV looks amazing. Do I get it right that there are no clocking options (max version) ?? The manual says “no quantization”.

And next, is this still true for the m4l pack ?

Maybe I am missing something…

LC

#585

No clocking in any of TPV stuff. The confetti stuff is a bunch of individual modules that all behave differently. Fundamentally there is no quantization there either, but they are more-or-less individual effects that have no need for that.

#586

Got it, thanks! Although I read that some triggers derive from incoming transients (thinking how one could use it with beats).

LC

#587

Stuff like that will respond to whatever you send it, so if you’re sending stuff “in time”, the output will also be in time.

1 Like
#588

i need to check out all of confetti.

@Rodrigo is there any chance a non-arc-coupled m4l chocolate grinder /cd skipping device within confetti? really any happy cd-skipping with some control within m4l?

#589

I’ve been mainly recreating the ‘fx’ modules from TPV1 (including some new ones), but I’ve also been thinking of some other things to build. A glitching CD-type thing is definitely on the menu. I just don’t know how to best implement that within the Live universe/paradigm.

I have a good brain for standalone-type instruments and such, but it would be silly to just create a standalone thing that sits inside Live and ignores everything there, but at the same time, it also doesn’t make sense to have something glitchy that is locked in with the Live transport etc… So kind of conceptually unsure how to proceed with that. Sound and feature-wise, that’s more or less sorted as I did a bunch of cool work on that a few years ago.

2 Likes
#590

do you remember the m4l port you guided of monolase recently? choc grinder m4l could be a similar idea in terms of being amazing on a send channel to just throw anything one want sin at any moment to capture/bufferfuck (but in discskip paradigm). definitely no need or worry for clock/sync. yours i see as petr B thought which is fully async from any idea other than itself by design.

#591

Yeah totally. I’m big into async stuff, it just gets weirds in terms of how people expect Live to work. For example, a project should open up how you left it, as in, buffers in tact. Max doesn’t work that way (and is a good thing in my opinion), nor does TPV/CG/etc…

So I’ve thought about ideas of bringing things in/out to clips directly from the device, so it’s more Live-like, but then it’s kind of useless inside Max natively, etc… So not super straight forward.

1 Like
#592

the monolasem4l definitely doesn’t leave sessions intact between save/cycle. it’s oriented to live input/interaction. cg is more oriented to me as drag/drop or live input, many live devices can be like that. could have modulation section to replace arc or grid control?

#593

That’d be the idea. As in, using native live.objects so you can use any mapping, modulation, automation, etc… that you want.

You would lose out on the really slick cg-style animation of what’s happening, but that’s not too big a deal (if you then have access to all of Live).

1 Like
#594

the animation is cool but the sound is the importance imo, those variable click samples, transport forward and back like ff seek on discman, “window” placement and size and bam. probably definitely just one iteration per track as layering in live as many as desired happily possible

#595

Yup, all that is there, and much much improved.

I created tons of new samples, analyzed a bunch of behaviors, and recreated things as accurately as I could (for the core mechanics).

I have a stripped back version of the patch towards the bottom of this blog post:
http://www.rodrigoconstanzo.com/2019/01/rhythm-wish/

3 Likes
#596

brain… reeling…

it reminds me i read that incredible post already but was so engrossed in trying to prepare for gibgab that i couldn’t focus on this aspect and then later got overwhelmed in max after kadenze course lost me and everything working well with raja patch and monolase m4l so i drifted off…

2 Likes