You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the full API with a reused buffer which is much larger than the expected number of samples.
After I run:
resampler.full(inputSamples,resampleBuffer);
How do I know how much data is in the resampleBuffer. I looked at the source briefly and it doesn't appear to slice the Float32Array or return the number of samples in any other way.
Is there a way to deal with this, or does the library need to be updated to support this use case?
The text was updated successfully, but these errors were encountered:
Hey, thanks for submitting this issue. After reviewing the implementation, I think you're correct in identifying that I didn't provide what you would need to properly read dataOut. I imagine the best way to do this would be to add a third argument, something like outLength: { length: number } = { length: 0 } that we could reference following a call to full to determine how much to slice. I wouldn't want to break the existing API by change the return val.
I don't have time in the nearish future to implement this, but if you're able and have the time, I think it'd be great to add this.
Summary
I'm using the full API with a reused buffer which is much larger than the expected number of samples.
After I run:
How do I know how much data is in the resampleBuffer. I looked at the source briefly and it doesn't appear to slice the Float32Array or return the number of samples in any other way.
Is there a way to deal with this, or does the library need to be updated to support this use case?
The text was updated successfully, but these errors were encountered: