Right, that would be easy enough. I noticed that fluid_track_t isn't part of the public API -- is it excluded intentionally, or would it be OK to expose that?
On Fri, Oct 14, 2011 at 1:49 AM, Matt Giuca <matt.gi...@gmail.com> wrote: > It looks like there is no way to do that. The tracks contain events, but the > events don't link back to the tracks. That could easily be added, but at a > cost of, I suppose, 4 bytes per event. > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev > > _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
