Ringbuffer (String) mixes up its slices

also behaves differently compared to its Spreads counterpart when Framecount Pin is set to 0. see patch

RingbufferBug.v4p (8.4 kB)

Acting strange also

hmm think it’s normal
because if you have 0 frames means you don’t have any value…

It think when it´s set to 0 frames the node should output NIL not an empty string.