So I’ve been trying to build test corpora with the
-comparison example and on top of other issues I’ve run in to I’m now having a thing where I can’t use my
polybuffer~-based workflow since all the labels in the dataset are the path/filename (as generated by the abstraction). Don’t get me wrong, that’s super handy to have, but at the same time, it was also super handy to have indices that I could use to feed a
play~ object being fed by a polybuffer~
. I can generate a parallel coll
or something to keep track of indices or hack at the-comparison` abstractions so that it stores indices-as-labels instead of paths-as-labels, but I can definitely see the usefulness of having the latter sometimes.
Even better would be to allow for arbitrary data to be stored in a dataset so any column can be a number, symbol, etc…
The main reason I’m after indices as not paths is that I want a fast(/easy) playback engine, so loading a concatenated version of audio files, or worse, loading each file as I need it, gets really clunky.