Sigma Designs Accused of Copyright Infringement 417
Cygnus v1 writes "The XVID team has ceased development of the XVID video codec for the time being because they say that Sigma Designs' REALmagic MPEG-4 Video Codec software includes their code and has claimed it as Sigma Designs' own work. The current XVID homepage includes some binary-level comparisons." Update: 08/23 03:14 GMT by T : Apparently the folks at Sigma have seen that no good is likely to come from this; an anonymous reader submits a link to this release on Yahoo! which says "complete source code will be available for download starting August 23, free of charge, through Sigma's website."
Why stop coding? (Score:2, Insightful)
Re:Why stop coding? (Score:2, Interesting)
The only reason that I could think of would be if they thought Sigma was dependent enough on their code that stopping coding would leave Sigma high and dry. But that's a pretty roundabout way to get back at somebody. I'm going to guess that there are other legal machinations going on right now that they haven't mentioned that contributed to the decision to stop (publicly) coding at the moment.
If these guys are real hackers, they have their own private copy that they're still working on. Whenever this is resolved, expect a huge jump in Xvid functionality :)
Re:Why stop coding? (Score:2)
So what someone is stealing your stuff.
Then why bother putting your code under any kind of license at all?
The XVID guys used the GPL for a reason, and they should expect others to abide by it.
Rape Is still rape if you're not a hooker (Score:4, Interesting)
Software distributed with the GPL is not without cost The 'price' of using GPL code is that if you make changes to the code, you can't distribute the modified object code without also distributing the modified source code.
(I.E. the price is your derivative code).
In any case, these people are stealing copyright code without permission. Since they're charging for it, then they are liable for both the price they're charging for this stolen code and any punitive damages (which can be quite hefty for copyright violation).
It looks like this might be a good time to call in the lawyers.
____________
And yes there IS damage to me from having someone steal my GPL code. When I put code under the GPL, my expectation is that, in return for making my source code freely available, I'll get back from the community that uses my code the work that they do to improve my code. When someone steals my code and puts it into a proprietary product, I loose in a few ways:
Re:Why stop coding? (Score:2, Interesting)
Ignoring them won't help (not sure why you suggested that--if MS used GPL code, say, the kernal, instead of developing their own idea, you'd say ignore them?). You mention sue them--sorry, but copyright infringment usually falls into civil, not criminal (there are exceptions, e.g. DMCA, the other one Ashcroft is using that Clinton signed into law in '97) court. Civil court cases are darn expensive. And if you lose, you're liable for the other parties legal bill.
btw, project development stopped; that's not necessarily all coding.
It's probably the best solution for them.
Re:Why stop coding? (Score:3, Insightful)
Actually, I would say yes. They have way too much money to try to sue them. It's a lost cause for just about anyone unless their lawyer is willing to work pro bono.
You mention sue them--sorry, but copyright infringment usually falls into civil, not criminal (there are exceptions, e.g. DMCA, the other one Ashcroft is using that Clinton signed into law in '97) court. Civil court cases are darn expensive. And if you lose, you're liable for the other parties legal bill.
Not in the US. In fact, nearly every statement you made doesn't apply to the US. Filing criminal charges falls into criminal. Filing a lawsuit almost always falls into civil. Also, in the US you are not, by default, liable for the other parties legal fees. This is one of the problems some people have with the system here. Civil court cases are indeed expensive, but if the loser was required to pay the winner's legal fees, you'd see a lot more lawyers willing to work on a loan, particularly when they're sure they can win given enough time.
Re:Why stop coding? (Score:2, Interesting)
The only way to pressure them is to (hopefully temporary) stop development of xvid. By ignoring & continueing development you would give them a free ride.
"Hey now we can use GPL source from other projects too, they don`t sue anyway ! And those code monkeys keep improving it for free
Re:Why stop coding? (Score:2, Interesting)
Re:Why stop coding? (Score:3, Insightful)
Sigma Boss: We got a letter from some Xvid guy that says we are using their code; are we?
Sigma coder: Uhh, no. Hell no! I am the genius behind our priducts.
Sigma Boss: Those damn freeloaders, well, make them happy and do what we can to shut them up.
Sigma coder: Secretly recompile with loop unrooling and restructure project files.
Xvid group then stops publishing codec updates.
Sigma Boss: Those Xvid guys stopped complaining, good work. Now about those product updates, when will the B-frame updates be finished?
Sigma coder: Well, that is taking a lot more time than we originally scheduled, but should be ready Real Soon Now.
Sigma coder: Busily prepares his resume.
The real point is that Sigma will have to put-up or shut-up. Sigma Designs is a publicly traded company that will have to answer to shareholders and courts if they have been stealing code. This move will expose the truth about what really went on fairly quickly.
press release text (Score:5, Informative)
ERLANGEN, GERMANY -- August 22nd, 2002 -- The XVID development team, author of the popular XVID MPEG-4 video codec, claims that Sigma Designs' REALmagic MPEG-4 Video Codec is an illegal copy of the XVID software and publicly requests the company to stop violating their software license and copyrights.
XVID is a leading open source MPEG-4 video research project: software distributed by XVID is covered by a Free Software license, the GNU General Public License (GNU GPL). The XVID team announced that Sigma Designs' REALmagic MPEG-4 Video Codec includes wide portions of XVIDcodec software. By not offering a corresponding source code distribution and by claiming sole authorship on the product, Sigma Designs' Inc. is violating the GNU General Public License and the copyrights of the XVID authors.
XVID learned about the license violation in early July, soon after the initial release of the REALmagic software (version 1.0). Sigma Designs' were immediately contacted, and replied confirming the violation and promising to replace all violating code.
Version 1.1 of the REALmagic software was released on the 9th of August. After examining the new version, XVID developers concluded that the violating code was not replaced, but disguised by programming and compiling tricks. Sigma Designs' were again contacted and asked to remove the REALmagic download link from their website. Thus far, they have not shown any sign of cooperation.
In a statement to the XVID development team, project founder Michael Militzer showed his disappointment regarding Sigma Designs' behaviour: "We have been quite reasonable and have given Sigma Designs' ample opportunity to resolve this issue. Apparently none of our demands have been taken seriously. Nearly two months after the initial release of the REALmagic MPEG-4 Video Codec, Sigma Designs' is still knowingly infringing the GNU General Public License."
Militzer believes this infringement might be of high general interest: "This is an unfortunate event, not only for us but for the whole Free Software movement. Therefore we hope to receive wide support from the Free Software community in our efforts to convince Sigma Designs' to respect the terms of the GPL."
Evidence supporting the claim has been published on the XVID website.
http://www.xvid.org/v1_0_comparison.pdf
http:/
About XVID (http://www.xvid.org/)
XVID is a leading open source MPEG-4 video research project, founded by the German student Michael Militzer in August 2001 to continue the efforts of DivXNetworks' former OpenDivX project. Today, the XVID project consists of users and developers from all over the world. XVID publishes all its software under the GNU General Public License (GNU GPL).
About Sigma Designs Inc. (http://www.sigmadesigns.com/)
Sigma Designs' headquarters are located in Milpitas, California. The company specializes in MPEG based video hardware for encoding and decoding. Recently Sigma Designs' introduced the Xcard, the first consumer hardware MPEG-4 decoder in the form of a personal computer add-on card.
About GNU GPL (http://www.gnu.org/copyleft/gpl.html)
The GNU General Public License is the most frequently used software license for Free Software development and is supported by the Free Software Foundation (FSF). Software distributed under the GNU GPL grants everyone modification and redistribution rights, on the condition that derived or redistributed software carries the same license.
Contacts
For contacting the XVID team please use the e-mail addresses contact@xvid.org or contact@xvid.de
Please address your request to one of the following persons:
Daniel Smith (USA)
Michael Militzer (Germany and international)
Christoph Lampert (Germany and international)
Edouard Gomez (France)
Sigma has released to code (Score:3, Informative)
MILPITAS, Calif.--(BUSINESS WIRE)--Aug. 22, 2002--Sigma Designs, Inc. (Nasdaq:SIGM - News), a leader in IP video streaming solutions, today announced the release of the source code behind its free MPEG-4 video CODEC that works as a plug-in under Windows and encodes digitized video content into fully compatible ISO MPEG-4 video files. The complete source code will be available for download starting August 23, free of charge, through Sigma's website (www.sigmadesigns.com), to support developers wishing to enhance the MPEG-4 encoding.
"We are pleased to provide the development community with an open source MPEG-4 CODEC, and anticipate that this will accelerate technical improvements and enhance the proliferation of MPEG-4 content," stated Ken Lowe, Sigma Designs' vice president of business development.
About Sigma Designs, Inc.
Sigma Designs specializes in silicon-based MPEG decoding for streaming video, progressive DVD playback, and advanced digital set-top boxes. The company's award-winning REALmagic Video Streaming Technology is used in both commercial and consumer applications providing highly integrated solutions for high-quality decoding of MPEG-1, MPEG-2, and MPEG-4. Headquartered in Milpitas, Calif., the company also has sales offices in China, Europe, Hong Kong, Japan, Korea and Taiwan. For more information, please visit the company's web site at www.sigmadesigns.com/.
Re:Sigma has released to code (Score:3, Insightful)
There is no notice that they are using previously GPLed code, or where it came from.
So they're still misleading their shareholders and the public.
Then again, if you look at the history if DivX;-), you'll see references to a hacked Microsoft codec, too, and that quite likely was not GPL =)
Re:MOD Parent Post up! (Score:4, Insightful)
if by not attainable you mean that clicking on the link to xvid.org then clicking on the press releases in the files section is an impossible feat, then yes the information is not attainable throught the links in the original post. it is indeed a harsh reality.
how about the unattainable information in pdf [xvid.org] format.
for more unattainable information i would goto this oracle of truth [google.com]
As someone who once worked for Sigma Designs... (Score:5, Informative)
Re: (Score:2)
Re:As someone who once worked for Sigma Designs... (Score:5, Insightful)
What the XVid folks really need is some sugar-daddy corporation (FSF, IBM, anyone?) to fund their legal costs going after SD.
But before they do even that, I'd suggest the XVid people just tell Sigma Designs that if they don't conform to the GNU Public License, they'll start contacting their distributors to tell them about the situation - and that they're selling products in violation of someone's copyright.
Believe me when I say that Sigma Designs will fold like a house of cards if they do that. At one time they had such a bad reputation with distributors, they had a terrible time just getting their products out on the shelves. Assuming little has changed (and this episode convinces me it hasn't) it wouldn't take much to have them get dropped completely. And that would hurt them where it hurts the most - in the pocketbook.
Re:As someone who once worked for Sigma Designs... (Score:5, Informative)
This was in 1998. Well after software-based codecs were freely available (Microsoft shipped ActiveMovie with MPEG-1 playback support back when it released Internet Explorer 3.0 somewhere around 1995? 96?)
I did a demo for the deparment head showing two systems side-by-side, one with Signa's REALMagic card and their codec, and the other with Windows Media Player installed. Ironically, the guy picked the software based solution as the "higher quality" solution and said it was worth the extra $200.
Needless to say, when the labels were revealed, they immediately cancelled the pending order for 6000 REALMagic cards, a savings of $300,000.
Sigma Designs seems like a bunch of snakeoil salesmen to me.
- JoeShmoe
.
Sue them (Score:3, Interesting)
This sucks.. I've had people claim my code as their own and it just deflates your morale. Looks like it deflated XVID to the point where they pulled a Cartman*.
*"Screw you guys, I'm going home."
Re:Sue them (Score:2)
Re:Sue them (Score:5, Insightful)
There should be a donation system to finance a lawsuit for the GPL - perhaps with the EFF or the Free Software Foundation being the collector.
We are the GPL. We are the ones who use it, live it breath it - and if we are truly a community that believes that the sharing of ideas is more powerful then the hording of them, then we must be the ones to pay for its support.
Re:Sue them (Score:2)
Depending on how big and solvent Sigma is and how straightforward the case then it should be possible to get a lawyer to work on it for a share of the award. The XVID folks are almost certainly going to be able to get damages (if they win).
Lawyers are more than happy to work for a percentage on cases that have the potential for large damages.
Re:Sue them (Score:2)
Re:Sue them (Score:2)
They're a public company, so I'm guessing no matter how 'big' or 'solvent', they'll have sufficient insurance to make a lawyer at least interested, especially if it is fairly cut and dried. IANAL, but I would guess it'd get settled fairly quickly if filed. Again, being public, these days, there's a lot of scrutiny.. they'd either have to disclose quickly or the once yawning press might go heavy covering it. If so, their stock could drop faster than Martha can make an omelet.. or a judge might just permit an injunction against any distribution until the case goes to trial, again, if he thinks it's fairly cut and dried. Again, IANAL, but I'd like to see this one go forward. (Interestingly, it seems the only way to truly get them back to a closed product would be hire new folks and require it be developed in a clean room. Simply saying they'll take out the GPL code shouldn't suffice. That'd get REAL costly, possibly nudging them to open their source and follow GPL as it was intended.)
Re:Sue them (Score:2)
Re:Sue them - I agree, for all copyright violation (Score:2)
Re:Sue them - I agree, for all copyright violation (Score:5, Interesting)
http://forum.doom9.org/showthread.php?s=
Specifically:
I spoke to a manager at Sigma Designs over the phone a couple weeks ago, and he basically verified the accusation - a programmer "mistakenly" based their MPEG-4 codec around XviD, added a few patches, changed the interface (but not by much), then released it as their own. We were informed that they were replacing all GPL'ed code with their own, to avoid a licensing problem (even though copyright infringement had already occurred, of course).
After that, version 1.1 came out, which was a complete slap in the face. Supposedly "rewritten", it was nothing but a different checkout of XviD with a few registers changed and some code reordered.
Should be an interesting few days.
-h
Re:Sue them - I agree, for all copyright violation (Score:2)
i tried napster once, but never really liked it that much. i preferred to rip my own cd's since i could generally produce stuff with better quality.
GPL Powerless (Score:2, Insightful)
If you're a small developer and they're as resonably sized company, the prospect of shelling out bucks to stop them from copying something you don't make money off anyway is no good.
Being closed source doesn't protect your work from being copied, but it's at least a lot harder to rip it off and stick your name on it.
--
GCP
Re:GPL Powerless (Score:5, Insightful)
They can do this for any license, including one where you only release binaries (I've seen at least one instance where the only difference between two programs is that one had the startup messages patched to display a different message).
Re:GPL Powerless (Score:2)
Re:GPL Powerless (Score:5, Interesting)
Being that Xvid is a larger project than Virtual Dub, I would be highly surprised to not see the FSF step in at some point.
Re:GPL Powerless (Score:2)
Re:GPL Powerless (Score:5, Informative)
If someone plagarizes your work, sue them. The only information the judge is going to need is a copy of their source, and yours. Are they the same? Judgement for plaintiff.
Finding a couple of pro-bono expert witnesses in this case should be a snap, if that's even necessary. Hell, ask Stallman, he's always looking for a pulpit.
Over the years, I've had three or four clients who didn't want to pay for work I had performed. A couple of them even said "We're ready to be the 800 pound gorilla on this matter." (That's a direct quote from one, BTW).
Ok, you be an 800 pound gorilla. I have all my notes, all the specifications, all the correspondence related to the project ready to go. I have notes on every phone call, every meeting, every conversation. It costs me $40 to file, and all I have is time. If you want to tie up your $150 an hour lawyers for six months fighting an angry badger about a $20K project, go right ahead.
Funny, the check always shows up after that.
Don't let people push you around because you're a small operation, or because they think having more money guarantees them victory through intimidation.
K.
Or don't (Score:2, Insightful)
Or don't ask Stallman, because he's always looking for a pulpit. Find someone whose credentials are as good, but who's less likely to offend the judge by getting preachy.
Re:GPL Powerless (Score:2)
If people knew what it took, 40 dollars and some time would be worth it. I think the "800 pound Gorilla" idea has people thinking it would cost too much time and money.
Statutory damages for willful infringement (Score:3, Informative)
So suing Sigma Designs is not necessarily a futile effort, though of course it will take some resources and I don't know if it will happen. As for me, when I use the GPL on something interesting, I generally assign it to the FSF, so the FSF can then take action if necessary against infringers.
Finally the missing step!!!! (Score:5, Funny)
2: Get ripped off by a for-profit outfit
3: Prove it, and sue
4: Profit!
Re:GPL Powerless (Score:2)
I'm not surprised (Score:5, Insightful)
It's easy to think, who would ever know? Comparing binary compiles is a good way of testing, but it's not 100% proof. It's damn close, but would a judge know that?
Most interesting of all, will the FSF actually do what it always said it'd do, and protect this GPLd software? And will the GPL stand up in court? IANAL, but I don't see any reason why it shouldn't. This sort of thing needs to be dealt with swiftly however, lest other companies get the idea that it's OK.
Re:I'm not surprised (Score:4, Interesting)
Re:I'm not surprised (Score:2, Informative)
So, yeah, the bully is in the playground, but the XVID has a big brother he can call on.
Re:I'm not surprised (Score:3, Interesting)
Re:I'm not surprised (Score:2)
Where's the DMCA when you need it? (Score:2)
Here's to hoping they smack these hoes with the DMCA.
Any Questions? (Score:5, Informative)
MILPITAS, CA, (August 12, 2002) - Sigma Designs (NASDAQ: SIGM), a leader in digital decoder solutions, announced today that the Company will be discussing second quarter results during a conference call on Tuesday, August 27, 2002, at 4:45 p.m. Eastern time. The dial-in number is (612) 332-0226. A question and answer period will take place at the end of the discussion. The earnings release will cross the wire at the close of market on the same day.
The call will be webcast live from www.vcall.com. An audio replay of the call will be available shortly thereafter the same day and will remain on-line for 30 days. For further information, please see the link to this site on our website at www.sigmadesigns.com or email investor relations at IR@sdesigns.com.
Re:Any Questions? (Score:3, Insightful)
Q: "Does Sigma Designs have any comment on the recent accusation from the XVID team that their MPEG-4 codec infringes on XVID's copyright?"
A: "We're not aware of any court filings pertaining to the matter, so no, we have no comment."
Conference calls are for analysts. B-) (Score:5, Insightful)
Q: "Does Sigma Designs have any comment on the recent accusation from the XVID team that their MPEG-4 codec infringes on XVID's copyright?"
A: "We're not aware of any court filings pertaining to the matter, so no, we have no comment."
Perhaps you will get that answer, but you may make other shareholders aware of it and start thinking about if they should still own stock.
That will get the company's attention better then anything.
It's better than that.
Conference calls are for analysts, i.e. reporters for the financial media and stock brokers. ANYONE can call in. (But you'll be asked for your affiliation. I recommend one of our big guns be the questioner - like somebody from FSF.)
Ask that question and the whole financial media community will hear it as:
There IS no good answer. So:
The brokers will call their customers and tell 'em to dump ahead of the rush.
The funds will just dump right away and try to beat the brokers to the market.
The analysts will write scathing articles about the stock for the financial papers and shows.
And their stock tanks. Even if the company survives the executives' stock options turn into wallpaper.
And that's BEFORE you get around to actually filing a suit. B-)
I'd go out and short 'em right now (or buy puts) - except that the software codec is not their core product. So they can clean up their act by releasing the source to the software codec under GPL before the conference call.
And the news (including links to XVID's smoking gun and the fact that slashdot has this item already) is already on the Yahoo SIGM [yahoo.com] stock discussion board. So it will already be factored into the price by the time I could trade. B-(
Re:Any Questions? (Score:2)
Even so, I think it would be good for
Read the diassembler output (Score:4, Insightful)
Makes you wonder how often companies silently steal code
Re:Read the diassembler output (Score:2)
IF you include the original license along with your software. I was looking at some page (IIRC linked off the zlib website) showing products using zlib. Often (mostly on commercial Windows apps) there is an additional note: (copyright notice removed). They don't explain exactly what this means, but I suspect removing such a notice violates the license.
ISTR back when W2K was released there were allegations that it used OpenBSD's TCP/IP stack without attribution. I can't remember how that ever turned out, though.
Re:Read the diassembler output (Score:2)
Well, the BSD license says that the license/attribution notice must stay with the code and its derivatives, but since you don't necessarily have a right to look at BSD-derived code, and there's nothing about using preprocessor directives to eliminate the comments from the binary, there's no way to know.
ISTR back when W2K was released there were
allegations that it used OpenBSD's TCP/IP
stack without attribution. I can't remember
how that ever turned out, though.
A friend and I were discussing this a while back - he recalls seeing some files working at MS that were BSD-licensed code, and IIRC the license notice wasn't actually stripped out, but it had been taken out of context and slapped down at the bottom of the file, in a not-likely-to-be-read place. He was of the opinion that it was a sleazy but legal move. No idea whether it was the OpenBSD TCP/IP stack.
Re:Read the diassembler output (Score:2)
ISTR back when W2K was released there were allegations that it used OpenBSD's TCP/IP stack without attribution.
What happened is that microsoft used some ported bsd utilities, such as ftp and telnet, which spit out the copyright message on startup. Somehow somebody got confused and thought that this meant that the TCP stack was from BSD, when it's a complete custom job.
Ok, I read it.. let's talk base rates (Score:2)
How likely is it for the two dumps to have that much similarity by chance, or by convergence?
This is the 'base rates' problem. Taking an example from My Cousin Vinny, you can say "wow, that's amazing, those two car tires make exactly the same tracks" but it's meaningless if most cars have the same tires anyway. Could this be another such situation? If you compared two programs compiled on the same platform, you're bound to find identical code somewhere, and it becomes more likely the smaller the regions you look at. Comparing huge asm dumps is not likely to be compelling to a jury who knows nothing about asm, and comparing small asm dumps lacks statistical weight.
To really support their case, these guys need to get research data on the statistical similarity or dissimilarity of two programs written to do similar things.
Sony and SN Systems copied GCC for PlayStation (Score:5, Interesting)
I think... (Score:2, Insightful)
Look at those comparisons between the two DLLs... the assembly is identical between the two. It'd be a damn coinkadink that two independent code bases would be compiled into an identical DLL.
Mike.
Re:I think... (Score:3, Informative)
I'd say it's certainly possible but what XVID has demostrated has me in awe. That's damn near impossible.
As long as they can demostrate large and complex blocks of assembly which are identicle then you're right: there's almost no way that could happen with two independant code blocks.
However, it is possible, just not to this extent. An exmaple would be if two blocks of code independantly implemented quick sort or Euler's algorithm. In that case I would expect those two peices of assembly (provided that they were compiled with the same compiler) to most likely be identicle beacause those are algorithms that are so popular and refined that almost every developer implements them in the same way.
But in this case XVID has certainly demonstrated the large and complex blocks of identicle assembly to prove that they were ripped off. And not only that but that the pieces of identicle code occur at almost the same offsets in the dll!! That's a very good indication that Sigma has extended on, or simply modified, XVID's original code base.
I sure hope they can somehow find the resources to sue Sigma's pants off. I will certainly make a donation if they go that route.
--
Garett
Anybody else notice... (Score:2, Interesting)
Re:Anybody else notice... (Score:5, Funny)
Nice DMCA violation there. Heh.
Tempting (Score:3, Insightful)
Re:Tempting (Score:3, Insightful)
Re:Tempting (Score:2)
Re:Tempting (Score:4, Funny)
hipocracy
n : rule by hippopotamus, a massive thick-skinned herbivorous animal living in or around rivers of tropical Africa.
Sorry, couldn't resist. Yes, as you said, tempting.
Count me in. (Score:2)
Of course this presumes some sort of reputable arrangement so I know I'm not sending $25 to some wise-ass AC with a Paypal account, but if it comes to pass, let me know at eodell@sfront.net, and I'll pony up right away.
Incidentally (and IANAL), while it is hard to sue for damages when you're not actually selling something, I'd be surprised if the XVID team weren't entitled to a substantial chunk of any profits Sigma has been making with their work.
Re:Count me in. (Score:2)
I rather suspect this is a matter of principle and fairness. If Sigma was handing the modified code back to XVID I suspect they'd be happily merging it back into their tree and we wouldn't be having this discussion. We'll see how things pan out, but I for one hope that Sigma gets sued into compliance.
ehmmm... why the shouting? (Score:2, Insightful)
Re:ehmmm... why the shouting? (Score:2)
the proof is RIGHT ON THE FRONT PAGE [xvid.org]
And while this isn't a court ruling, I think one would have a hard time finding a programmer worth his/her salt that would say that the evidence doesn't look incredibly incriminating.
Re:ehmmm... why the shouting? (Score:2)
Re:ehmmm... why the shouting? (Score:3, Informative)
-- Bob
Re:ehmmm... why the shouting? (Score:3, Insightful)
All briefs may be filed via the clerk at The Court of Public Opinion.
*May not apply in some countries. Please check the label on the back of your government for democracy content.
Sigma Design Resumes (Score:5, Funny)
Qualifications:
Comment from the FSF (Score:5, Informative)
Not a GPL Legal test? (Score:2)
Lots of similarities (Score:2)
My question is, why can't XVID enforce the GPL by taking the code they've decompiled, diff it, and keep what they want?
Dirty programmers (Score:3, Informative)
In our case a competitor heard we were working on a program with some features similar to theirs. So to try and create the Dirty Programmer situation our competitor sent copies of their program to our developers trying to get them to look at it. Lucky for us the developers went to management and they went to legal department. Legal collected all the copies of the program and had a hell of a chat with our competitor.
Understanding GPL is not trivial. (Score:2, Interesting)
However, I don't think that even the majority of the software companies, used to deal with closed source, know what GPL means.
BSD license is VERY clear and simple. LGPL is somewhat clear. GPL then...well... I have not yet seen a good and BRIEF explanation on for example : what in practise - makes the GPL spread to new code - when does your software become automagically governed by GPL? Where's the magic line. I think I can somewhat imagine myself where the magic line is but I am not able to express this in one simple sentence which would not leave any exceptions. Can you? If yes, please post it here. It would make it much easier for many.
I can very much understand even the feelings of those who think "GPL is a virus" before someone can express it's meaning without sounding like a hippie, if you know what I mean :)
Re:Understanding GPL is not trivial. (Score:3, Informative)
IANAL, but I believe the answer is: when your software is considered a derived work of GPL'ed code [gnu.org], according to the copyright law of the land.
There is, as far as I can tell, no "bright line" between when this does and does not happen, nor can one be made to exist, short of "everything infringes" or, more practically, "nothing infringes".
I've written about this principle in length on USENET's gnu.misc.discuss group [google.com] in the past, if you want to search for my posts from years ago.
But the main thing to remember is: just because we're dealing with technology here doesn't mean we can expect to, or expect the law to, draw us a nice, technologically clean "line" between infringing copyright and not infringing it.
So, the question being "does my program derived from GPL'ed code?", two things, at least, must be answered:
What actually constitutes your program, which, in copyright terms, is the "work"?
Does that work contain a substantial portion of someone else's GPL'ed code?
Anyway, since the GPL "protects" code no further than copyright law defines "derived work", it cannot definitely answer the question.
Instead, all it can do is limit the degree to which copyright law's view of a "derived work" might extend beyond what the GPL intended to protect.
Hence things like the "mere aggregation" clause.
Bit packing (Score:2, Insightful)
Looking at the copied code in the pdf files cited, a lot of it relates to bit packing, unpacking, and color transformations. Whilst this code may be copied, there are just so many ways to do these operations. Several of the examples include MMX instructions, but pipeline scheduling usually means there's a right way (speed-up) and a wrong way (slow down). If we were kind to Sigma Designs and assumed they wrote the routines independently then it wouldn't be surprising some of them were the same, ie only so many ways to do this stuff.
Is there... (Score:2, Interesting)
DivXNetworks also sad to hear about this (Score:2, Informative)
How would we know? (Score:2)
Perhaps it would be worth collecting an archive of disassembled open source programs and then using it to compare against commercial products.
We'd need a wide spectrum of open source code compiled in different versions of GCC and other compilers, then disassembled and archived in a DB. We'd also need a modified search algorithm, and from what little I know about bioinformatics, BLAST does for nucleotides what we need for opcodes.
Anybody think this is feasable? Worthwhile? Intresting enough to work on?
-Ryan
It's not a slam dunk (Score:4, Interesting)
If not, they should register it right away, while Sigma is still distributing the alleged infringement.
If not registered, you can only get actual damages. And it's easy to see a court saying that actual damages -- which are financial, not personal -- are zero in a case like this. How much money did the team lose? You might do better arguing how much Sigma made from the infringing code but they would of course make the argument that the money came from their proprietary additions, not the GPLd code which of course anybody can get for free.
To compel them to comply with GPL, you will have to get the court to agree with the implied licence. That's harder, though if they really have documents from Sigma admitting that they were aware of the GPL terms you might have a shot.
Otherwise, I don't think anybody has had a court rule that you would be bound by the GPL contract if you used GPLd code. They would rule you violated copyright, but will they rule more?
Think about it. If I put a licence in my code saying "Use this code without my permission and you must give me your whole corporation" no court would consider that enforceable.
Will they consider it enforceable if the licence says "use this code without my permission and you must give away all the source code to everything you bundled with it"? Also in doubt.
Could be. Could not be.
Re:It's not a slam dunk (Score:3, Interesting)
That's not what they are saying. All they are laying claim to is the DLL file which contains the stolen GPLed code.
If you take my code, compile it, and sell it, that doesn't make it yours.
Binary-Level Comparisons ring true! (Score:2)
From the homepage:
If you ask me, that's pretty damning evidence of binary-level code stealing!
unanswered question (Score:3, Interesting)
Re:unanswered question (Score:4, Informative)
"why have they ceased development?"
If you were painting someone's house, and you
found out for certain that they had no intention
of ever paying you, would you keep painting the
house? Or would you take your ladder, your paint,
and your brush, and go elsewhere?
What if you were painting the house, and you found
out that not only were you not going to get paid,
but that the person was going to then take your ladder,
your paint, your brush, your truck, and call the police
to have you arrested for trespassing?
Would you stay and finish the job?
How would you feel about this story if the Sigma folks
had finished their product, and then turned around
and accused XVID of stealing THEIR work? Who's to
say they STILL won't try that?
Unfortunate abuse of noble intent (Score:3, Insightful)
The XVID people suggested that we email Sigma Designs requesting the source code. This is a good idea as it will hammer down the point that they are in violation of the GNU license agreement. It doesn't take long. I drafted the email below in under ten minutes:
To whom it may concern.
After comparing the disassembled code of Sigma Designs REALmagic MPEG-4 Video Codec V1.0:rmp4.dll and XVID MPEG-4 Video Codec 01-May-2002:xvid.dll, there can be no doubt that the two libraries came from the same code base.
As you know, XVID was released under the GNU license and such being the case, your software developed, released and based on intellectual property covered by the GNU license must also be released under the same license.
The license under which XVID was released expressly requires that the source code based on XVID which is developed and released in binary form by any party other than the original copyright holder be made available.
Whereas you are selling a product which is indisputably derived from the XVID code base, I hereby request that you provide a means whereby I may obtain the modified source code.
Ignoring this email or refusing to comply will constitute a violation of the GNU licensing agreement that you willingly entered into when you modified the XVID code.
Please be advised that violating this licensing agreement will almost assuredly result in costly litigation and judgment against you.
Thank you.
Eric L. Damron
Re:How retarded. (Score:2)
NET act? Criminal prosecution? (Score:2)
The reproduction or distribution of 10 or more copies of 1 or more copyrighted works which have a total retail value of $2,500 or more constitutes a felony, with a maximum sentence of three years imprisonment and a fine of $250,000. The reproduction or distribution of 1 or more copies of 1 or more copyrighted works which have a total retail value of more than $1,000 constitutes a misdemeanor, with a one-year maximum sentence and a fine of up to $100,000.
The XVID developers should file a complaint with the U.S. FBI.
Re:No, use corporation speak instead (Score:5, Funny)
Re:No, use corporation speak instead (Score:3, Funny)
Re:"napsterize" the shit out of it! (Score:2)
Re: (Score:2)
Re:Have any of you actually read the comparisons? (Score:2)
YES! I read it carefully - it's a smoking gun!! (Score:5, Informative)
Standard optimization trick (Score:3, Informative)
So compilers will often unroll a loop and add a jump to the correct starting point at the start. Even unrolling a loop once (duplicating the code once) can have a noticeable impact, and I think 4x and 8x are most common. 16x seems unusual, but it could be a high optimization level.
Re:What I like... (Score:3, Insightful)
That, to me, is the most damning of all the evidence. Directory structure: oh, we were inspired by their structure. Compiled code: optimization conincidence. But coming up with a hand optimized assembly code of that length, and having it accidentally that close - not in a million years.
Re:At least these ppl have courage of convictions. (Score:2)
I'm not going to listen to this crap about them being helpless. They can file a lawsuit, just like anyone else, and they can let it be settled in a court. As it is, they're just bending over.
Re:Lets not jump the gun here... (Score:2)
Re:Sue (for money) for GPL violations? (Score:3, Informative)
Specifically, see 17 USC 504 (b): you choose between actual damages and statutory damages, and profits of the infringer due to the infringement count as actuals.
Re:Sigma still doesn't get it. (Score:4, Insightful)
License. This Software is licensed by Sigma, free of charge, to you as end user solely for the purpose of building ISO MPEG-4 compatible content for your own use. This license to you is personal, non-transferable, non-exclusive, and without right to sublicense the use of the Software. You may NOT modify, prepare derivative works of, rent, lease, distribute, sublicense, sell or transfer the Software or any part thereof.
And added to all (most?) of the source code files --
Copyright © 2002 Sigma Designs, Inc. All Rights Reserved
Source and object code (Copyright Sigma Designs 2002) may be covered by one or more pending patents.
(GPL header stuff)
Sigma Designs, Inc. www.sigmadesigns.com
This code inspired by the XVID MPEG-4 VIDEO CODEC
Although I think the best bit comes again from their Click-thru licence to get the source --
You also expressly agree that you will not violate any copyright of a third party or Sigma in your use of the Software.
Bwahahahaha. Do as I say, not as I do!
Idiots.
grnbrg