-
Notifications
You must be signed in to change notification settings - Fork 15
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
fix: A lot of RAM is needed #26
Comments
Hi @synchronisator, you are right. The sounds are loaded into memory to make them accessible as fast as possible, useful for game sounds. Actually SoLoud::Wav.load() function is used for which the doc states: I put this on my TODO list |
About the huge memory allocated: the audio data in an mp3 file is compressed, while into the allocated memory goes the uncompressed audio data. Since a second of audio takes about 350KB of data, every minute will take about 20 MB of uncompressed data. |
Thanks for your answer. I make a practicing app for choir singers with multiple voices. So its essential that the files are played in perfect sync. So i think the Stream is not an option, but i will try. |
Hi @synchronisator, I have made some modifications that point to resolve this specific issue. I will be very grateful if you will find some time to try it! and add this:
Thank you! |
Wow, thanks. I will, try. maybe today or in the next few days. |
I made a quick test and the backward seek is not working correct. |
You are right, thank you very much. |
Hi @synchronisator, I have updated the PR, but there are some problems. I explained this in the PR comment here. What do you think about that? |
I think this is fixed with #30, right? Should we close this? |
Hi, |
Description
I load a bunch of audiofiles.
Round about 35 mp3 files with round about 5MB per file a complete size of 180mb.
On Linux i can see, that the RAM usage goes ob from ~450MB to 3,1GB
On Android this leads to a shutdown of the app by the system
Steps To Reproduce
Load a lot of big files.
Expected Behavior
The RAM usage should not go up this high.
The text was updated successfully, but these errors were encountered: