Feature request: export library to a file

aleksey-saenko / MusicRecognizer

An Android application for music recognition that uses AudD and ACRCloud services to perform song identification.

GNU General Public License v3.0

514 stars 14 forks source link

Feature request: export library to a file #44

Open Freeedim opened 10 months ago

Freeedim commented 10 months ago

Hi there!

Great app, thank you!

I would love to be able to export the library, in a CSV file or something alike.

Use cases :

changing phone
mere backup, useful if phone gets broken, lost or stolen
building a wish list
...

Personally, I hated Shazam the day I changed my phone and wanted to keep the 200+ songs I had shazamed (I don't want to have an account). Fortunately, I had rooted the phone and could eventually find the database and copy the file. Now I don't want to root my new phone anymore for security reasons, and I have just discover Audible which is as good as Shazam (except for musics from TV shows or films), but would still love to be able to retrieve my library at will

Thanks for your consideration

ihatemakinganaccount commented 7 months ago

alexxtasi commented 4 months ago

Totally agree !! Now that I am preparing to move to a new phone, I miss this feature. It would be very convenient.

pdimu commented 3 months ago

@aleksey-saenko can you bring your attention to this? It would be really appreciated if it goes real

aleksey-saenko commented 3 months ago

I understand the importance and convenience of this feature. But I considered this feature in a broader context: export + import (backup). I've tried to implement a backup feature before, and there is even a working version. Although it's easy to implement this functionality for one version at a moment, maintaining it between versions is challenging. I periodically change the data format as the program evolves (something gets added/dropped/converted), and in addition to database migrations, I now have to consider this for backups as well. This is a high cost. But I will try to find a more elegant solution when I have some free time. Exporting the database in its current form to a file is not difficult. However, a comprehensive solution in the form of (auto)backup would probably be more desirable.

woiwoiwoiwoi commented 2 months ago

Maybe you could add your current solution as alpha/beta with a notice that it only works for the current version? The name of the backup file could include the app version to make life easier for users.

I think if it's clearly marked as alpha/beta, people will appreciate it for what it is. Me personally, I would be super grateful for this.

aleksey-saenko commented 1 month ago

Added as an experimental feature in v1.6.0. Known issues:

Saved audio recordings (scheduled recognitions) are restored with errors when transferring data between users with different IDs. This is relevant for those who transfer data between different users (Android multi-user mode) or between regular user and private space on Android 15.
Data is exported without any encryption. The most critical concern is potentially exposing API keys (if they are valuable to you); in this case, it's better to store a backup in a location that is not publicly accessible or export only the database. I may add encryption in the future.

Otherwise, it seems to work.