-
Notifications
You must be signed in to change notification settings - Fork 56
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
Installation is successful "Everything is okay", but songs are not downloaded, no folder is there. #98
Comments
I'm having the same issue and not finding a fix - lmk if there's anything you did to remedy this! |
Can you try the latest release? I guess that if it still doesn't work the problem could be AV blocking the DLL from being loaded. |
not sure if related but I upgraded from 2.7.1 with spicetify trough 2.7.2 to latest 2.7.3 with spicetify and soggfy installer upgraded spotify and spicetify automacially, soggfy doesn't appear to be loading into spotify. I got no download and option buttons on the top, I got no checkmarks next to the songs etc... |
+1 same |
same I tried it in a win 11 vm i turned off av all settings and then tries still not working |
I had this happen on a fresh windows install and installing the MSVC redist package solved it for me: https://aka.ms/vs/17/release/vc_redist.x86.exe (this is briefly mentioned in readme but perhaps not very clearly for this case) |
I tried that also but still did not work Also i know it will be a lot of work but can we expect a linux build?? |
Don't have plans to put in significant work on this project anymore, since i have not been using spotify very often. Sorry. You can check the FMHY wiki for other downloaders if you want. |
I've reinstalled it a few times, and it says that "Everything is Ok" and that it will be enabled on the next spotify launch, but there's no folder called Soggfy or similar, and after playing the song it doesn't give an option to see file location.
There is a Soggfy folder in appdata, but that only contains ffmpeg.exe file.
The text was updated successfully, but these errors were encountered: