-
Notifications
You must be signed in to change notification settings - Fork 4
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
General performance issues #16
Comments
I know that the first launch can be quite long, do you have a lot of songs on your device? It could be a good thing to select folders to use before fetching songs for the first time. I will implement that when I can. |
Currently, 844 songs, all of them on the SD card. |
Okay, I see. |
More than 20000 songs on sdcard, first launch never completes |
I'm currently working on ways to improve the logic of the data fetching. It's one of the things where the app needs a rework. I will let you know when a faster system is made. |
Same here, even with less than a thousand songs, indexing them takes a very long time when other players with the same music collection do it a whole lot faster. The transition between songs isn't yet perfectly smooth, but seems to be a lot smoother than what it used to be. |
App performance is heavily improved in the latest version of the app (v0.9.0). It includes primarily song fetching and cover management. However, I don't know if it can handle well more than 20000 songs! Let me know if it works correctly in your case @gargamel17 |
Hello, yes it works fine, music loaded in just a few seconds 🙂
Le 23 octobre 2024 20:27:37 UTC, enteraname74 ***@***.***> a écrit :
…App performance is heavily improved in the latest version of the app (v0.9.0). It includes primarily song fetching and cover management.
For example, on the v0.8.1, 890 took 3 minutes and 30 seconds to load. Now it takes 2 seconds in the v0.9.0.
I tested it on several Android versions and it should work properly.
However, I don't know if it can handle well more than 20000 songs! Let me know if it works correctly in your case @gargamel17
--
Reply to this email directly or view it on GitHub:
#16 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
I can indeed confirm initial music indexing is a lot faster. Not instant, nor "backgrounded". It can maybe go faster, but speed doesn't looks shocking for now, an improvement could be to let the user use the application while indexing is ongoing. On the other hand, everything related to GUI loading, transitions and globally every GUI drawing/rendering still have very bad performances, it's not fluid, nor synchronized: when we move onto the next song for example, things change little by little like you could have cover changing and then backgrounds colors between 0.5 and 2/3s later. |
I don't have such bad performances, so it will be difficult to improve the system, but I always try to improve what's already existing, so I will see if I can better optimize it 👍 |
Application is still quite recent so those things can happen, but it does have quite some performance issues.
First on the first launch for the global indexing of all of your songs, but even after that for example for the dynamic theming, which is causing some performance problems, especially when switching to a song with no cover.
Dunno what I can add there to help on that topic.
Device details:
Xperia XZ running Android Oreo (8.0) on stock ROM.
EDIT: To be more precise, first song indexing took at least 10 minutes I think, went quite slowly, and only offering 6 things to read during that time. You can't even set the folders first.
The text was updated successfully, but these errors were encountered: