-
Notifications
You must be signed in to change notification settings - Fork 104
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
Error code 12 (Cannot allocate memory) #3
Comments
same problem ! :/ what can I solve it? |
have the same problem over here |
same thing here, anyone manged to fix this? EDIT: Ah ok, just saw there's a PR that could fix it. |
I didn't have enough ram. You could either get more ram or modify the code
so the arrays aren't stored in ram
…On Sun, Mar 5, 2023 at 9:54 AM illtellyoulater ***@***.***> wrote:
same thing here, anyone manged to fix this?
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6UVWBHLMTBVZOLTWIMLNLW2SSKJANCNFSM4J3CHSGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I could make it work using this updated fork which includes this and other fixes, in addition to a couple more features: https://github.com/zlattala/deep-music-visualizer |
Thanks @illtellyoulater, it works fine for me, except is uses 0% of my GPU. How can I make it run on GPU instead of CPU? |
If you are using the code from the forked repository then you should open an issue about that on the forked repository. That said, I am not observing the issue you are reporting, but usually when you see the CPU being used in place of the GPU it means you installed a wrong version of torch. To make sure everything works as expected please make sure to follow the forked repository package requirements and installing instructions. |
You're right, but I don't think this issue is related to the new fork. With conda, I was able to use my GPU, so yes, it was something with the version of python/torch/env. |
python3 visualize.py --song ooo002.mp3 --resolution 512
VPS:
The text was updated successfully, but these errors were encountered: