[issue112] GOM Player infringes GPL in various ways

2010-10-06 Thread InShine

InShine insh...@gmail.com added the comment:

temp_test


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue112



[issue112] GOM Player infringes GPL in various ways

2010-10-06 Thread InShine

InShine insh...@gmail.com added the comment:

Hello. I’m a employee on Gretech corp.
I Know that GOM Player is listed on Hall of Shame list.
GOM Player is one of product on Gretech.
How can I delete GOM Player on Hall of Shame list ?
GOM Player mentions FFmpeg license.
Could you check the issue ?
How can I solve the problem ?
Let me know please.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue112



[issue2270] RTP parser fails on RFC 3550 header extensions

2010-10-06 Thread Martin Storsjö

Martin Storsjö mar...@martin.st added the comment:

I looked at the packet dump, and the patch looks quite ok to me. I touched 
it up a little, here's another version of it. I'll apply it in a few days 
if nobody objects.

--
nosy: +mstorsjo


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2270


0001-rtpdec-Handle-RTP-header-extension.patch
Description: Binary data


[issue2271] LGPL violation afreeca for iPhone

2010-10-06 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

$ ftp ftp://anonymous:passw...@ffmpeg.org/MPlayer/incoming/
Connected to ffmpeg.org.
220 (vsFTPd 2.0.7)
331 Please specify the password.
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Switching to Binary mode.
250 Directory successfully changed.
250 Directory successfully changed.
ftp mkdir test
257 /MPlayer/incoming/test created
ftp cd test
250 Directory successfully changed.

I can now upload any file.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2271



[issue2273] GOM Encoder violates FFmpeg's license

2010-10-06 Thread Carl Eugen Hoyos

New submission from Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at:

encoder.gomlab.com/eng/ offers GOM Encoder (I don't know the price).
The installer (GOMENCODERSETUP_ENG.EXE, size 6236928, md5sum
d57d77caea62e87165b2bc36f270bd31, will upload to incoming/issue) contains a
binary distribution of libavcodec called GVC.dll. Attached EULA is incompatible
with FFmpeg's license, actual sources are NOT available.
Since libx264 is linked against the same binary as GVC.dll, this might be a GPL
violation.
Contact is gomenco...@gomlab.com
whois information:
Gretech Corp.   sk...@gretech.com
WooJun Bld., 891-54 Daechi-dong, Gangnam-gu, Seoul
(Tel) 02-2193-5674

--
files: EULA.txt
messages: 12148
priority: normal
status: open
substatus: open
title: GOM Encoder violates FFmpeg's license
topic: (L)GPL violation


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2273
GOM Encoder Software License Agreement 
( End User License Agreement )

Please read carefully before you install the Software. This End-User License 
Agreement (EULA) is a legal agreement between you (either an individual or a 
single entity) and Gretech Corporation for the GOM Encoder Software 
(“Software”). The Software includes the associations of Internet services 
using on and offline networks, Software product included in the service, alpha 
version, beta release, free and paid versions of the Software. Clicking the 
“I Agree” button or installing, copying, or otherwise using the Software 
means that the user agrees to the terms of this EULA. If you do not agree, 
click the “Cancel” button or do not install the Software.

Installing this software means that you have read, understood and agree to the 
terms bound by this EULA.

1. [The Purpose of Agreement]
  
The purpose is to establish regulations on various options regarding the use of 
GOM Encoder Software (will be referred as “Software”) distributed by 
Gretech Corporation (will be referred as “Corporation”) and the use of GOM 
Encoder paid service.

2. [Effect of and Amendments to the Agreement]

(1) The Agreement is announced at the time of Software installation and becomes 
effective when the user agrees to the Agreement. 
(2) The Corporation can amend the Agreement under reasonable circumstances and 
when changes are made will make notifications about the alterations.
(3) If the user does not agree to the amended Agreement, he or she can request 
for termination. If the user does not express any disagreement against the 
amendment within the 7 days from the time of Agreement emendation and continues 
to use the service, it will be considered that the user agrees to the amendment 
of the Agreement. 
(4) The Corporation will not be held reliable for damages occurred to the user 
who fails to observe the changes made to the Agreement. 

3. [Protection of Personal Information]

At the time of service use error, the Corporation can receive system 
information and data provided by the user under explicit agreement for the 
purpose of resolving the error. However, the Corporation will not be reliable 
for any other personal information exposed due to user imputations.

4. [Payment]

(1) Paid licenses are categorized into individual license and corporate 
license. You have to purchase corporate license to use GOM Encoder at 
companies, corporations, public organizations or for commercial use and cannot 
use with individual license.
(2) In case of individual license, only one license can be purchased with one 
user ID and one license can only be used on one computer at the time of use. In 
case of corporate license, multiple licenses can be purchased with one user ID 
and one license can only be used on one computer at the time of use. 
(3) User Agreement about license payment will be established under the user 
agreement to the GOM Encoder EULA, the physical transaction of payment made by 
the user who wants to use the paid service and the acceptance by the 
Corporation. Only the payment method set by the Corporation can be used. Other 
matters will follow the policies set by the Corporation.
(4) Paid service users will also be considered as having agreed to the 
following. The Corporation can provide the user with various information deemed 
as required during the use of service through the means of e-mail and etc, and 
if the user does not wish to receive the information he or she can unsubscribe 
to such information. However, information regarding major policy changes about 
the service use and etc, relating to the service usage of the user can be sent 
to the user who has chosen to unsubscribe through the means of e-mail and etc. 
(5) If the user experiences damages regarding the service use due to the major 
flaws of the provided service, the user can be compensated through proper 

[issue2270] RTP parser fails on RFC 3550 header extensions

2010-10-06 Thread Ronald S. Bultje

Ronald S. Bultje rsbul...@gmail.com added the comment:

 +/* RFC 3550 Section 5.3.1 RTP Header Extension handling */
 +if (ext) {
 +if (len  4)
 +return -1;
 +// retrieve header extension length (number of 32-bit words)
 +ext = AV_RB16(buf + 2);
 +
 +// add header extension itself to extension length
 +ext++;
 +
 +// convert header extension length to bytes
 +ext = 2;

ext = (AV_RB16(..) + 1)  2;, this isn't barbie-code.

+// abort if extension length exceeds remaining buffer length
+if (len  ext)
+return -1;
+
+// skip past RTP header extension
+len -= ext;
+buf += ext;
+}

Rest OK.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2270



[issue2274] the bottom of frames from Sanyo HD2500 IP cam shows vertical stripes

2010-10-06 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

Please provide output for latest svn (and confirm that the problem is still
reproducible).

--
status: new - open
substatus: new - needs_more_info


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2274



[issue2270] RTP parser fails on RFC 3550 header extensions

2010-10-06 Thread Martin Storsjö

Martin Storsjö mar...@martin.st added the comment:

Applied in SVN rev 25372.

--
status: open - closed
substatus: needs_changes - implemented


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2270



[issue2258] MP3 with PCM inside decode error

2010-10-06 Thread Reimar Döffinger

Reimar Döffinger b...@reimardoeffinger.de added the comment:

On Thu, Sep 30, 2010 at 04:14:24PM +, Michael N. Pritula wrote:
 Media Player Classic 1.3.1405.0, Winamp 5.56 and Windows Media 9.00.00.4503
 refuse to play this file.

Very reasonable of them.

 VLC 1.1.4 plays it very well.

With r25378 I also works in FFmpeg, however

 File 'mp3_pcm.mp3' not attached

prepending a ID3 header to a WAV file and calling it a MP3
is a very questionable practice, as such I don't really consider
it a good thing that FFmpeg now supports that insanity,
particularly since it currently does so without even warning.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2258



[issue112] GOM Player infringes GPL in various ways

2010-10-06 Thread Benjamin Larsson

Benjamin Larsson ba...@ludd.ltu.se added the comment:

On 10/06/2010 09:44 AM, InShine wrote:
 
 InShine insh...@gmail.com added the comment:
 
 Hello. I’m a employee on Gretech corp.
 I Know that GOM Player is listed on Hall of Shame list.
 GOM Player is one of product on Gretech.
 How can I delete GOM Player on Hall of Shame list ?
 GOM Player mentions FFmpeg license.
 Could you check the issue ?
 How can I solve the problem ?
 Let me know please.
 

https://roundup.ffmpeg.org/issue2273
http://ffmpeg.org/legal.html

This should be a good start to read. When you can say that you comply
with all the points on the checklist we will remove GOM Player from Hall
of Shame.

MvH
Benjamin Larsson


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue112



[issue2117] MJPEG decoder crash

2010-10-06 Thread Pavel

Pavel i-love-s...@yandex.ru added the comment:

Why is the status needs more info?
I saw in logs other photos also crash mjpeg decoder (all these photos are broken
uploads from iPhone just like the one attached).
djpeg from libjpeg correctly identifies that the image corrupted (Premature end
of JPEG file) but ffmpeg crashes on that image.
This image crashes also on arm the same way. I also tried that on pre armv5te
build and it also crashes (pre armv5te uses different bistream reader). So, I
think decode_block should check if bit context has enough bits before reading 
it.
Can I change the status to approved/reproduced?


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2117