We had an offline imessage design session about this, but basically, this allows anyone using AMY to add patches at runtime by giving u1024,AMY_PATCH_STRING where 1024 is a patch number from 1024-1055. This message must be the only thing in the string sent over. amy.py will parse it and send it right away, and amy.c will treat the rest of the message as a patch, not further messages.
We divine the number of oscs used for the patch at store_patch time. If you store a new patch over an old one, that old memory is freed and re-allocated. We rely on malloc for all of this.
Also recall you can "record" patches in amy.py, so the whole loop is:
We had an offline imessage design session about this, but basically, this allows anyone using AMY to add patches at runtime by giving
u1024,AMY_PATCH_STRING
where 1024 is a patch number from 1024-1055. This message must be the only thing in the string sent over.amy.py
will parse it and send it right away, andamy.c
will treat the rest of the message as a patch, not further messages.So you can do:
We divine the number of oscs used for the patch at store_patch time. If you store a new patch over an old one, that old memory is freed and re-allocated. We rely on
malloc
for all of this.Also recall you can "record" patches in
amy.py
, so the whole loop is: