Music Service Software

This software will be a music service that we will sell to our customers. in general terms, it will be similar to Itunes with some functions similar to Last FM. The application will be, in reality, 3 separate applications: (1.) the client based application (will reside on the client machine and actually play the music), (2.) the server web service that will communicate music, playlists, ect. to the client application, and (3.) the admin module that will allow the administrator to customize the customer's services(i.e. import/create/eidt playlists, ect.). ## Deliverables This is a program that will be used for the reproduction of music. Our customers are buying a service from us where we will provide the ambient music in their businesses over the Internet. This is not to say that we want Internet radio or any kind of streaming, but instead, we want a program that will allow an administrator to manually create play lists for the customer and based on the play list created, the client program will actually download the Mp3's and play them. There are 3 Components: The Client, the server web service, and the administrator. The client program will need to be limited in its functions because it is us who are providing an ambiance of music, we are not providing a list of songs to choose from. The client will have various playlists with their respective songs. The administration module will define when these playlists may be played (morning, night, weekends only, ect.) Please note the following points that must be found in this program: 1. Sound check: We work with a sound volume stabilizer that is also found in Itunes. It is called iVolume. 2. 8 Band Graphic Equalizer 3. There needs to be a manual or automatic mode. Based on the defined use period that the administrator sets, the user can manually select the playlist that he/she wants that is available at that time (This is to say that a playlist defined to be only used on weekends cannot be played on a Monday). The program should also have an automatic setting where the program will simply play the playlists that are available in the defined time period (i.e morning, afternoon, weekends, ect.). 1. Also, if the program is in manual mode and the playlist(s) finishes, if the system is inactive for 5 minutes, it should change to automatic mode and resume play. 4. Each playlist needs to have a certain amount of times it can be played in a certain period of time. This time period and number of times should be variables defined by the administrator. Once the playlist has completed playing the required percentage that has been defined, the system will register it as "played." Once the system has "played" the playlist the limit number of times in the defined period, it will not be available for play in either the manual or automatic modes. 5. When the music is downloaded, it needs to be encrypted in the server and send (encrypted) to the client so that it cannot be stolen and will not work with any other music player. The music file needs to be decrypted in the memory and never be decrypted on the hard drive. 6. This program should eliminate all Windows sounds, and any other sounds from programs, like Media Player, that may make sounds. The goal with this is so that no other sounds will “pollute?? the music service by mixing sounds with it. 7. When in the automatic mode, the playlists should always play in the order of the playlists order on the server. The user, however, can change this order of playlists in manual mode, but if the system returns to automatic mode, it should also return the original playlist order found on the server. 8. This player should have a button so that the user can input a user name and password in order to enable certain functions. 9. The player should have the normal functions: Play, rewind, advance back, fast forward, advance forward, stop, pause, and volume control. All of these, except for advance forward and play, should be disabled until the user inserts the correct user name and password. 10. There should be a function that will monitor the song play so that a song is never repeated. 11. The player should also show the artist, song, album, and the playlist information. 12. The admin should be able to connect to the client to get real time status and statistical information as well as consult how many . 13. The system should have a form where the user should be able to rate the song from 1-5 stars and enter a comment as well. This form should also let the user rate the playlist. Once a month the client should send all of the ratings and comments to the server. 14. The client should be simple to use and be similar to other industry standard players. 15. There needs to be a service running that monitors the client and makes sure it is running. If the client is frozen, the service should End Task on the client and restart. If the client is closed for any reason, the service will restart the client. When started the client should always start playing music and in the last mode (automatic or manual) and resume playing the programmed music. 16. When the client starts, the volume should start in 0 and gradually return to where it has been programmed (through the player which is locked until a user name and password is input). Also, a popup window should come up with a check list like “turn on amplifier, make sure its plugged it, ect.?? 17. If there are any “technical problem?? events, they should be reported to the server immediately. If there is a problem that does not shut the client down, a popup window should come up alerting the user to the problem and informing them that it has been communicated to the server. 18. The playlist GUI should be similar to that of ITunes. There should also be a column dedicated to informing the user how many times they have played the playlist. 19. When the client is installed and run for the first time, it should prompt for a user name and password so that it may connect to the server. In return, the server will send the client the playlists and configuration information. 20. There should be an option of 3 downloading styles: 1. The client should be able to either download the huge amount of data that it has waiting, 2. or it should be able download smaller blocks of information (music), play the information, and then erase it. In the second download style, the client should always keep an emergency playlist on the client that can fill an entire day of musical needs. 3. If possible, we would also like the option of complete data streaming with a 30 second buffer. The administration application (Admin Mod) will be used to create playlists, import playlists from ITunes, define various limitations about the music y player, and manage other customer subjects (like client deactivation, monitoring, ect.). Please note the following points that must be included in the Admin Mod: 1. The Admin Mod should be able to remotely connect and control each of the clients. 2. The Admin Mod should be able to create new clients, modify existing clients (playlists, passwords, usernames, ect.). The Admin Mod should have an inherent organization system so that customers can be managed easy with multiple points of service (clients). 3. There should be a client data base of info which includes all stats, ratings, comments, non-payment inactivations, reactivations; basically anything that occurs with respect to the client. Kind of like a professional looking activity log, 4. This should be designed so that the interface is simple to use. 5. With respect to the playlists, the user should define which clients should be enabled to which playlists. 6. If it is even possible, please give a separate quote for constructing the web service and admin mod on a Mac Os X operating system 7. The Admin Mod should encrypt the music and place it on the server. Also music must be imported through the server. (the client will download the encrypted music directly for the server later on). The web service will have a connection to the server data base, where the user profiles reside as well as the music. The clients will connect to this web service and solicit if there are changes to its (cliente) profile. The web service will answer yes/no. If yes, the web service will tell the client what it needs to download and allow it to download only that. Please refer to the following points that must be included in the web service: 1. The download transmission should be similar to a torrent in that if the connection is lost and restored, the download will resume from the last position and not have to restart. 2. There should be an activity log of downloads by client. 3. There should always be security where possible in the form of user names/passwords/authorization as well as record of the authorization. 4. There should be an option of 3 downloading styles: a. The client should be able to either download the huge amount of data that it has waiting, b. or it should be able download smaller blocks of information (music), play the information, and then erase it. In the second download style, the client should always keep an emergency playlist on the client that can fill an entire day of musical needs. c. If possible, we would also like the option of complete data streaming with a 30 second buffer If you have any questions please let us know.