back at it – MIDI mapping still treating all parameters the same.

when I open up the karma_sampler subpatch, I get this message. is this potentially my issue?:

also, when I try to verify the scripting name, I get nothing:

tried it on two different controller, same results. anyone else having issues with the MIDI mapping or is it just me?

I actually ordered a cheap MIDI controller the other day so I’ll test more practically, but it should be working ok if you see different versions of the names in the [r hover] thing.

Do you see different 1karma_pitch, 2karma_pitch names if you do the [r hover] -> [print] thing with beta4?

If you are inside the actual patch, you’ll only see the “#1” version of the names, since they haven’t been opened with any arguments, but the beta4 should have resolved all of that stuff.

nope. :confused: for reference, was hovering over 5

Balls, looks like I uploaded the wrong one when I uploaded beta4. Swap this file out for now, and I’ll put up a beta5 later tonight.

karma_sampler.maxpat (308.8 KB)

1 Like

Here you go. It looks like I’m mucking something up when turning things into projects, as it’s fine in my local version, but when I turn it into a project, it’s converting the scripting names into “1karma_pitch” instead of “#1karma_pitch”.

I’ll have to play with it a bit more to see what the issue is…

But in the mean time, I manually changed the files out:
http://www.rodrigoconstanzo.com/party/blockv01_beta5.zip

in business, baby! irony is that when the CPU load goes up, it makes manipulating those parameters draaaaag. but I am glad for the fix, thank you @Rodrigo!

1 Like

Size/Position

Fonts

Colors

dark rainbow

light rainbow

dark og

light og

logo

tpv2-logo.ai (170.0 KB)

sketch file

I hope that’s helpful to you @Rodrigo. Let me know if I can do anything else to help.

5 Likes

after a week of resting my eyes and looking at these again

dark rainbow is the clearcut winner & makes too much sense to try anything else

serious props

2 Likes

Thanks @glia.

I definitely agree, but if @Rodrigo thinks theming sounds like fun, I can get behind that too. I can even imagine exposing hex codes to the user is a settings screen, and making those settings exportable/shareable. People go crazy customizing their text editors in such ways.

Of course, they might be doing so as a way of procrastinating on their coding tasks. :wink:

1 Like

so much subtle beauty in this new iteration

rodrigo’s last mock up looked great (if a little too “madrona” in retrospect) and made me feel like your first attempt was almost unmoored with all the lines removed

the simpler lines included and the rounded corners on each wav window are just enough to tip this over into near perfection

really curious what other improvements you both might make

3 Likes

Dark rainbow. Super beautiful that it’s even worth more than 20 characters :slight_smile:

2 Likes

My twopeneth… I like Dark Rainbow too - especially in low light, which is where I suspect many people would be using it. If the background is bright then on a screen it becomes a light source which makes it more difficult to jump between looking at a bit of hardware and a screen. The colour coding makes things clearer without tipping over into gaudy, top stuff!

If I could put my oar in for a feature request, which may well already be there, a pitch control for the playback would be really useful. I have a basic single Karma looper and my go to trick is to grab a loop from whatever I’m sequencing and then tweak the pitch by a a few percent one way or another to either keep it in time with the original or deliberatley let it slide out of time. Along with the retrigger this is all the control I thought I’d ever need, until you posted Block Party, giving me access to re-triggering anywhere inside the loop. Can’t go back now!

2 Likes

Holy shit! Yeah, all the little changes make it really pop now! And thanks so much for putting together such a thorough spec. I can’t state this enough, but your work on this has been invaluable. I got a little bit of a direction going, but you’ve completely blown it out of the water! Plus with all the color/layout/weight/font work you’ve done, I can easily apply that to new areas/additions, as the general design language is now put in place.

Yeah I agree, it really comes across now as having a ‘look’. And although I might consider adding a skin choice down the road, this is definitely the way it’s going to go. I guess it all depends on how easily I can setup something like that.

@sensum_clunch. As in the main “file playback” in the input section? I think what I’m going to do is build a “karma” fx module, that is simply a karma module without (all) the bells and whistles so you can record/overdub/half/reverse/pitch/gain and load files in to it. With the idea being that you can have samplers/loopers at multiple points in the signal path.

I’ve just been wrestling with how to handle a complex signal path and having audio going to/from the loopers really complicates things. I’m still going to have dynamic audio routing and assignable ins/outs, but it goes really difficult when you involve “thru” audio, with loopers that can feedback into themselves. Still more brainstorming to do, but either way, having a ‘karma’ slot will resolve all of that stuff.

2 Likes

All this design progress is looking fantastic, fellas.

I’m trying to do a quick and dirty port of the basic Karma core for an upcoming project to M4L and am having some issues. I’ve stripped away the combine, brain, and pattern recorder modules, and am trying to streamline just a single instance into a M4L device. Problem is, I keep getting a stack overflow from the vexpr object in the altDisplay subpatch in the monomeControl patcher. I can’t seem to figure out why or how to fix it. Any clues?

There are a lot of send and receive objects so I’m having trouble following dataflow. I’m assuming I’ve got a feedback loop in the control/monome area, and the monomeControl patch does feed back into itself through a route object the Karma cores, but I haven’t changes anything in there as far as I can tel that would cause this…

Yeah I had that happen too for a while. As far as I can tell there’s not a feedback loop anywhere, so I suspect vexpr only tolerates a certain data rate before it thinks it has a stackoverflow or something.
I was really pulling my hair out for a bit, and don’t remember what/where I resolved the issue, but I did see the message pop up the other day when I was opening a subpatch on its own (?).

The feedback loop isn’t really one as inside monomeControl the outlet doesn’t speak to the inlet (the in only drives the animations, while the outlet comes from the fingerParser control messages).

If you post what you have (or email me) I can try to take a look.
Alternatively, if you’re not using the grain/combine/slicer (or tilt settings?) you can remove the altDisplay section altogether.

Great thanks!

Def using the grain, slicer, and tilt. Just yanked out the combine module.
What is the best way to share the patch? Should I do the text paste thingy?
Sorry for the noobness…

1 Like

Ah right, you only pulled out a couple of sections. I misread it originally that you were making it just a karma karma module. If it’s so little you’re removing you can also just disable brain at startup (loadmess 0 it or whatever), and just remove those bits of patch from presentation view.

Actually, brain won’t do anything as the audio analysis stuff lives elsewhere in the patch, so once you strip that away, it won’t do anything. And pattern recorder/combine both use next to no cpu when not engaged.

For sharing, you can attach the main file you’ve made (unless you’ve changed any subpatches too), or just zip the bits together and attach that? If not, wesharing it.

I know this conversation has been going on and I’m a bit late, but I would personally avoid italicizing the smaller text, it detracts from legibility and with this much stuff to look at, legibility is already being pushed to its limits.

1 Like

I don’t disagree. I believe that snuck in there as part of the homage to Madrona, but legibility is definitely being stretched to its limits. I already specified a heavier weight for the italic text in an attempt to mitigate the legibility issue. I’m on a flight to Cuba so I won’t be revising anything until after 5/9. Im sure @Rodrigo can make the call whether to italicize or not.

1 Like

oh yeah

have fun in cuba!