You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gvf.mxo crashes max if trained with a number of gestures different from a previous training that has occurred since it was instantiated. Sending a clear message to the object before training again does not mitigate the issue.
Also reported in the MuBu repo on Ircam's GitLab (where I guess this is now being maintained) given that the more recent mubu.gvf version has a very similar issue: https://git.forum.ircam.fr/haddad/mubu/-/issues/102
Sorry for the late reply, I'm actually not supporting GVF anymore (or at least very rarely). The library is now supported as a MuBu object by members of the ISMM team at IRCAM https://forum.ircam.fr/projects/detail/mubu/. They actually made some changes to GVFlib.cpp in order to fix crashed in the mubu.gvf Max object. It may also fix your issue.
Actually, now that I think about it if you don't mind I'll keep the issue open in case anyone in the community wants to fix the bug in this non-mubu version.
gvf.mxo
crashes max if trained with a number of gestures different from a previous training that has occurred since it was instantiated. Sending a clear message to the object before training again does not mitigate the issue.Also reported in the MuBu repo on Ircam's GitLab (where I guess this is now being maintained) given that the more recent
mubu.gvf
version has a very similar issue: https://git.forum.ircam.fr/haddad/mubu/-/issues/102Here is a relevant excerpt from the crash dump:
The text was updated successfully, but these errors were encountered: