Marcin Pączkowski
Marcin Pączkowski
> IMO the status quo is fine - or what would be your motivation? Limiting unnecessary CI runs. E.g. when you make a PR from the fork, the CI runs...
@capital-G is this PR still valid?
> * What should happen if e.g. offset=-2 with 4 channels? Should we mask the non-existing channels with silence or post an error? I vote for unobstructed reading of random...
> However, since it already addresses the overhead of spawning multiple BufRd UGens for control-rate access, @prko, FluCoMa does _not_ address the overhead, but this ugen does. If this is...
@elgiano this is great! I wonder about the name. One association I have with "...In" is the it could be an "input" to a buffer... which this is not. (And...
> > There is still the case where one writes `b.numFrames`, making a buffer-specific synthDef, but that's an edge case? > > Can't save everyone all the time. Per above,...
I like BufRdArray (or BufRdAsArray). I don't feel it's very "elegant", but I think it's more accurate/descriptive than others.
> Each Buffer frame becomes a channel - So how about Frames2Channels or BufferFrames ? Frames2Channels is nice, but I'd like to have "Buf" in the name (like with Playbuf,...
TL;DR I can't decide 🫣 My internal desire is to support older OSs as much as we can, but with limited dev resources I don't want us to bend over...
We now have a PR with proposed API change: #5713. Also #5610, while not strictly breaking API, might also be related. I think it would be good to re-start discussion...