-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
frame_period bug #14
Comments
Hi, thanks for report this. Does this happen with the original REAPER? https://github.com/google/REAPER |
Sorry I have not try the original REAPER |
Then, could you try to reproduce the issue with that? I would like to isolate what the problem is. |
I have not too much time to check it, I have spent hours to find the error today. If you hope me to check this, it may be several days later |
I encountered this same problem. I have tried it with the original REAPER code using -e 0.0125 to indicate the frame interval and can say that this error is not reproduced in the binary version of REAPER. |
Then it may be sure that, something may be wrong when wrapping the c++ code! |
when set the frame period to 0.0125, the pyreaper may cause memory free() error. This is random in different wavs. But it is right with the default frame period.
something may be wrong because of the mismatch between the wave length and frame period
The text was updated successfully, but these errors were encountered: