Coll auto save in patch fails
I try to save coll data in the patch by setting the embed flag in the inspector. When I close the patch, coll data is not saved and max doesn’t ask to save the patch before closing. I tried sending a [flag 1 0] message with a closebang, but this doesn’t work either. How is the flag different from the embed? When I send the [flag 1 0] message, the embed flag gets set..
im not sure , if u send [embed 1] message it will embed [coll]s data it into your patcher . but u need to save your patcher if u want to include it inside
Yes, it has saved a data set once and it never wants to update the changed data. Still puzzled by [flag 1 0] vs [embed 1].
Any chance that you have a saved file on disk that the coll is reading? Try adding a 1 after the name of the coll so that it will not try to read from disk.
That’s already what I do: [coll name 1] Documentation isn’t very extensive on these options have to say.
it might be not your problem but ,i had some issues when ive tried to store links that has been bad formated … ive used "" instead of "/" … in my case [coll] did not readed ,stored or keept anything . just to let you know that it also could be the case if you are using [coll] for such data .
Tried quite a few things, even stuff like name space conflicts and the like, but can’t get changed coll data to save in the patch. I now reverted to saving to and loading from file with a closebang and loadbang construct. At least it works now, but might be a bug.
can you see the data in my coll ? could do the same and post ?
----------begin_max5_patcher---------- 364.3ocoSsraBCCD7bPh+AKelhvAnB5s1eCDJxIdK3VGaT7FJTT+2qsSbZ3k Tq5gXmLyrqWO6lSCGjPyMG.Kk7DYEII4jCIIf4QRh.IzR9gBE2FDRKAqkuAn iZIQ3.FHXDVGnttzTiJ.CwvhvMX3wcPyYRoj0QtWMZzJ+LvvlLdRDWJBY2j+ 1CSO6.j5X9S6mCMuLjC5yURth7hQI5hZGGK1J0axpfBroDR8GEgMyuNMc7b2 6ONdBYcHhuFNvu61F8q8GM7gqVu1dJLJEwQdGOZ188nQ8d9S9U5ha6Wr+seM coec9xfesv6WwP7WyLAG4sdTzj7L0Zr+wmPi5VET9iVG06vwyz5f1yU0slBq sA0zihe36SskgkuGDYNSvU3YbDqj40Xyn9YEETlCACi0khK57MWMpRpu5Okf 83ItXdvZpqJhsu3fKomII.KJ0bTZz8T4aW8UsUJDPPPWysTJ1YjZrsRtZL0C 319FPDYz+B -----------end_max5_patcher-----------
you should try to prove it on a fresh patch
PS: it might also be that you did not NAMED your coll . im guessing
Here’s my coll with data. Not sure this is useful as creating a new coll in a new patch, copies from memory the data and it’s not a problem with data in memory, but saving it in the patch.
----------begin_max5_patcher---------- 459.3ocqU98SCBCDG+Y3uhl9LZ35Xvlu4eGFCoiUUlrxBTlSM9+t2UJ5LoKo K3C.i6Ge36c8xtOii3aZOo54r6XOvhh9LNJxZhLD4dOhuWdppQ1aCiqUu0tY GOYzkQcxXMW01zvdRVoJ6MRihASQ7Tq1zW+ghhBD2l5LqG1WqaTFKT3WisCl IqYNqGjlpWp0OW1opLiRcQZJRhA4KoGqKn6BzD6QWNiXLuePMl.mmb10OgUu 0Jdrft4OBVK2aSjeeWsrYxCUikakFoq835OjiAsUYBmli3Sg8fMveBE87p5c xgqQPVNJaFb5bAjvxwhAqDm6uhStDBvKBgHgsTDHBgeDYXuEBUFK7xXUNwHT cj4kAIAHMTcrzeGESOacfHx82NRulRoveofouNOPDq7hf5CABX8bA.oyl.7O LZA9mOQ1gelB9mOWbUymP1EExRHTFWX.8ZlL.+SnHZVdQnLJl8Y6p+iy1YOj Jl8Pp.lMAwrI3e9ji6GokU3xW5gtsieFM2OQriql5kGUaKw8X3JxRowzUuYv LtX+7EUp8aT1UdfK83o6DRjEWd3vQUWecq1lKkHJgczW282ijvFe0194cpi0 SwWDSz9J9afszzl+ -----------end_max5_patcher-----------
That works fine. Perhaps it has something to do with bpatchers?
So what do bpatchers have to do with it? If you’re saying that the coll is in a bpatcher, and it doesn’t get saved when the top level patch gets saved, that is the way things work. You are not saving the bpatcher when you save the top level patcher, so the contents of the coll doesn’t get saved.
What I do in this case, is have a "Vault" subpatcher at the top level (not an abstraction) that holds all my colls, tables, etc. I use arguments to abstractions/bpatchers to get them to use the colls in the "Vault."
Forums > MaxMSP