mirror-github-bspeice/Melodia
1
0
Fork 0
mirror of https://github.com/bspeice/Melodia synced 2024-12-04 13:58:18 -05:00
Code Issues Releases Wiki Activity

Slight README update

Browse Source
This commit is contained in:
Bradlee Speice 2013-01-19 11:19:20 -05:00
parent bcfbd7bc60
commit ff95b1072e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -22,7 +22,7 @@ The name comes from the Portugese for "melody." Plus, I just needed a catchy nam
Why do this?
------------
Melodia was created for a number of different reasons. I needed a project to keep myself busy, and wanted to learn Django. Beyond that, I've maintained a personal music collection on a hard drive, and have had a sufficiently hard time trying to keep it organized, keep it centralized, ensure tags were all filled out, etc. Additionally, trying to create subsets of that archive (I.e. the songs that I wanted to put on my phone) has been challenging to say the least.
Melodia was created for a number of different reasons. I needed a project to keep myself busy, and wanted to learn Django. Beyond that, I've maintained a personal music collection on a hard drive, and have had a sufficiently hard time trying to keep it organized, keep it centralized, ensure tags were all filled out, etc. Plus, that was only one archive. What if I wanted to keep another archive of music in addition?
On this note then, I wanted to create a music system that could be used in place of a standard local program. This way, I can have one copy of my music across the network, and use it everywhere else.
@ -32,8 +32,8 @@ Good question. Besides just wanting to learn Django, there are some good reasons
* Music archiving isn't very good. I haven't found software that I can use to manage the archive.
* Making one library available to multiple network locations is problematic. You can use something like IceCast with XMMS2, but that lets only one person control the song choice. I needed something a decent bit more flexible.
* Managing multiple archives is problematic. I need to create a subset of songs to play on a different device that may not have as much space, etc.
* Create a web-enabled music player is also important. XMMS2 only allows you to work through IceCast, and enabling something like a socket to XMMS2 concerns me. Just doesn't seem very secure.
* Managing multiple archives is problematic, especially when you want to keep backups.
* Creating a web-enabled music player is also important. XMMS2 only allows you to work through IceCast, and enabling something like a socket to XMMS2 concerns me. Just doesn't seem very secure.
* Using a server architecture isn't the only thing happening. If I just wanted a local music server, I'd use MPD. I want a full music player available, frontend, everything.
Questions? Comments? Concerns?