[prev in list] [next in list] [prev in thread] [next in thread]
List: amarok
Subject: Music Collection Issues
From: "Joshua Booth" <boothin8or () gmail ! com>
Date: 2008-03-01 23:52:38
Message-ID: b659d8d10803011552x32c6c3eamcff2abc02c71e7f1 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I understand that the maintainers of Amarok don't want to see it turn into a
gigantic program for managing a music collection, but it is halfway there
anyway. It already uses a database backend, allows for transcoding,
organization and movement of files, and burns CD's. But it still has some
issues that seem to be hard to solve without some backend changes. Let me
catalog the issues I see:
Transcoding:
* Transcoding takes a long time (that can't be changed), but doesn't save
the results except on the device. (If it does, I haven't used it)
* Even if transcoding did save the results, they would be listed next to the
originals, and would be indistinguishable anyway
Ex: Coldplay
Parachutes
Don't Panic (Is this one the FLAC or the MP3?)
Don't Panic (What about this one?)
Shiver (This means that Amarok cannot truly be given
access to my entire collection)
Shiver
If I add all tracks from the album, it plays the FLACs and the MP3s!
* If the transcoded files were saved in another place, how would Amarok know
to use them again? They aren't in the database!
So this implies that the same songs in different formats should be treated
the same. But then, Amarok needs to know to play the highest quality
format, but transfer a compatible format to an MP3 player.
Organization:
* Non-library filing is annoying--Not everything should be filed under T!
Ex: "The Smashing Pumpkins" should be filed under S, not T
* There should be some kind of "flexible view" that displays the standard
Artist/Album/Track format when appropriate, but Album/Track format when
displaying compilation albums.
Collection Management:
* I know that Amarok is not supposed to manage your collection, but once you
added transcoding, organization and burning, it basically wants to.
* Why not integrate k3b's ripper into it? I recently ripped all of my CD's
to FLAC (using k3b), then transcoded the FLACs to MP3 for use on my MP3
player. And I had to use two programs to do that, one of which is alread a
transcoder (soundKonverter).
I know that very frequently, people post onto this list with some complaint
about tagging, organization, or duplication of files. My personal gripe is
that if you have two files that literally are the same song, but in
different formats, they are placed one after another, instead of displaying
only one of them. But you have to admit that it needs some kind of
consistent collection management mechanism.
I don't know how much I can help, since I don't know too much about
databases and Qt and KDE, but I would like to help some. I do have a few
ideas for solutions, though:
* Map artists to a number, and then store those numbers in the database
instead of the textual names.
- This lets you use a heuristic to combine "The Goo Goo Dolls" with "Goo
Goo Dolls"
* Associate some kind of "encoding type" with each file (MP3, FLAC, OGG,
etc), and have Amarok play the highest quality encoding type of that file.
* When transferring files to an MP3 player, try to transfer the appropriate
"encoding type". If it doesn't exist, transcode it.
* If you do integrate a CD ripper, have it rip to several "encoding types",
so that you can have an archive version (FLAC) and a portable version (MP3).
I've looked through the collection source code, but I'm still not sure how
much this would break the current system.
[Attachment #5 (text/html)]
I understand that the maintainers of Amarok don't want to see it turn into a \
gigantic program for managing a music collection, but it is halfway there \
anyway. It already uses a database backend, allows for transcoding, \
organization and movement of files, and burns CD's. But it still has some \
issues that seem to be hard to solve without some backend changes. Let me \
catalog the issues I see:<br> <br>Transcoding:<br><br>* Transcoding takes a long time \
(that can't be changed), but doesn't save the results except on the \
device. (If it does, I haven't used it)<br><br>* Even if transcoding did \
save the results, they would be listed next to the originals, and would be \
indistinguishable anyway<br> Ex: \
Coldplay<br> \
Parachutes<br> \
Don't Panic (Is this one the FLAC or the \
MP3?)<br> Don't \
Panic (What about this \
one?)<br> \
Shiver (This means that Amarok cannot truly be \
given access to my entire collection)<br> \
Shiver<br> \
If I add all tracks from the album, it plays the FLACs and the MP3s!<br><br>* If the \
transcoded files were saved in another place, how would Amarok know to use them \
again? They aren't in the database!<br> <br>So this implies that the same \
songs in different formats should be treated the same. But then, Amarok needs \
to know to play the highest quality format, but transfer a compatible format to an \
MP3 player.<br><br>Organization:<br> <br>* Non-library filing is annoying--Not \
everything should be filed under T!<br> Ex: "The Smashing Pumpkins" \
should be filed under S, not T<br><br>* There should be some kind of "flexible \
view" that displays the standard Artist/Album/Track format when appropriate, but \
Album/Track format when displaying compilation albums.<br> <br>Collection \
Management:<br><br>* I know that Amarok is not supposed to manage your collection, \
but once you added transcoding, organization and burning, it basically wants \
to.<br><br>* Why not integrate k3b's ripper into it? I recently ripped all \
of my CD's to FLAC (using k3b), then transcoded the FLACs to MP3 for use on my \
MP3 player. And I had to use two programs to do that, one of which is alread a \
transcoder (soundKonverter).<br> <br>I know that very frequently, people post onto \
this list with some complaint about tagging, organization, or duplication of \
files. My personal gripe is that if you have two files that literally are the \
same song, but in different formats, they are placed one after another, instead of \
displaying only one of them. But you have to admit that it needs some kind of \
consistent collection management mechanism.<br> <br>I don't know how much I can \
help, since I don't know too much about databases and Qt and KDE, but I would \
like to help some. I do have a few ideas for solutions, though:<br><br>* Map \
artists to a number, and then store those numbers in the database instead of the \
textual names.<br> - This lets you use a heuristic to combine \
"The Goo Goo Dolls" with "Goo Goo Dolls"<br><br>* Associate some \
kind of "encoding type" with each file (MP3, FLAC, OGG, etc), and have \
Amarok play the highest quality encoding type of that file.<br> <br>* When \
transferring files to an MP3 player, try to transfer the appropriate "encoding \
type". If it doesn't exist, transcode it.<br><br>* If you do integrate \
a CD ripper, have it rip to several "encoding types", so that you can have \
an archive version (FLAC) and a portable version (MP3).<br> <br>I've looked \
through the collection source code, but I'm still not sure how much this would \
break the current system.<br>
_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic