Hello,
Is there any incompatibility between poly~ and mubu.concat~?
I am trying to switch from one buffer to another inside my poly~ but it seems some voices get stuck to older buffers. I have checked that my voices do receive the right messages to switch.
What’s wrong?
Hi Roald, mubu.concat~ should workk fine in poly~. Can you post a simplified test patch that shows that problem?
Cheers…
…Diemo
Hi Diemo, I cannot send to you a simplified patcher. However I have sent to Riccardo a .zip file with all my patchers and sounds required to solve another issue two days ago and I would send the same to you to solve the present issue. Maybe you can get it from him? Otherwise I’ll send it to you over WeTransfer if it’s ok for you.
I know that is an old thread, but did you find a solution?
I have the same problem: mubu.concat inside poly~ doesn’t seem to update when I change the source buffer/mubu.
As soon as I “open” the buffer, it works just fine.
Hi Jason, we’re not sure, it was hard to tell so far…
If you have a reasonably simple Max project that reliably reproduces the problem, that would help a lot. Cheers!
Hi Diemo,
So I tried to recreate the problem and found out that it is maybe not a problem of mubu.concat~ but rather a problem of mubu with polybuffers. In the example I will post below mubu.process will only process the first buffer in the polybuffer until I “open” (e.g. by double clicking) the mubu once. Then it will process the whole polybuffer. The same issue appears when I save the content of the processed mubu with “writeall” and then “readall”. If I try to play e.g. bufferindex 2 markerindex 1 it won’t play, until I, again, open the mubu. Then it will work without a problem.
Could you think of any sollution? Is there maybe an attribute or message I could use?
PS: Thanks for responding so quickly and also thanks for your work on mubu and pipo. These are truely genius and masterfully written objects.
Here is a quick example patch:
----------begin_max5_patcher----------
1371.3oc2XsziaaCD9rWf8+.gtTfBGCQIY4GGJ1hliEsEE4RQRvBJIZalHQJ
PQsd2Fj82dGRJYK6UVQds7dnGroF9Py7wuY3LTe61aF4DIdjV3fVh9HZznuA
8LxzmtmQ0cLxIi7XbJovLQGNcqH5KNiqFSQeTY5OqLpbRrfGSTOi7PefVnP2
kmRdB4htKiH+JUVfpauiTlvDnOZZ9rVTITR150TIBu6cyKyX7TpxnXbidEkp
5t8q611m5obpEONEr0bRpy3lO4f9b87YIFyFvx6ltSi4DU7FFe88RZrx9d77
7m3NF4uvzDD3pa77l3t+UUPdflbO7lfEcOQA.IpTY2WGseazXh4kpBEQYrQ2
w0CHoEjr7TpY6fwgIYF2N72u8FyCUsPy3dSVwhrLJW8R15ODaQhbJGo1PQFp
C8OhRTLgiJnTnWhBwTnDVB+mTnboHlVTfDvrknnxUqzjHLI65Wwj.YK3zIn+
tjua1j0DFG8teAwAkommcgLdB8QvCYKKMEsUH+5jclWJiSiEkbiMFdNtAtsP
qdgcwq9KrL4hY5F7Tiz7EZdc32t+vFVAJQPKfcyINWLvB5iCqWntYl4eO2qH
tJ1HJSSNhJe0XysKrYYoJngc8tlX6upbiqiPtXng86BZAAV+vEVnM8ZBseUY
iGoqYbNXFKQuWniyO3Dg1iJ8t3cgNIX7brA+X+FQk9AWmsg+TCWBZkHMgJuX
5cdOXWyYMVHdgbaF3ZRVSeInZdHKdbUF2Jw1wnW6XDexLqsmE0qGAtSMQr3v
FIQe06.PNVkfeVzFduEJIYTEUdOkShROHc7KwaDgu9DX1uam48jtWP8+WCRO
FpcPRRSutDLtSvZw4BCCGLa.H3SUooBEghNKd2qapcbWTLdwOlhqSKcEAcBI
94yhca8r248nvgo1yd8mdEQyO+LxcxzAxasp791Yuvdf3.OqS6+WNUB2Y8g3
EMJz35drzAE7+VlKB60mJjGxrQcds35aDYtTb8kdKRYwzkqVoVVTlsrHljRW
FuQjitiCdA6upb8hc0ORyIIPoCtffY8SJX+KUWIbPcG52f2zvZQtPlgxEag6
scGnqIYhDZS4sT15MJX+AttWoLHbNrPsoLgwAZAgaHR.VysVFHB83GHevDVU
xiQoh00xQjBpYXMFsls2zZQyRqe1pV6yTxdgBURB8AsHiuRfVWxPexgwg3kU
j3caXiQ5OlPDTuZRgt.HSPUrHs.8akTzuShnon2WJIJlf+Im1Kx0uaeyUBtR
C.imoN.pUe1flSWSo1RukLx9zzuzcdr8GSWu5Ad252hFmm7r8Y8HneQ0EmlY
xOOc1EF1Ca8O+5Np6E.eUpfnZOXtSf4MCay.6Zu2vr5bWWoXYSL7.g41gaPO
pxBa4yvfW+GihlEQSN7yPA3jJgToqXozCL88egpcCseUZEBwhCzWr5j4RjTR
RW2TafxbziB5sk3F5eEyZjKRexl774y2gyqySW5nrgdbWFqe2B+gvu6TNK12
o4D4i+1zFCSOvQapEhRYbMJq9jtnFFWBrGx3ly7aLIcwgnNoudqOu9nuiLpL
VRt.NnuBjPAYSgitlaiogKSTKMHFH9brvAPe98h.Ft8+9ouECmBw8QgACl9p
M8t0m+vpO7OReGuKbjKMbiJvIdl4ljXuvZggw.C6yFxrNsupnr.nFBnwat6N
o8KQH0ob1cd0agQquldyYsyD7daMAbKl.dHLgfdYByZ0YtJ6.IO+AnZ+pkX0
Eja8KBiUNerUlwsx1LkPMDOvpWhs.FGhDxzofbVkRaA5OFVU.li9pRRtsxFM
r0nUqZS5acA8E4U0iaRye6MvD9Ov7O1LJ
-----------end_max5_patcher-----------
Ok, I found a solution: I now use an imubu instead of a mubu. The issue doesn’t appear that way. Is it intended to be like this or is it a bug?