network filesystem level exposition. Use an existing network
filesystem. read only or read-write, to expose either the entire
database or only portions of the metadata as files that the client can
request ALA SMB, TFTP, HTTP, etc.
Use cases:
Read Only:
User can view album art, lyrics, metada
On 9/8/2011 23:23, Max Kellermann wrote:
> On 2011/09/09 08:00, Christ Schlacta wrote:
>> I've been looking forward to being able to maintain one central MPD
>> database for a long time now. keeping it in mysql will hopefully make
>> that possible. simply update fro
On 9/8/2011 21:37, Max Kellermann wrote:
> On 2011/09/09 00:06, Demian Martin wrote:
>> Max:
>> Thanks for getting to the bottom of the 24 bit bug (3299). Will the fix go
>> into 0.17 git?
> Yes; if you see I didn't soon enough, type:
>
> git cherry-pick 5cf4ce9318acfcd3698b10e173315ad681d39560
if you implement service registration, perhaps the simplest way would
be with a pair of .bat files for windows that will register and
unregister the service, then there's no unclean code, and it's not
difficult to do for the less windows minded.
On 9/19/2010 12:18 PM, Denis Krjuchkov wrote:
nullsoft has a popular open source installer generator. could look into
that.
Max Kellermann wrote:
> On 2009/10/03 21:17, Avuton Olrich wrote:
>> As many know libmpdclient2 is due any minute now for release, and the
>> win32 binary will probably follow behind soon thereafter. I would like
>> t
I think he's referring to my problem, which is caused by having one
big, slow disk dedicated to holding all my music, and is sometimes
mounted across teh network using NFS. I mainly attribute the problem
to hardware deficiencies and don't see it as a bug in MPD, but rather
a reasonable cause to ob
I'll express the same dissenting opinion I have on the bug tracker:
I think this is a really bad idea, and if it's implemented at all it
should be implemented carefully. When you have a large amount of
music to add to the database (imagine you just found your long-lost CD
album at the bottom of y
okay, I want to add a feature request at this point for RTP and RTCP
streaming in MPD, bot configurable in the config file or through your
favorite client.
On Thu, Jan 15, 2009 at 9:38 AM, Max Kellermann wrote:
> On 2009/01/15 18:09, Vasily Stepanov wrote:
>> My justification: I was trying to fo
I'm in favor of scrapping the current protocol and redesigning from
the ground up with a 2.0 protocol that's separate from the current
protocol. publish:subscribe, compression, and encryption are all
decent candidates for a protocol version bump.
all I ask is that if you add SSL, please make sure
I think that Community involvement is a horrible idea. we represent
the very nature of the free open source software community, and we
should act accordingly. We must close our project off to outside
interference and remain purist and isolated!!
if you can't tell, I'm joking. I love the idea.
Problem I have with wiki is organization and ease of finding stuff.
if you can make it easy to find common bits of information from the
front page (config keys, common setups, install and config guides,
supported formats, downloads, "what the hell is this", etc.) right
from the first page you see,
11 matches
Mail list logo
