Proposed additions to the portable_audio_player namespace

David Zeuthen david at
Tue Mar 7 21:19:57 PST 2006

On Tue, 2006-03-07 at 15:57 -0600, Gabriel Burt wrote:
> On Tue, 2006-03-07 at 14:43 -0500, David Zeuthen wrote:
> > Btw, are the output_formats and input_formats useful? IIRC they are both
> > a mixture of containers and actual encoding formats. I dunno how to fix
> > that or if it's even a problem; I'm not an expert in the audio / sound
> > domain..
> I think they are useful.  In Banshee we use them to decide whether we
> need to transcode files before putting them on a device.

Yea, that was the plan all along when we introduced these properties.
Glad to see that Banshee is taking advantage of them! 

I was more wondering if we need to make a distinction and e.g. export

 1) what container formats the player supports

 2) what codecs it supports

 3) what combination of container/codecs it supports

but last time I checked this is hard to express in MIME types.

> Attached.  I made the playlist_folder into playlist_path with a %File
> variable to accommodate devices that may only allow a single playlist in
> a specific location.  I didn't add a %TrackNumber because I was thinking
> that applications could choose how to format the file name (01 - Track
> Name.mp3 for example).  But I'm not certain - maybe we should allow it
> to be fully dictated by the device.  The original goal of the
> filepath_format key was really support different music folders and
> hierarchy limitations, not file name formatting.

Sounds good, I've committed your patch. Thanks. Any chance of patches to
the fdi files for implementing this? :-)

> By the way, I've been browsing the HAL spec via this URL:
> and it used to come up as a nicely formatted HTML page, but now it's
> plain text..  Firefox recognizes it as text/html but it's still just
> text.  All the HTML tags seem to have been removed in the last commit -
> was this on purpose?

No, I got a defect Docbook toolchain on one of my desktop boxes at work.
I should probably fix this. It should be fixed in the CVS repo now since
I committed this from my laptop.


More information about the hal mailing list