The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: networked mp3 players



I am amazed at how quickly conspiracy theorists have jumped to this
conclusion.

There is, as far as I can see, no evidence that the device uses any SliMP3
code internally, or for that matter any other GPL code.

I grant that it works with the SliMP3 server, but for that matter it works
with iTunes as well. The point about the SliMP3 server is that there are
published interfaces - it's possible to write other clients for it. Exactly
the same happened with the JReceiver software - different people wrote
different clients, some based on the Rio hardware platform, others on
PC-based stuff. Not all of this stuff has released source code.

The same bunch who brought you the "it pinched source code" line
also came
out with a "the product shots are mocked up images - it can't display
pictures"... based on nothing other than an assumption that it was a
repackaged SliMP3.

Roku then announced some differences, such as the fact it uses a
pixel-addressable VFD, so _can_ display graphics...

Mark

----- Original Message -----
From: "Steven Edgar" <yahoogroups@xxxxxxx>
To: <ukha_d@xxxxxxx>
Sent: Thursday, February 19, 2004 6:17 PM
Subject: Re: [ukha_d] networked mp3 players


> There was a comment about this on the slimp3 mailing list a few days
back.
It
> appears that Roku have pinched the source from Slimp3, which is fine
as it
is
> open source, but are refusing to acknowledge that this is where it
came
from.
> Other complaints are that they have not returned their modifications,
which
> given the software is licensed under the GPL is a violation of the
license.




Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.