Forums > MaxMSP

hr objects (or similar) and Poly~

February 8, 2009 | 9:25 am

So I’d talked to JKC about this a few months back, and I’ve got some spare time again so I’m trying to figure out a workaround. Here’s the issue.

I’m making a patch that needs to provide sample-accurate playback of a buffer~, even at long file lengths. The hi-res objects allow for this (the milquetoast max play~ object, among others, causes something that sounds like sample-rate reduction on long files, due to using 32-bit floats internally. After a playback position number gets too big, it begins to lose accuracy).

This works great – except that now I want to reorganize my patch to use poly~ objects for all the heavy lifting. There’s an issue with any of the hr.objects that reference a buffer~ — if you put an hr.play~ into a poly, and load a file into the buffer it references, you won’t be able to load a new file into that buffer unless you restart max. Something isn’t releasing cleanly when run on a separate thread.

So, I’m at an impasse. I was mildly hopeful that index~ might help, but it does not. It’s just as bad, if not worse.

Anyone have any ideas?


Viewing 1 post (of 1 total)