Nikolas K

Is there a way to completely remove a file and its buffer from polybuffer?

I know, you can clear a single buffer, and resize it to 0, so its a completely empty buffer.

But, if you open the polybuffer's window, the name of the sample still remains.

Is there a way to completely remove the buffer?

If I load 5 samples, and delete one, I would like only 4 buffers to remain in polybuffer, and if I append another one, that last should be the fifth.

Hi everyone,
Is there a way to completely remove a file and its buffer from polybuffer?
I know, you can clear a single buffer, and resize it to 0, so its a completely empty buffer.
But, if you open the polybuffer's window, the name of the sample still remains.

Is there a way to completely remove the buffer?
If I load 5 samples, and delete one, I would like only 4 buffers to remain in polybuffer, and if I append another one, that last should be the fifth. 

remove-file-from-polybuffer

I have the very same issue and I find it quite troubling the absence of a "remove" message... Polybuffer~ is great, but if I can't delete a single buffer, half of the usages I'm thinking of are off limits.

I know this is a feature request, and not a bug, but it seems like a basic thing to have...

But maybe there is a reason why it's not there?

I know this is a feature request, and not a bug, but it seems like a basic thing to have...
But maybe there is a reason why it's not there?

It's not possible because removing one item would mean to do cause the buffer names to change (remove item 3, would mean the buffer 4 comes 3, 5 becomes 4…). This is hugely problematic because the objects reading from a buffer would see the buffer disappear under their nose ;-)

It's not possible because removing one item would mean to do cause the buffer names to change (remove item 3, would mean the buffer 4 comes 3, 5 becomes 4…). This is hugely problematic because the objects reading from  a buffer would see the buffer disappear under their nose ;-)


Thanks Emmanuel, I understand the programming problem – but aren't there other ways to save both things?

For instance, I'd prefer to have all objects referencing buffer.4 to fall back to (say) buffer.3 when I delete buffer.4, (or to a default "private" empty buffer? Used throughout all Max for any "fall-out" like this?). Of course I have no idea of cycling'74's choices, and I'm not trying to suggest anything. I know that it is far from being trivial from the programmer's point of view. Only, polybuffer is a list of buffers, and deleting an element from a list seems like one of the two or three most basic things to have. :-)

Thanks Emmanuel, I understand the programming problem – but aren't there other ways to save both things?
For instance, I'd prefer to have all objects referencing buffer.4 to fall back to (say) buffer.3 when I delete buffer.4, (or to a default "private" empty buffer? Used throughout all Max for any "fall-out" like this?). Of course I have no idea of cycling'74's choices, and I'm not trying to suggest anything. I know that it is far from being trivial from the programmer's point of view. Only, polybuffer is a list of buffers, and deleting an element from a list seems like one of the two or three most basic things to have. :-)


remove file from polybuffer~