#61

re: aleph and m4l versions-- i’ll try to find time to port these, but anyone willing to jump in and help would be appreciated. i also have to figure out if ableton will give me an NFR of a newer version of live-- i have 8 and it’s no good for m4l anymore.

2 Likes
#62

can’t wait to get to know this version, thanks for all the thought that went into it tehn. would there ever be a possibilty of a trigger-on-press mode like boingg? it’s easier for me to make more intentional patterns that way, since i get to precisely define the trigger coincidence for two or more patterns at the moment buttons are pressed. even if possible, it seems like now wouldn’t be the time for it, but i thought it might be worth mentioning.

4 Likes
#63

updated for mono-brightness support. checkbox next to the device dropdown.

link updated at the top.

@goiks that’d be an easy addition-- i’m just trying to figure out how to make it toggle-able…

5 Likes
#64

i’m really considering swapping out my white whale for meadowphysics running this firmware…decisions.

1 Like
#65

Yeah! A great thank you for the mono bright update…
I just had the time to plug to see if it’s ok (it’s ok).Will try it later this evening.
I just have a 64,do I loose features regarding a 128?

#66

If it’s like eurorack, all conditional rules are access via the right half of the 128…

#67

really nice additions to mp! :smiley:
can i make some suggestions?

on mono-brightness the 4th column (resets) can be just on for the resets enable?
it is bright all the time, i cant see which resets are on/off…
the same for trigger/gates columns…

another one: selecting the range on mono-brightness lights all leds on range –
is it possible to light only the start/end leds?
so we can see which ones are being triggered each time its resets…

last one: midi clock input? :smile:

i dont know if i made myself clear but i think these suggestions can improve mono-brightness experience :wink:

thx again! very funny times playing mp!

1 Like
#68

instructions/keymap added to the top post

2 Likes
#69

Can triggers and gates (toggles) be mixed, then?
This toggle (gate) addition looks like it will be very useful, thanks. mp and Rene will now play very happily together and I may be able to sell a module or two…

#70

Is the old link function effectively replaced by the decrement rule? It looks like a row would need to be off and have a rule applied to it for this to work. The auto start feature when setting the count would mean that linked rows couldn’t be manually adjusted…

#71

triggers and gates can be mixed, yes. a trigger will override a gate, however, if multiple rows are acting on the same output.

the old link function doesn’t exist. this is a reworking of the whole concept, more similar to flin. you can, however get some link-like results by having one row RESET other rows, not just itself. you can also have one row just be a master RESET for the rest of the rows (this row could reset itself, or not.) TT can RESET a single row or all at once as well (0 does a full reset).

II MP.STOP x is also implemented in TT.

you can use the STOP rule in one row to halt another row as well.

so lots of new options, and you’ll get generally different results. the old version is still musically interesting for sure, but it has a narrower set of configuration possibilities.

#72

One thing that i’d love to see is a pendulum rule within a range. No way to squeeze this into the code ?

2 Likes
#73

@tehn - typo here, at least in relation to my MP module (which I’ve just updated):

On my unit:

toggle is 6
trigger is 7

ps : v2 is excellent :boom:

#74

Is anyone using this with sum? I’m not getting sum to see mp2.

#75

I’d gladly donate some $ to anyone who ports this to m4l.
Also this simple grid patch would be awesome to have in m4l.
grid-midi.maxpat (12.4 KB)

1 Like
#76

i could help with an m4l port, just seems a little soon (are there going to be any more updates?)

one thing i’d still really like to see is teletype integration. i’ve had some seriously insane results with mp1+teletype. Teletype 2 for max a possibility?

1 Like
#77

At some point i dug a little into the interaction between mp1 + teletype. Seemed like the communication was pretty simple (a send object which transmitted trigger commands 1-8, I believe) the toggle feature might have complicated the data which mp2 outputs a tiny bit, which would need to either be filtered out or handled a bit differently in teletype, but you could probably translate all this fairly easily. Obviously things could have gotten vastly more complicated and I’ve not dug into this at all on v2…

Teletype-wise I always found playing w/in one preset loads of fun, but that I couldn’t get presets to advance properly, if I recall notes in the kslider was kind of pesky and I had issues where the preset would update, but the notes would still be from the last preset. I wasn’t very diligent at searching for fixes to this . Would be curious to see if this issue was improved in later versions.

#78

Warning :
i’ve crashed my MP module at the point it became unusable until i reflash the firmware.
i plugged a 256 instead of a 128 (cause saturday i am gigging with both a 128 and a 256, not simultaneously so i thought ‘what about just bringing my 256 ?’). In the preset page, i hit the 9th row (first button) as if it were the 9th preset. Crash, a rectangle of leds lit, module unresponsive.

#79

yes-- that’s undefined behavior. the modules aren’t bug-proofed for the 256. i’d have to add code for that.

#80

i had no problem at the time when i had WW and only a 256…