I'm kind of picky when it comes to audio. I'm picky about efficiency, and I'm picky about level of control. When I was a wee lad, I used xmms. Then I discovered cplay, and I was satisfied for about a year and a half, but it was a bit slow because it was written in python. Then I rewrote cplay in c, but it didn't work. Then I discovered mpd, which let me have ncmpc running locally in yakuake and on another computer, without the terminals needing to be the same size, which was a plus. mpd's developers turned out to be dicks, however, and in a fit of revenge I abandonned mpd and switched to cmus. cmus absolutely rocks: it uses vi's command mode, and it's really powerful. I should just stop now and enjoy my music, but honestly that isn't my goal. Perfection or bust.
Okay, so for the ideas that I've got in terms of audio software, I'm going to present a problem situation, and my proposed fix:
Let's say you've got a playlist (or library) of music set up, and you decide that you want to hear Dark Side Of The Moon next. You switch to the browser view, :cd /media/music/Pink[Tab]/Dark[Tab], and you see ten tracks. You back off a directory and hit 'a' to add the ten tracks to your playlist. But your playlist is in shuffle mode: you'll hear Gorillaz, Eclipse, Rage Against The Machine, Breathe, etc. The album is treated as individual tracks, like all of your other songs. I envision the ability to create a "container" to lock together those ten tracks, which can then be collapsed into + Dark Side Of The Moon. The container would be treated like any other track, and it would even have its own combined 'length' attribute, so the time bar would read your progress through the album, not the tracks. You could move the "playlist entry" up and down as a single unit. This would let you hit [Space] on the album and see the current track highlit, etc.
Let's say you've been listening to a song, and near the end of it you realize you need to know its name, for whatever reason. By the time you've reopened your music interface, it's skipped to the next song. Now, in a complex audio setup, the previously played song could have come from a library, a play queue, a play list, and any of these could be in shuffle mode, which basically means the previously played track is now ancient history. I envision a "trash can" of the last played songs, or even better, a "history" or "system log" of the events that have happened, which can be filtered on-the-fly to tell you exactly what you need to recall.
Let's say you've got //add meta-tracks, filter matches into playlist, silence as a track, delays in your playlist for alarms, adding section of song to playlist,shuffling between songs albums artists,one-shot shuffling to preview shuffled order,
not - 2008-10-30 08:14:46
Soraia - 2012-03-04 00:07:21
Any updates on when and for how much would the bcarkberly storm 2 would be out in the market? No wifi made me think twice on getting the storm1. thanks!