Name: Tomahawk Player
Version: 0.4
Größe: 30,6MB
Homepage:
http://www.tomahawk-player.org/Supportforum:
http://forum.tomahawk-player.org/Lizenz: OpenSource/GPL
Screenshot/Video:
http://www.tomahawk-player.org/splashAdmin-Rechte nötig?: k.A.
portabel / abhängig von: k.A.
Lauffähig ab (Win95, 2000, XP): Cross-Plattform
Nativ x64?: denke ja
Beschreibung:
Zitat:
What's the story?
Tomahawk was born out of frustration... frustration that the most widely used media players were designed to solve problems of a different era. No longer do we need desktop music players built 10 years ago that jam in CD ripping, label makers, device syncing, into a massive wad of code that takes minutes to even launch. Freed from the shackles of having to worry about supporting legacy use cases, we were able to focus on solving a new set of problems and capitalizing on a new set of opportunities. We thought... "there has to be a better way".
Why can't I easily listen to all the music I have scattered across multiple computers, at multiple locations, from a single interface?
Why can I stream my home iTunes library to my laptop when I am at home, but I can't when I am somewhere else?
Conversely, how come I can stream my co-worker's iTunes library when we are both at the office, but only if we are on the same wireless network (or subnet)?
When I am reading a website that talks about a song, and I own that song, why can't I play my copy directly from that page?
Why can't I subscribe to, and import, playlist metadata from all over the web - and then have that resolve against any/all songs that I have access to?
Why do I have to listen to songs I have on my hard drive, and songs from services I subscribe to, in totally different user experience silos?
If I am a music subscription service provider, why do I need to incur the costs of streaming you content you already have locally?
Hylli