monome / crow-max-and-m4l Goto Github PK

hi @dndrks

sorry if this could be handled more easily somewhere else...might be a simple fix but my w_synth m4l device looks like this:

screenshot of my device

i haven't experienced sonic or control errors, just a slightly wonky UI

This is minor but could lead to some confusion. In Max 8 when either the light or solarized UI themes is used the text in the object boxes ends up as black text on black background.

Default theme:

Light theme:

problems

• 'stream' data causes zippering when mapped to an audio parameter like panning or gain. this is due to Live not having internal smoothers on those parameters.
• v/8 + trigger sequencing is behind a step and misses triggers.

solutions

• incorporate jit-based smoothing and [live.remote~] to reduce the zippering effect
• don't use 'stream' to get v/8 information -- rather, track changes on the trigger input and get cv state on-demand.

if Live is in Dark Mode, certain text elements become white instead of the specified black, which causes them to be illegible against the yellow theme of crow's UI.

fix incoming

when scripting inputs with peak, crow returns ^^peak(input) values -- these fail to get through [crow]'s parsing, however, resulting in peak being sent back to the Max patcher without identifying whether its from input 1 or 2.

it looks like the issue occurs at [crow] > [p crowmax] > [p eval] > [p match-^^], which uses an [unpack s s] at the inlet -- but when it receives peak 1, only peak passes.

fix incoming.

^^jf_synth currently engages pullups and flips just friends into just type mode.

while it wouldn't cause a major problem to have crow's pullups engaged on an already-engaged bus (if TT was in the mix), it would be best to make this a standalone parameter on ^^command_center

it seems that a combination of quickly sending negative values to pitch and two decimal point precision values to level reliably crashes crow hardware. JF remains responsive, however, both to i2c messages from other devices on the bus and to panel controls.

this only happens in Max + Max for Live -- i cannot reproduce the issue in druid using the same circumstances.

to repro in Max:

• load the patcher below
• by default, pitch values are all positive -- you can change this with the radio buttons at the bottom of the patcher
• using the radio buttons toward the top of the patcher, you can change whether JF's level argument is receiving an integer, a float with one-decimal precision, or a float with two-decimal precision
• when pitches are all positive, level float precision doesn't matter
• when pitches include negative values, crow remains stable for integer + one-decimal precision values to float -- things quickly crash if two decimal level precision is used when negative pitch values are cycling, however!!

----------begin_max5_patcher----------
1933.3ocyas0ihhDE9Y6eEULYSlIiiotRAa1W1eGSuoCMVZWcTvAvt6YmL6u
8EpCn3EfR.Y7gVygFkuuSctVmxe9vjoOG8gJYJ5OQeCMYxOeXxDykxuvjB4I
S23+QvZ+DysMciJIwekZ5L3+kp9H0bc7bon7haiUIpvT+TcT3Sq0gpfncgla
iVbGg61DsKcsJ07kRJtpdg4qJ54W+pfT9kA2W5O1p.XNcJ5eJeN9oAunCW8T
rJHE9ubJdtXFR3fmimgXz7WoYut+yj8j0gkOXZ9090COj+xLKU.AQa1jQtyT
.aiRzo52Tn27WuSk7XXTnBEpV4e3hkelKpRtVkF9BJM7z50LfFQhk4uQHLi9
gUmlgzAMSn58LTblhYcj+hbqFzdz05pOW1wUeCqbjt.Uadwe.o3WPD64lSsb
Smud2J8jBhgXd4F5Cqscr+Bczp3ncasmNG758i82nRUwOoB8edsppQZWVFKM
UMKlLdsKikXJUso7AT9XSz+qppGD3EV4FVnSxg5B34l8bxdHCmYQx65Ltgn1
qL4cytmRLpJIgm+lnkndrALp2e8eH+kYq4nfnvrPVopEnzHTPbz6nufdcIRm
fzgnjeDl9BZSzB0LTRpebJJQ88cpvflCI1Z.ONqo.dFcBOKRWleBwSLZA7hQ
gQoJ6Wz6XpNJ3lHLzj407ZNd.spafdWZMpojRkFtPHMNY3iXWW8J1Gvl10jQ
YogxKEwkeqBWWG295UPNm9Um03Strmq8rSzM1wbn+tXm8bqi4JXX9Mla0EVL
CmJDAQQLD+xzTbNMIM38M6j+ZzfECoFM4FkNMGnQLbr1jTKK+HoNNyu.matD
wJTtsJFYlTDbWntXugm0oQqVs19bcdcpXQKYIToHkW95MOQeFAhiPDr8Ns0m
p+Y+vU1PRArTxFuFa0OFRdLjdwJ0X1VE.AKq9E+5tjT8Rcfoa2p5pKPbBEVW
gLNvhLWNjKu0w77N3WnBza7WiVqdSs1T85yqsu3GB1oopeDlhRoLSrIh.ZXE
OBVtIaiybpVlUXdNAPONUqm+5x4aW6+imdKRGn9Da1eLmtLKT4b5mebp8N36
WlWFElV1+EIuvtVSVk+IByhJX9x96Xs+5FzcRA3m6HLIvHPDcxcgti1McWk.
I2XkmfPtaUdjtp7Dijxqzq8Fp7pMTbVoDqxJlnaAi3dMxJYNcbcuiCEcM1CR
5XEHhaJojPMsLPgMs5dKPzUo4FKGItm2cqlizEMmGarBAAa8yuAMWW1Le2t0
nJA1MShq3Nd27Y7Nua9DFTWKzb1cx14yXC+14WrPRIdG1OeAtO6mO6z8ymV6
94ea1Rel8JTZGs9gpLXTq1Re9.tETPrv7Mq+SjOaeViNtI1tycc4NXJg5wEd
LWRtgBybQBggcERtiTlOaiwqi2z2iNsuufX+jWTIH8RzViEfNY+vc62LLHXZ
SQ5cbf4VXdi.ZgQYJFWSKhtWUZRWwnUZFLajLcnI1J8trGwqT44NV8Hh42sJ
ORGUddjQq.M2eSJu7QudY8A6BFSMt25lsjblk4obLTjeEUoYtCSPySN.RlmR
90Ol8IQ6hCJwW4f4PGdPKTIo5v86n32NLRcDY+MsQuXaTl0UwijC865.chTT
VsQZ+mHJdgJt9EIqAKu2fkA0QMFfUzevJoiDXyOpX80L.1AVAzpAGSOW5hDo
W3NexVHZK39DxcBtgC5j.bAKIQtzfaPXsqF0RWMgoemZLHv8CrN8Grft7hfc
j7rnV5YcKUj79C1iiYcCAK2JvhaxchRMoqkEMlWQpmq5bqbeDMgMgYqdjEgl
NHzWjYsuRaHSBM4CUMdhD9HEJd.TnV4F4XAr47JJTNu2HyyBf0XLctAJb.WU
D5a1FavkiE.SJq.Lor+Kk1fL2F8MnvxGozLClgwQRLJANnYFSP1QkhOP4Hsi
HtCCQDvwZrFhvu8DwizWhTbLlg4NYjNmHxQfHxdRjhI.JcX6mG3fmayJuWLd
XXh.NoE0vD1Xvj95tScJFvs4rtYjNmIN2dljOExVIhKo7LvVHbNToi.TEVCU
A1sdnJFAWVl0Pshv4P0s+8uwZApzFit3QmSEGZfCKp1NWgD2ANBet6kFi9No
NVz2ILStRfdhjW0dRk2fB9M7fzFOZzpNKjsTrG5EMVYjFBcbalwzFKqlaZUp
DZE+xNFBnYSE+DY6UBJfeCYE3jv5eoy1nzxmmV8saVjDlgKF0nydo9hMlsXi
zRbohjrE+fTNVpD2Rwfgahs3lUOtgJz7vUlh6IRvPcIdvcR5eCdmTmbWvcYI
x.R4t3J3tTZ3wsn23trGkhsLoTe6cS02RQusuKpJXbsuOo.qtf6hBuFYbaSu
hMECl4Nmc5fyYvuELBT0qQpuMmakaXikiQnE8EAGx4JR8DaLtsK80iM9AGnC
5sAvchYU5BtM5MnPpBjRk82ziQ6qsWohhejZi2e01oM90kR.J54a3KA3z9q6
B3JZstMvAiF0e612TwIEe+FbMci+qQPuKyLh5PPz7KmZZr5Mc48aN.JS8iCd
QmpBR2ECSt9CG3DqMM+.9DGtSWrwWYZjrGoY7x4S4NYqOPdyTne3WO7+.H14
.kA
-----------end_max5_patcher-----------

this one was difficult to nail down, but i'm feeling confident that it's the source of the crashes folks have reported with the JF M4L devices! i wonder if there's some high weirdness happening in the [crow] string parser subpatch? unsure, but happy to help test any potential solutions! also, lmk if anything needs further detail @trentgill !

cc @dndrks @whimsical-sam. this issue is moved here from the main crow issue tracker.

Query the 'correct' looking ports.
Determine what the port should look like (compare mac vs win).
Possible to attempt re-connect after dropped connection?
Possible to warn user that no device was found / dropped?

@dndrks for those not adventurous enough to set up druid, perhaps we should have a super-micro patcher that just activates the bootloader? (^^b)

it could have a link to the update docs. or even to github.com/crow/releases/latest (?)

then directs them to run flash.sh?

the LFO section is the most complicated, because at the time of release crow's LFO function was not syncing -- it would drift quite a bit, making accurate timing impossible. to compromise, I made an ASL action that represented an LFO which would be retriggered every bar. this was necessary at launch, but (hopefully) is needlessly complicated these days -- either way, it causes crashes:

• Max is experiencing Lua crashes
• if you do not select an output before selecting the LFO action, Max will crash
• if you do select an output, you can load the LFO page, but then changing the LFO rate will crash Max
• no other action is experiencing this trouble

When instantiating a [crow] object on Windows 10, Max will jump to a high CPU usage if there is no crow device attached.

The Max window repeatedly prints "serial * error reading from serial buffer".

It seems that banging the input of the serial object when there is no connected device hasn't different behaviour on mac vs windows. The high cpu usage is likely caused by the prints to the Max window, rather than an underlying issue in the serial port handling.

Maybe this is more of an ableton question but I just can't figure it out... is there any way to record the modulation produced by ins in a nondestructive way?

I have a chain of m4l lfos, modulating the remote ^^out v knobs of 3 outputs on crow. periodically crow will stop responding, and I have to unplug and plug back in the usb from crow, refresh the ^^command_center and choose crow again (which immediately causes the crow to start responding again).

Sometimes crow seems to stop responding without any manual changes, sometimes it seems to happen directly after I tweak a parameter on one of the outs (like bias) or once when I tried to create another midi track.

I'm on macOS 10.14.5, live 10.1.7, crow 1.0.2 and the latest master of this repo.

I'm not sure how I could give you log info, but if that would be helpful and you can tell me how to access it I can paste it here!