A real time collaborative music player and tracklist organizer where a group can add, listen and interact with each other music in a totally private and owned cloud auto-scaling container.
Pagination must be implemented in order to reduce the load while rendering and getting all the playlist data for all tracks at once... Above 40 tracks performance is gravely reduced.
Integrate the result from http://realfavicongenerator.net/ for this app, allowing a deeper integration with Chrome mobile, giving a more native experience on Android phones.
There should be a view where the user can see and index of every playlist on y2bt. Obviously the users own playlists should be prioritized over the community ones.
The playlist index should also be ordered by number of playlist plays (the total count of plays on every track of that playlist).
Allow the user to add a song to the master list directly from the youtube search results.
A possible approach would be to set the music url and run the add.js getMusic event.
The search results template should also make a search on the local master list collection and display results before showing youtube results. If the search does not retrieve results, no information should be displayed except the youtube results.
After skipping a track, autoplay breaks and the track starts repeating itself, although the currently active track changes in the list and player metainfo.
There are currently three different logic + templates for the Master Playlist + Personal Playlist + Playlists in general. This behavior must be all present in the same logic + templates.
After opening the app for the first time, this error pops up in the console.
Although this is expected behaviour (The music player markup is cleaned and directly injected in the DOM on each track load), it affects mobile browsers by immediatelly stopping execution of the action, and not playing the track.
The existance of the player must be verified before trying to clean it.
A feature that allows any song to be added to a priority queue, this time based on a local Minimongo Collection (instead of a FIFO array) that has to work the same way as in the enhancement #17 , but:
rewriting current logic to always play the next track from this queue instead of the continuous play queue, while the first is not empty.
Provide a template to view and edit queued songs.
Enhance the player to ensure it does not bug out in case conditions (empty cues, redifining, etc).
In Android for example, playing from another audio source automatically pauses y2bt playback. The play/pause button must be updated on event, to reflect just that.
Use a Session key to store a FIFO array that will be the feed source of the continous play feature.
On playing a track, the array must be emptied and then filled with all the remaining songs from the list where the user chose the song from (Same jquery stuff used now, but get all the remaining instead of just the next one).
On load of the next track, the first element must be removed from the array (pop).
It should not be possible for a user to add the same song twice to the master list...
A verification is must done in the database before adding the song. If it already exists, it should start playing automatically, and the active screen should change to the master list.
When a new song is added through the "Add Song" page the title displays as expected, but when changing song through the "Master List" page, the title loses formatting.
Also it sometimes disappear in "randomish" situations.