Bug 237155

Summary: Introduce a media player manager
Product: [Applications] amarok Reporter: Richard Hartmann <richih-kde>
Component: generalAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 2.3.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Richard Hartmann 2010-05-10 21:18:48 UTC 
Version:           2.3.0 (using 4.4.3 (KDE 4.4.3), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-4-686

As an alternative to https://bugs.kde.org/show_bug.cgi?id=237151 it would be even better, but more work and a larger change, if there was a dedicated way for media player management.

I decided to keep all requests in one master request after all. If you want me to split them up, please tell me.


While one can argue that a media player is local storage just like an external disk, there is a significant difference inasmuch that on my local disk[s], I am trying to limit duplicates whereas I specifically want to create duplicates on my media player[s].

This media player management window would

a) Keep track of every unique media player I ever attached to my computer and what I copied onto them. When re-attaching, I would be able to see what was deleted and what is new since I last attached the media player.

b) Give me an easy and consistent way to copy media to the player. Think Norton/midnight commander or Kommander.

c) Keep track of all podcasts I have ever copied to a given media player. I want to listen to a podcast once and then remove it from my player. Currently, I need to remeber everything or keep a text file.
Comment 1 Sven Krohlas 2010-05-11 17:08:18 UTC 
Seperate bugs would be much easier to triage, as this now spans many different components and Bugzilla is component oriented...

a) is the local music browser with an additional syncing framework (which is wip)

b) well, just right click on entries in the local music browser...

c) is related to keeping a database on the media device (some of them won#t update it, like most ums devices) and use it

-> seperate bugs, please. :)