if statement and read/writeagain coll in saving clock
Been working on this clock for a bit with help from others (Broc has been super helpful so far!), I feel like I’m making baby steps to having it done. It’s basically a clock that saves how long you’ve been working on a project in Ableton as you work. Problems encountered were that having the clock just simply tick into a live.numbox or any other live.* object would write to the undo history, which wasnt good at all. So there’s a coll in it’s place now and I’ve been reading about writeagain and readgain messages going into coll, so my current attempt was to the try have a load bang that would trigger a live.numbox to send its output into an if statement which depending on whether it was 0 or anything other than 0 (if its the first time you dropped it into your session, or if you’re opening a new session) would either immediately ask you to name the file and save it somewhere, or it would send a readagain to read what it saved from the session before.
I guess before anything else, can readagain and writeagain work over the closing of a session in live? Or does closing the session basically make them just send normal read and write commands when you re-open the session? If it’s the latter, I’ll have to think of something else entirely I’m afraid!
----------begin_max5_patcher---------- 1377.3oc6Z10ihaCEF9ZleEVndWYG4OyGUUUcW0apzdUusZ0n.wv3pPBJwvt SWs82disSBILfwYmPXXZuf.1wIb7iOG62iS95cSlNO6K7hofeB7mfIS95cSl nqRUwjpxSltN5KKRhJzMaZJ+yYy+qoyLmRx+hTWsDfpqKc65rsxDtTeAnpZE w51UdsuC2zzMQxEOJRW8PNegzXE3ff68Yy.XRv8vxuvpinxeC9T0EYt4xm1v MWwTQZ40Ve1kYoxzn05yM884hnDvGxRhm15zEh+VeZDr7d2XyhzFSVU22t6N 0gYuLrDyShdp7OBBcmNPWnCjp3hG57zYdT5pAEO3gCO+XO7ZPgV4hu1awWCD B9d1X6zfGZmFVO7YHVPCxDHQHZzv7tQ7XVyKJhVweFb9btPxcGLTajgocZnL crDCpIimMx7Z0iQrD7CBzu.AxG4ofBtDjyihiVEIRA7jBttpdRNrsvMBSEgQ BzLCCcXZnq9LzIhc76KuKpVUcO2Ek2XHG4zcYD9HLBd9ojHPcDGwD2wrhnYf oKSxhZMwzln7RCTxyefmFMOg2dvpKQpprHZGO9gHoLWLeqju+WEUnohMpNex Vd1x5pqqu8+YssUMFz4bEOlkKsPuNMNIKckqscapPVHexzWglyqGpq+5Jrzi mkwYRHSOzh8dCrzSejwg7sQEyxMAn2.h3J8Kyyzh3.+ZzBYo6aenTv4oDgn4 ChbaqlSMD5LVXVvBMzfEz+4BorsnKinWskZhltUhorpiSqPwY5XykgDPzJRL ATd2vZ4JE.DqixcEK1lfAC0XA4qABicElfY.mHdQRVAuWrAYSgFEqgS0NMT4 yLtvANfvIKI43bgdDtfrN8andd2.8WrvyO8qR4ZymA04oir1RKuzHsnokudN OdutwgTu3lb9FdZbelLmXkwlrCn5PRVvMPBTJI67bmSNBYK0aZfIeHTXqTuO 6ZYy5YD3wxdBdgozhr0q46EB03+7yfOrUjDCdJaaNHZarHCvWtrDHfG44MKO lHR4Kx1lJaC0tnF9bTaizgZP6o2hiPS55gs37UxW5TT5Ol5ZeF2nFXY9p4l9 J7dxL0Ap5X4ATqN5w1+GnQCEx7k+ybBOAb.+tLJQrnswWN4aV94MhwFmezcb 58hwoQd5aXZ1CmS5P4bR9eey2gwCjuoI4f2hv7236DK3fc7boXQo0mHVKZZ0 ih3Xd5Aacncja6YsXBy8qh1cAlWqUSdudYVYF3ihcbmc27e4daFwMs2BLT3n 4tgFKvtLOac+P6vsHiVNi2sKYOUVFIaWUhv+wYU1XqhrasfLygMWrPrJUEs1 7qWoaQhhRhT2gD5rPh75iQ56qNgfCd+LzcBU8cAWQYhEKpsxp8EBruiDyKjh zHoHKsUaTOAqVMZ+JE0lWrnPk4T7o2rhA0bdUYM3wCNLGLG0d1X0bVKh2jUl mbQ8ClR6NS7qd71A5MHUUZ+ezf0ATOn8AuGf77T1L02reTziUBBa06zktD8N rKNuzQyc4fv1SXO3wydFB7b3fO0WOjZ1c1ZWARvEY.Fibw8Mbz.J1kAXLZzr mC55W8ESPtL+s5ATOV1iuK1iWOm.mB0a8tQ.GERaJcAh.Nv3NQOnmwv01rQX E0yrYFcKYzxSCYldG5xz6bZA1wS9Ah5p+Bxh8zIGF3rVGZSwCGSpHsmdYTZo OF9HEMuKBTTPyalvkXTwIJvNCENd+CaRBmgzpezktD8.xPH6Y.sG7EPFFine DfTpIIIy60V2RDe+NhL8uLzFMDyQ8cE0TKvzDPvLOOktkFoYxTL.eNFLdR+P tnTg85xbPin83hNtQ0ZPNXMnuCqA7o691c+qs9BnM -----------end_max5_patcher-----------
It’s unlikely that readagain/writeagain would work across sessions.
So you probably need to store the filename in your patch and use it for read/write operations.
The filename could for example be stored in [textedit] and typed in from the user.
But finding an elegant solution seems tricky. Good luck!
Sorry about the delay getting back to you. Sad to hear that the readagain/writeagain idea wont work. Almost wondering if having a C/C++ external that deals with either the whole saving process or just the naming process might be the best bet. Will have to read up on that. Thanks for all the help again!!
Hey, I suggest looking into [pattr]. Activate parameter_enable attribute and it will save clock state together with your live set ;>
[pattr] can be used to save the clock state but it writes the clock values to the undo history.
As mentioned in the original post, this behavior is not wanted.
Forums > MaxMSP