Help me replace matrixctl with live.grid?
When I was starting my latest patch I couldn’t figure out how to configure a live.grid the way I wanted and ended up using a matrixctl. Now I’ve sussed the matrix mode of live.grid and want to go back to that but my patcher is using the matrixctl approach of sending out changes e.g. (row col sel) -> (1 1 0) rather than the live.grid approach of sending out the entire configured matrix on each change.
Does anyone know how to get live.grid to be compatible with matrixctl and send messages for each cell change?
hope this helps
(in case you dont know, copy the code below. go to max -> file -> new from clipboard.)
----------begin_max5_patcher---------- 1157.3oc0Y0sahqCD9ZVo8cvaTu6PYicBAxd244nBUYRLfOahMx1gROqNu6G ameZBj.oTZfppFCy3L9ye1yLdL+46eajyR9dhzA7KvSfQi9iVxHqLijQkBF4 jh2Gkfk1N5rJgyxRcFWnimoRHJ0qaI4lwnGqbFCbVhYqc.KJ63VrJZCks9YA IRk2Wu.2ItiAnv.SiGx7DNeh6auzJNSIo+q01PSmKjqQ.koGWKjfkRowVDxW 9OO564T2FLbp0FN+sfhSbpYlb7asCxJ8+992Ls5lw8lSh3ooDlpxtJxd6TTO oi9MPsg.XjW.6vIYDIXoUFeMYihHbNA8.mZYDu7FXvzOJ+rRrdYgoMlxs5Ar tMqwhdg8gEMy1HdBWbda2jvcu9D9S+3QvrE.JaGQnj.Wf9qZxV+3QfFLKIQ3 LIwtjjvegH.B9K.9JPJVIn6iThD.UBlo6Yl53dkP2QlrVPiMcRaNJCDg0l6U dlnvDfMXodsx7FRibPZlTALioAZvfEZFAkq0J.s.fYw.IGvYSlLoZFkPYjHd FyNs7NwtDen06AMCk6K4YZ7gC4tj4e01krhJLKJrJ2SuRmyS5OFlSwHeKhgy Fd+wYe0X5+ROaq75zb.MMK8HOIcWzpN1Mz8TqF9t4IMxSgL6FrXDbmtXny0n wWqqEcm1lZhzbxj0n5DtNY8zKhuQswj9u+j0v6M5I3yidf2CziIw5GmeJRSc c4G2gjeRIRIdM4XBRRTQjjDvCPvCHvCdcSV8yQKOaybX9g+tJLEJ7dXmjMqK Df.eXJJ+jwggWXreu1nnYCIE0YdScJirTF3m1Sd9y7SmbxCmfbma8u7sMPW+ AOeHx+NMe3UrhUeW2Zr7UshUDZHqX8SnJ9OCNw8qJmf9z3D37gjS5JFdQsSt l+N8oBF2noWrVdAVWbX8VYsf2Oq4cwrVU0MUVdGVTMlGqMOZu8cm2cJwws7e e3S+hBVKtGISyaul4lHZLt4kfkxiIM3xsXgF+Jh3YBCuLooxXpYPoblMPcuO NBzqClOnTrDuiD+LVogzxLE4sOIKn+R92vv5Tj7UkxqTTG5T1JtczKG2FZ4h Xhn9Lng1LFMGbs+xxsDRbBMsy2WpHakcpkreKmQxusG3jtAf50Bpu0tjp2EZ 0hlMoiNPyWiZWc4tMuwsRdTk1Yo15e6yyMbgp685GXxcTI8fcSMALO9byILi wUXytumqF1VGMc3808DXlg8jLUBk8ais5dE0XhBmH2B0EgRd6CW05OhRHXwk dhZzT6sH5Wu50qSMGPzfVcV0EH0MSjPk17Q119D.M38D+7rohB5YR57wvdQv G9SzXgpQwATgjmIhJmlk+LHfZnMlHUTFtLT8SucAC060FZbLoYr7TZ7VtNAd AR.K5dEp2fyT294A2gSggBb98AblpEuAfybFvdrr5eaXNXuYN3fCNTu1yc3N ygBbg8AbvaiCwga06XYM71.NTu2ygFdu0flCaGfCcaBkDzzOrCv4d6.24cHl eS.W+vVvsg35k+v6FanfolSFNMz7zCEV9kivrQft4+kLd.6F -----------end_max5_patcher-----------
I’m very grateful to for you trying to help me, thank you. Unfortunately I’ve just realised how my request could be misinterpreted.
In my device I am using a matrixctl to manage connections among other objects. I ended up using it because I thought I couldn’t get live.grid to do what I want.
Now I’ve learned enough about live.grid and want to replace the matrixctl I am using with a live.grid.
The problem is that matrixctl sends out a message for each cell change as a tuple (row,col,state) whereas live.grid – so far as I can see – will only send out a list of all cells switched on as [(row,col),(row,col),(row,col),….].
The rest of my device has been designed around the matrixctl approach and is expecting single cell changes. I’m flinching at the prospect of having to re-engineer the device to work with live.grid.
To do this I am probably going to have to create something that remembers the state of the live.grid and compares it’s output with previous states in order to generate single cell messages but I see complications ahead.
So I am hoping that maybe I have missed a way to make live.grid emit single cell state change messages like matrixctl. Or that someone might have already gone down this road and made an adapter.
If live.grid in matrix mode really isn’t drop-in-compatible with matrixctl then I’m pretty ticked off the Ableton/C’74 for the inconsistency.
Anyway thanks again for your help and if you have any further advice I’d be grateful.
I’ve written an email to C’74 support to ask them why:
live.grid (in matrix mode) has a different output system to matrixctl
live.grid uses 1-based addressing instead of 0-based addressing throwing out any notion of consistency
live.grid uses (1,1) as bottom left while matrixctl uses (0,) as top-left so they are not address compatible
It’s hard to believe this sort of inconsistency could be the product of chance alone. This kind of work requires a devious mind.
i can guess what support’s answer will be:
live.grid states within the help file that it is a UI grid of ‘steps’ and it is ‘designed for use with the chucker~ object’
whereas matrixctrl is more open-ended(does not readily confine itself to specific step/direction/transposition style use but is rather a simple matrix of switches(or dials))
they don’t work readily within the same message protocol because they are meant to do completely different things, otherwise, you wouldn’t need one or the other included in Max.
if you’re unable to reverse coffeencigs patch to get live.grid to change matrixctrl, then you can try to learn more about the [zl] object to help you process the lists coming from live.grid…
otherwise, you should really post your patch so far so we know exactly what you’re trying to do…
hope that helps.
Yeah I guess so.
It just seems like when you put the live.grid into matrix mode it would have made a lot of sense to make it compatible with the matrixctl object.
I think I can figure out an adapter to make it compatible, I just hoping I wouldn’t have to. Or I suppose I can re-engineer the rest of the patch state to take complete updates rather than individual cell updates. That’s probably the better long-term option but more work now.
Thanks anyway guys.
I’ve built an adapter that takes the output from a live.grid (in matrix mode) and makes it suitable for patches that were, previously, expecting the output from a matrixctl.
It’s not really generic enough to just "drop in" into any other patch as I made some choices about interpreting the output specific to my situation (the size of my matrix being the principal one), but it should be pretty easy to re-use.
There were two obvious approaches to this problem one of which would have kept the matrixctl behaviour of a single message (col,row,state) for each cell change, and another that involves resetting the entire matrix on each cell change.
The former would have involved redundantly maintaining state inside the patch. Since I didn’t expect performance to be an issue I went for the simpler approach which outputs the entire state of the matrix, as a series of messages, on each cell change.
Any comments on my patching style or solution welcomed:
----------begin_max5_patcher---------- 2364.3oc6bs0iqZCD94r+JrxKsUZ2Hay89OnRsuzSk5CmVcDAbx5VhAAj8bo p+2quAA1EHNj.gUpZkRhM2l4yyLdF6O1+4gUq2l9ERwZvOB9HX0p+4gUqjcI 5Xkt8p0GB+RTRXg7zVyHeNc6es9Q0gJIeoT18S.TUeriGROVlPJkW.R26tTV YA8aDYe3MPc2pyr7qYDkPrlx32v+Tezrvxnmor8eJmDUpNAKKH+hA9H4WV3M NOBv7eWeMzXo.wExmP1Nqa73YgGjOk0+BgkjB9Ux9iIg4MDaJqRpwh992GdP 7wiWGxjA1QYwOUdLKg7Dk8TBsn71.UChS1NRXxVBSHGYqdwIKqwhSME.RtFc zvC+tQSHuPxKnorFJ3p0mDSbfPvbUeZiDe4AwmDSNnuOIM5uIRoEV0YLY2kb ORyHrSmuDRZ8Q6yjxxxIEDVYXoVva9bCOlT9otGhZe7cgQjdu3Aw3Uq2mSiS YBgo0cPzc0i8i7QU0XaS4WdFrvrNt3xzzjsg4uPKnaSHsFO3F1gL5gvRRIUI WXX80QOjkK8JabuHrP9834hn7zjjV2J0QdoiiDSdgFQ9LMt7Y485Dp0JHTC6 mVtbs5+UtdQoGNvGupfuV9eefDlysMK.6RyAg.oeHfx3+T3IB19U.sjjyGpY 6AkOSp6MKjlW.BYw.9cOKLWd7T4oTHukpa0FvOsieuNHb..TwS4H+RDm0dNb J5o3yTgyQr7pU2fuC8cfrzBpv9R9HDcxCSDl.1FxeNbW8rikE.DWPKJIgwfz cb.qo9kPYjH9yRpjdMNP6XJvFGoGi1dBff8TQXUwawpHHHncCqsWEFAas9UO sgsxeSzDTU+xHupe73DXR7yhgXw3qX7POXxsNVOAnHxRhaJPD4a+5vvuACQu mvPN7ssxcfGgdBvOKWXC7yAdN7CErfvuCjhhv8jNwOX+nExLzp+7A5CLUXos 1jTl5Dxe.rz6JwR7Lgkn6.VpsEMGLc+evrevLPghHSAS6EDX1Ju+1XYNGJHf APT7XQzGMGUw9xubQmM1I5+ic1KX5ovRangVnvEjE5dUJnXyrCGmwlBerzeE nQodwG+6sq42Rz40StydmpDq8sNm2o26iPd7Zm3+wqioeX0djvpnzHAzV8c8 uOKTCUQ.k9tdtmCocWPgAG1BVT4J.emLf0UFhbcLCVcdeX.yg0bx96Llhke4 b1xEWR4AozXyJBrCUOPoxH8xMT8YeZtU+teMNPUErhqZ8MTWkOMyxB4xS0nx HvwLj.2KR.6AI9.oTsLWup982K.jNdto.DZD.T0ZBovIwZE0E5bZcWEKGWOK goTADGuaXqH8XdTkpqGOAs0kXRQIkUuZzer12+Um2yz331K5qbbgFmkRYkZw C7mFMLeoRssgRsyhRpcLTp8FmTawSDVr+TX85VYW2ZhzGdpK.zzY6frrjE9n 7+zZmr0DpOXCGePiPebT6enppNrqecqIRePFZu4tn7RDRikARsnn2QYV4gTN F58rrtwTMJ.MbXveQML3YnTiPKJwFYpQOZYMiFxdZsRzSGXY6cxpW1XhzGeS GFF4jcJMvVMWmaPciITcLYpNzHikhfM0GjyjqPtWf41XlqCorvTqBhV6jslJ +GSiWYMtAHsIlZYzBN0XpTG2oUcprvLSezcxULEAbJBegD+I9imWjzmBKKyo aOVppHoIgb1mjtMLQyVm50Jnl1IcRakolqKFbJ8Q6lGNgJWHYsZu01mV8meR xEDBHJM43AVA.sYiOHmnIDjfCHJCC.KkO5Cfa1TstrsYjgUmL7BNLCu5Zs.T Ylp3hAxyWtmi98PiqZxCboz3BcCo6FGrHrXPAYNX4lldENpLGCfCxxs58y9N BOyFOIqRl1HdRVuep2SdRNqFNUzHUU424Lbrt+FNGYYgQ+MfBnciN3QX+7nw lQd9vt2kp13D99iSkfDPxsAhZsh8CrNjdpTDU4w2O3rDBNGJsf5yF5l5gosb BP8r8PsAG3HAGq2qAfpWrCSB.AclQam1LunwTWHvSn4HzLTS4uFdUndR4Ivc Fm35b4Llm9YYBidsSXrQUB5rFQScVi58jsp1U+fgRazycID0d6sJpcM6.Fz6 yq4dWObjam4bVs9rw98mILtYUDg9hvlJjANlEKL51kmdPya8WHaDz+GHBjw6 hV.BKNQo8160GfxhRNFKtWhc4RbVjCYkeEDEVP5z1z4VUQihhPHUFEn.b0zC cg8V1KlIMmipYp3oBraB60IY6uiorK7Zo2Vu1ykOpFhrcLHkKLdALqIBfAV. afCvE3Me1P5kQR99Zz+zmidACtgFQBNLMe3hiSCBJ1qgCboY3.7mOHpJ.MJX HSm5Wzh4vzY6wxxT1vPP2gTLQesqe4HGHEbmodZl40OvFZfevRXcOTTnGNSU zqK5.qV0LW6gPmfkB3TTRxJlI.pJwYrAksNmEs1h7g8jiZ+Ugif3dncXWjsr S5F9VpFdgZPSFyYZHNSFpbMPyr5Tyf2HMquZZ9MYIJwgYBVLy+IO2OBKV8hx FkxdgjWJKLQ81vJdEXqqw4OXeOkIdoayoeAbfWT8OHt5TPHu.mbJuDa9IqmX sPe61Q2eLm.9ClzoIW89.SBidVbthGSVZg7MiFDQRDub.LdwOhh1K1Lo0pql sUkNqCdnB0uEoyJuusYqnZH70aGpdf7MaCZqc2zDN981c+ra9a7FiJSkHjiA hjHck4TlBLQlrlWYxjgNLdVkILxDYBNuxD1DYBMqxjiIxD5B86vdRRFTQ2bM +PrpYDx0IsnyHsyqCoIwHblWaeSBQD3NugHjb06bibx846RjJjsb6m8Tq1J1 xtt0UKuF4WzlIey.JZahTAm4oIgFMOI5BC1pGM80qVYiVWMJZYr7hLWd0jVO PWnmqkpNlqOnGFajqi2nbcr800kp2ImlsbvxrFQ1RnW15pgdOSlBz5RUEk.p Vwe8zMxVWKxCMUZu.6jJ4yW+pF4V25pAWSDW6Q4EFX2LBqr0MYFgymI6kZKn PWMsRbN03pyw07fFXyEWk.5qo+R.pt00lBfqwf6kDhCpHOpdI9z+WeoUKW8Z 7F.Emor0MHaFzMWST.u9+fEZYucqaulfMyDBMy4TXzzK1WZI.AxW4oZVB50h yfpVPuFurWxVWqtXaVlHWS4w7F+6C+GPlHwBd -----------end_max5_patcher-----------
Forums > Max For Live