Hi,
This $100 bounty involves a website whose main content will be mp3 playlists focused upon a specific, ever changing composition.
A theme over-ride (using Foundation theme) to make the Wijering media player the default for
playing generated playlists may be needed, or to write a patch to make it available as a choice (better because it would be more
of a contribution to the community) on the players page. For this project it may be best to just associate a auto-generated playlist to a
html embedded (or php)
Wijering media player.
1) The player should be able to playback playlist items with zero gap (buttspliced) so that one song is presented from multiple playlist items.
2) The player should also be able to show a different image for each playlist item.
3) The playlist should be generated from the ID3 tags embedded in each mp3 snippet.
4) A solution using the Views module (and possibly the Bonus Audio: Playlist) would allow easy presentation of playlists for user selection.
This brings me to solutions I've tried, to help you consider if your own module expertise is appropriate to bring one of these options to completion:
* The XSPF Playlist module generates a nice playlist into the embedded XSPF player using files attached to a node with the Upload module.
Possible solution: Modify the XSPF Playlist module to generate the playlist from the Audio Upload module instead. This would allow the use of the Get ID3 module. Attach images with same filename as the MP3 using upload to associate for player. Hook to SWFTools to use Wijering Media Player, or make Wijering Media player default Audio player.
* The Audio Upload module does generate an XSPF playlist, but the result calls the default embedded player and does not work with Wijering player (lacking .mp3 tag, in format of node/#/etc...). Would need a way to associate image files.
Possible solution: A routine that would modify the Playlist for Wijering compatibility and pull like named image files. Use the player with filtered HTML or PHP for more control over the look, and possibly buttsplicing. Downside? An unpublished node would be in the background doing the dirty work and hand the info to the public node.
* The Views Bonus Audio: Playlist module seems to be a generate an XSPF playlist compatible with Wijering format (embeds the MP3 player); would need to modify those embedded settings, or need to change the embedded to the Wijering Media player and modify those settings . ID info is drawn from the node, not ID3 (not great, but usable). Would need a way to associate image files...
The site is currently on a dev host, Drupal 5.2, the new host is registered and ready for migration or fresh start with 5.3.
Dev site:
http://dev.majorglitch.hypermediative.net
Scott Anthony
Comments
edit...
Scope of this project narrowed by another team member with more Drupal experience, please check here:
http://drupal.org/node/192341
I'd delete this post entirely, if allowed. Sorry...
-s