adys.wh at gmail.com
Wed Jan 15 14:06:40 PST 2014
On Wed, Jan 15, 2014 at 9:29 PM, Alexandre Franke
<alexandre.franke at gmail.com> wrote:
> On Wed, Jan 15, 2014 at 8:00 PM, Cosimo Cecchi <cosimo.cecchi at gmail.com> wrote:
>> Hi all,
>> Feedback welcome!
> Music player usually get all the content of the Music directory and
> then grab metadata to present the tracks filtered by
> artists/albums/whatever. This is relevant for your virtual disc
> collection, not so much for the notes you record with your sound
> recorder, or the multi-track recordings you're working on with your
> band in a DAW.
> More generically, user generated content and work files are not
> exactly the same as purchased, downloaded, or transfered (from a
> device) media.
> How do you think this should be handled? So far I've seen editing apps
> rely on newly created directories, usually in $HOME, but as I
> understand they are the ones you're trying to move into the
> Another concern, which is related: how should we handle
> foo-but-not-really-foo data? For instance, guitar tablatures in
> TuxGuitar format are music-but-not-really-music since they are not
> intended to just be played back with a music player. With your
> proposal I'd say TuxGuitar could choose to create a subdirecory in
> Music, but how would then your music player react?
I can't comment on the rest but this part should be handled with
simple mime type support. If the app can recognize guitar tabs files,
it'll know what they are - if it can't, it should ignore them.
> Alexandre Franke
> xdg mailing list
> xdg at lists.freedesktop.org
More information about the xdg