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
Problem With EZAudioPlayFile Example IOS7 #15
Comments
Hello! Thanks for sending over the issue, I took a look at it and found the issue in the EZOutput (has to do with how I'm freeing those AudioBufferLists when the EZOutput is done with it to prevent memory leaks). I'm testing out the tweaks tonight so the changes should be on the master branch sometime tomorrow. |
Alright I tweaked the master branch with the changes to the EZOutput and the EZAudioPlayFileExample projects for iOS and OSX to prevent the crash due to the |
HI, I have tried various formats, and all result in this error. Kind Regards Josh |
Hey, |
Hey guys, sorry for the delayed response. I've figured out what the (bigger) issue was and I'm refactoring the EZOutput and EZAudioFile to better solve the underlying issue under the hood. I'll be pushing the fix live tomorrow night when I've done a little testing. Thanks for bearing with me! |
Hey @prisonerjohn and @littlebearuk, I updated the EZAudio source last night so this issue should be resolved. Please let me know when you get a chance to try out the EZAudioPlayFileExample! |
This should be working after the last refactor - please let me know if it's still an issue in a new ticket |
Hey Haris, Elie On Thu, Mar 6, 2014 at 12:28 AM, Syed Haris Ali notifications@github.comwrote:
|
I still experience the EXC_BAD_ACCESS with CrashIfClientProvidedBogusAudioBufferList. Any updates or hints on how to resolve this? |
Hi There,
This is a great library....
However when I run the example on a IPAD, it regularly crashes.
Often it shows: CrashIfClientProvidedBogusAudioBufferList
Any ideas would be great :)
Also, how would one reset the audio plot?
Keep up the good work :)
Josh
The text was updated successfully, but these errors were encountered: