Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Max crash] Recreating referred and then reset fluid.dataset~ objects #370

Open
balintlaczko opened this issue Jul 29, 2023 · 0 comments
Open

Comments

@balintlaczko
Copy link
Contributor

The whole thing started out with me misguessing the function of the reset message to a fluid.dataset~. I was experimenting with the refermessage (to avoid excessive copying) but then I wanted a way "derefer" a dataset on the actual fluid.dataset~ object at hand. I guessed reset would just reset the object like a delete & undo would, but instead it seems to rename the dataset while keeping its contents.

While I was trying to "reset" the dataset objects with an actual delete & undo I discovered a consistent Max crash (upon undo/reopen). See attached patch: refer_bug.maxpat.zip

or

<pre><code>
----------begin_max5_patcher----------
1345.3oc0ZsraqaCDcs8Ww.gBTD.WCQJQI6rp.cUQWzMcWQQ.sEisBjHEjnx
idwse6cHo7qFaYEXZmz6BoHZZM7L7vYNy362FOJXg5UQS.bO7mvnQea7nQ1g
LCLp64QAk7WWVvarSKXoprTH0ASbelV7p1NNawcvuTyaVCz6gFQgXoF3xLHC
+Ss.VnzqgGKZyyllw07Fg9e.0hmvY0LE9i0BIrNWCsxL0zMu5hboXopUZe+Q
cCJaKUsZ7UZWMgciVw0KWmKW8PM9BcnIklLkMAhc2HIwSCwmRmFB+0dK8kpB
Us6KPLSHb6ExdyLOyBQb89SoA6VH4xMqChYruOdr4xjK0Qx23HI2CKKTMBPu
NuArXz5R00uAZETKTUneKWOENpKi9QcYLV56cYQQWpKi4MWVonoguR7NWVUc
9NG4gvkzMpaH8aUB2ROHX6R8HdBBYlwEvRlYcATyUJ83vK5nvi9UFdwwCGcD
uAuSQ3CuCpZ0PipT.YskkuAlHD.hYEx7EfjWJxftnF9gomjXwLywyidGOeOG
.cl2nuKZ0Zk7CtQtfKW06loa+KxdBjFu45Qgx7fsulZzopE0OHj7EEh8cWWs
SojPy+75wTFyf241cy348wiSu9GSIdGdgyMDzN306wzTxs.d9DbNZqCaTKNO
E1X2Dr4Uv4hu3.WDq23qLuANo3E7MdjrGBTlPFpISWo7bhDTvfM1i8n27Y8A
TJ4pKC3Gnd8zWDwkjHzRN6khRCu16hNoyE4MZ5h1G+n4PZe7QQ8fPK0lLLs2
fMD+kR7Dn8IjnB+rtNe0JQcCP7OmklZYqyi5kyRu1aqOgp2apxKJNNBomDgS
FT3Uxb6sXRunL5puchnTpxwJYHXMfJtNIFnePDiuiGJ4Hk30ghcmtNRXu5Bn
rqM3a+6bD1mH8RTux9lr6tIv8.vrKYSbbuPN8pKoOFkzaJZAWivZQs.dVTm+
XtnAEzy0aU0CqTZX4ZDhn.ekz0j.LWUieZA.wUmSDKdO9vAs.X+fZIew042U
SZDydqek9jzahR+Ss8GcG76+1DPpdA9UHSI+QM7BWpcMs.yDAb4akpZwDrnO
XIunvvSpEnBkI.57f1JjLrk.8h.0tfy0Rcx2QX1vhbemFMFEEVyariapV7nj
H1GtoHQ1tgPCS1iDkdJ+d7WbRDi3TyzcqeRD6SkDQuqirz0F.kT.ujiAH3c6
5VBh4SsAWdyOcFHZlsGXDWqvNSuAHzu58FHg3fA87cGfD8otcS5RY3RBz0sm
lIuea2zATtDmDRMbefD3sZ0JgTTy0XfAy77SFjnXlSCQ3drgSlAg7UmM3jBQ
HCfM741pntbAduwmcg+557YRuUlSu5ccvEdyvgef+vdwz7ZaVbQ.5PLIp2Zz
m8+uVY2woYIomuW1I2lhz296as2NquKuyUDaBwIJg0KQN9ZWgygv16Ux5Xvc
XcVXucl3rP09srYE9O+pmVKaF+P72nZqWtYs1EXD1Y6LAp6Tx04Xz5cyIwMm
i5gGpclM.6P7fcLMF+rFxTx3kaIxsxRICvPwGLGUcln9zGK7ogIG2vgWjgY2
Leqog02HKQF913kYnajcnCI1AyGGps9exYrTj2rzYoCLeYI54rD0GVZPT7He
XogP8Hy7gknCASdgQbqN1Z9QWNOjntSBWlktQ4hICIo+FXeYVZHGa8ACmLny
R9vPC4nz6OI4zCxqpdVT2zMYqMPkuO49+4zrI1GyktGscPDqc647My2MBuFU
tpQYqs010UvqINk2AkJLGurMuSeAhNzjVU0lRCZp3NfXEeO96i+W.dgPPMB
-----------end_max5_patcher-----------
</code></pre>

It is probably an edge-case, but since it is consistent, I thought I should report it.

I noticed issue #249 and @jamesb93 helped me understood how reset is not what I thought it would be. We have also discussed the idea of having refer without arguments to do the dereferencing (that feels like the Maxish way). Right now I can achieve the dereferencing safely if I provide an empty dataset "dedicated" to this purpose. This is still much less overhead (and horror) than my current method of patch-scripting the fluid.dataset~ object with the target name as a way of "referring caveman-style". :))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant