As outlined in this thread on the discourse it seems that @startframe (and presumably @numframes) is only being applied to the @source buffer and not the @weights buffer, leading to errors being thrown even when both buffers satisfy all the conditions of fluid.bufstats~:
a single-channel
exactly the same amount of frames as source
all values must be positive (anything lower than 0 will be rejected)
This creates a situation where the @weights buffer needs to be manually trimmed based on the @startframe / @numframes attributes of fluid.bufstats~.
Expected behavior:
@startframe / @numframes truncating is applied to both @source and @weights buffers (as well as the right inlet (the "weights inlet").
As outlined in this thread on the discourse it seems that
@startframe(and presumably@numframes) is only being applied to the@sourcebuffer and not the@weightsbuffer, leading to errors being thrown even when both buffers satisfy all the conditions offluid.bufstats~:This creates a situation where the
@weightsbuffer needs to be manually trimmed based on the@startframe/@numframesattributes offluid.bufstats~.Expected behavior:
@startframe/@numframestruncating is applied to both@sourceand@weightsbuffers (as well as the right inlet (the "weights inlet").