d2ed22d229
More precisely, the MediaLibrary matches up files based on their file hash. If it finds a files that matches an already known entry it doesn't create a new entry, only updates the file path to the found file in the existing entry. This is useful if files get re-organized or if an existing database is loaded at an entirely new library root that contains mostly the same files (relocating the library to another computer for example). This method preserves information added to the database that was not originally present in the ID3 tags in the media files (custom tags, name corrections, etc).
What Do I Want To Listen To
A simple, tag-based music library manager.
This project is born out of a frustration I had managing my music library. I have found playlists, genres, and other ways of organizing my music too restrictive and cumbersome to keep up with. Here are the main features I want out of music player, in order of priority:
- Web-based interface.
- Mobile interface (could implement the Subsonic API on the back-end to be able to use pre-made mobile apps)
- Song tagging.
- Playlists.
- Read meta-data from ID3.
- Transcoding on the fly.
- Read songs from Amazon S3.
- Stream from Amazon Cloudfront.
- Bookmarks (temporary song tag marking location in a playlist/album)
I have not found a music manager that gives me all of the above, so I'm going to write my own.