Ronald S. Bultje rsbul...@gmail.com added the comment:
Ping
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1628
Ronald S. Bultje rsbul...@gmail.com added the comment:
Looks American, sweet, - SFLC.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1883
Ronald S. Bultje rsbul...@gmail.com added the comment:
Administrative Contact:
king, jack w...@moyea.com
shenzhen
shenzhen, 518000
China
+86.15895658525
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1810
Ronald S. Bultje rsbul...@gmail.com added the comment:
Administrative Contact:
Actecom Trading Company
Goblet Jean Louis
39 Av Notre Dame
Limal, 1300
BE
+32.10401077
acte...@scarlet.be
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Ronald S. Bultje rsbul...@gmail.com added the comment:
Administrative Contact:
los, viche viche...@yahoo.com
308 Ningxia Road
Qingdao, Shandong 266071
China
+86.158
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
Administrative Contact:
Server Hosting Company, H4Host ad...@h4host.com
H4Host.com
1901 60th Place E.
Suite L4467
Bradenton, Florida 34203
United States
6175076598 Fax -- 6175076598
Is their hosting provider.
http://www.softwaremile.com
Ronald S. Bultje rsbul...@gmail.com added the comment:
Original binaries uploaded to incoming/issue1625/. FFmpeg is indeed there.
bash-3.2$ find . -name '*av*'|grep dvdpl
./Contents/Resources/XBMC/system/players/dvdplayer/avcodec-52-x86-osx.so
./Contents/Resources/XBMC/system/players/dvdplayer
Ronald S. Bultje rsbul...@gmail.com added the comment:
Handler for ovh.org/ovh.pl:
OVH
2 Rue Kellermann
59100 Roubaix
Francja/France
+48.71 7860700
po...@ovh.pl
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1783
Ronald S. Bultje rsbul...@gmail.com added the comment:
Configure line:
--enable-memalign-hack --enable-gpl --enable-nonfree --enable-libfaac
--enable-libx264 --enable-libmp3lame --enable-pthreads --extra-libs=-lx264
--disable-devices --disable-demuxers --enable-demuxer=pcm_s16le
--enable-demuxer
Ronald S. Bultje rsbul...@gmail.com added the comment:
I removed it, such checks do not belong in depacketizers anyway, and the check
is wrong since this can in theory be used for any Xiph payload, think of future
extensions for VP8, Speex, etc.
--
status: open - closed
substatus
Ronald S. Bultje rsbul...@gmail.com added the comment:
OK, closed as invalid then.
--
status: open - closed
substatus: needs_changes - invalid
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1849
Ronald S. Bultje rsbul...@gmail.com added the comment:
Ronald, what's your opinion on this?
If they're not using _open(), then they shouldn't use _close(). If they want to
use any _close(), then they need to use _open(), as you suggested.
av_global_network_init()
I don't think that's a good
Ronald S. Bultje rsbul...@gmail.com added the comment:
Michael, ping?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1740
Ronald S. Bultje rsbul...@gmail.com added the comment:
EULA.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue272
{\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf250
Ronald S. Bultje rsbul...@gmail.com added the comment:
I think this issue is now resolved.
Carl Eugen, can you confirm and close if OK?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1266
Ronald S. Bultje rsbul...@gmail.com added the comment:
They chose LGPL3.0, and that's fine. In the latest version, their configure flag
should be OK, I asked them to fix it. If it's not fixed, then we can always ask
them either here or by emailing the person directly.
As for spelling, Rui
Ronald S. Bultje rsbul...@gmail.com added the comment:
Yes, FFmpeg supports the RTSP protocol.
Without telling us what ip is, there's not much more we can do here.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
Looks OK with me. Carl Eugen, OK to close?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue488
Ronald S. Bultje rsbul...@gmail.com added the comment:
I'm not sure how relevant this is, because the software (AFAICS) is no longer
available for download...
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1625
Ronald S. Bultje rsbul...@gmail.com added the comment:
The offending binary is missing. Their current media player uses Adobe AIR, the
only thing is some antique source code (search for source.zip) that lacks a
binary.
That, by itself, is no GPL violation. So currently, they do not violate
Ronald S. Bultje rsbul...@gmail.com added the comment:
Hi,
On Wed, Feb 24, 2010 at 6:59 PM, Michael Niedermayer
iss...@roundup.ffmpeg.org wrote:
also i still doubt that there is no specific field for this address in the
existing specs
That one I can assure you there isn't, if you google
Ronald S. Bultje rsbul...@gmail.com added the comment:
Hi,
On Wed, Feb 24, 2010 at 6:17 PM, Michael Niedermayer
iss...@roundup.ffmpeg.org wrote:
Michael Niedermayer michae...@gmx.at added the comment:
On Wed, Feb 24, 2010 at 10:00:33PM +, Ronald S. Bultje wrote:
Verifying if an access
Ronald S. Bultje rsbul...@gmail.com added the comment:
Little bit more wordy: your recent versions of the software link a LGPL-version
of libavcodec/etc. into Mezzmo.exe. Reverse-engineering should be allowed on the
whole executable / running binary, not only the FFmpeg-parts of it.
I'd
Ronald S. Bultje rsbul...@gmail.com added the comment:
Reverse engineering (from a practical point of view) implicitely requires you to
load the whole of a running program into a debugger. I cannot merely load only
ffmpeg.dll into the debugger while leaving mezzmo.exe outside, gdb has
Ronald S. Bultje rsbul...@gmail.com added the comment:
It returns invalid request for me.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1653
Hi,
On Sun, Feb 28, 2010 at 3:55 PM, Martin Storsjö
iss...@roundup.ffmpeg.org wrote:
Setting st-need_parsing = AVSTREAM_PARSE_FULL; for the stream doesn't solve
the
issue.
Can you look into why this doesn't fix it? Is the parser screwing up?
I think your solution lies here.
Ronald
Ronald S. Bultje rsbul...@gmail.com added the comment:
the player might not even know about it, for example our
mov demuxer opens files behind its back based on urls stored
in the mov.
[..]
In the end, I'm still not sure I understand correctly, what exactly does this
patch enable
Ronald S. Bultje rsbul...@gmail.com added the comment:
this patch works with, you mean this patch fixes the issue
as described here?
I'd like somebody else to confirm before I close the issue.
Ping.
_
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
Verifying if an access is safe depends on knowing what is
accessed. truncating at 1024 bytes and at ? is very unexpected
behavior.
1024 is the length of AVFormatContext-filename, I can make this a define if you
prefer. No truncation
Ronald S. Bultje rsbul...@gmail.com added the comment:
this patch works with, you mean this patch fixes the issue as described here?
I'd like somebody else to confirm before I close the issue.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
no i was thinking of a file or playlist that had 2 references
the first pointing to another local downloaded file but when
truncated to 1024 or at ? pointing to some file it should not
point to the second pointing to a remote location
Ronald S. Bultje rsbul...@gmail.com added the comment:
do you think
something like
/tmp/fileone?nolongernotours
could be used as part of an exploit?
There may be situations where someone wants to open a file
through a user supplied filename (maybe some kind of link in
a mov file
Ronald S. Bultje rsbul...@gmail.com added the comment:
strncpy(filename_temp, filename, 1024);
I don't think strncpy() should be used. Either use strcpy, or use av_strlcpy()
(recommended). strncpy() has some corner-cases where it fails to NULL-terminate
the buffer
Ronald S. Bultje rsbul...@gmail.com added the comment:
Patch is fine with me. Michael, OK with you? You're file.c maintainer.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1740
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
access |= O_BINARY;
#endif
+
fd = open(filename, access, 0666);
Don't add newlines when not needed.
+if (fd == -1) {
+/* File open failed; process query string, if it exists */
+char *filename_temp
Ronald S. Bultje rsbul...@gmail.com added the comment:
Also,
+if ((qs = strchr(filename_temp, '?')) != NULL) {
The != NULL is not necessary.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Ronald S. Bultje rsbul...@gmail.com added the comment:
+char *qs;
+char filename_temp[1024];
Can be on one line.
+strncpy(filename_temp, filename, 1024);
+
Please add a whiteline between variable declarations and function calls. Also,
you can remove the whiteline below
Ronald S. Bultje rsbul...@gmail.com added the comment:
test.c:6: warning: suggest parentheses around assignment used as truth value
#include string.h
int
main()
{
const char *qs;
if (qs = strchr(test, '?'))
return 0;
return 1;
}
Adding () around it fixes the warning for me
Ronald S. Bultje rsbul...@gmail.com added the comment:
Jeremy, I think Michael means that you should copy the filename into a local
buffer before you remove the trailing '?...' part.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Ronald S. Bultje rsbul...@gmail.com added the comment:
Please test this patch, lacking any testcase and being too lazy to set up
ffserver myself right now. I'll do that if this doesn't work.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
I've had several (private) about this also, I was sort-of thinking of adding
chunked encoding support to FFserver, as in the attached (unfinished :-() patch.
Basically you just need to add chunkheader parsing and ffserver will work again
Ronald S. Bultje rsbul...@gmail.com added the comment:
I would first open the original filename, '?' is a valid filename character.
Only if it doesn't exist, try parsing it as a option string.
+while (*p != '\0') {
+if (*p == '?') {
+found_qstring = 1;
+break
Ronald S. Bultje rsbul...@gmail.com added the comment:
I think the relevant section is 8.2:
Although the probability of SSRC identifier collision is low, all RTP
implementations MUST be prepared to detect collisions and take the
appropriate actions to resolve them. If a source
Ronald S. Bultje rsbul...@gmail.com added the comment:
Patch attached, for clarity.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1713
_Index
Ronald S. Bultje rsbul...@gmail.com added the comment:
Fixed in r21461.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1713
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
Fixed in r21381.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1697
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
updated against SVN, now also prevents filling the control URL with *, which
is what some Windows servers give as control URL (it means: use the same control
URL as the input filename, i.e. s-filename). Alan's original patch did
Ronald S. Bultje rsbul...@gmail.com added the comment:
You're suggesting these are the only two options.
- people could be busy with other features and this could be lower on their TODO
list
- people might not be interested in doing it themselves, but still want it in
FFmpeg
- ...
I will work
Ronald S. Bultje rsbul...@gmail.com added the comment:
Ping, has the EULA been updated given Diego's suggestions?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue272
Ronald S. Bultje rsbul...@gmail.com added the comment:
Simplified version of Alan's patch.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1697
Ronald S. Bultje rsbul...@gmail.com added the comment:
The man 4 udp stuff I quoted earlier on IRC.
There's two questions here that are interesting.
1) UDP is - in ffmpeg - primarily used for RTP, which is point-to-point. It
makes no sense to provide the source IP to the client because we know
Ronald S. Bultje rsbul...@gmail.com added the comment:
Fixed in r21178.
--
status: open - closed
substatus: reproduced - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1658
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
Crasher fixed. Changing subject to reflect that the format is unsupported.
SDP:
sdp: v='0'.26 A-V: 0.000 aq=0KB vq=0KB sq=0B
sdp: o='- 1040309956 1040309956 IN IP4 10.72.0.135'
sdp: s='Helges Moerchenlied'
sdp: i='Helge
Ronald S. Bultje rsbul...@gmail.com added the comment:
Could you please post this file in upload.mplayerhq.hu?
/srv/smb/mp3z/comedy/Helge Schneider/moerchenlied_sure.ram
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Ronald S. Bultje rsbul...@gmail.com added the comment:
Between 8272 and 8550 used to be another comment, by Ramiro, posted Dec. 9th,
2009, it was removed for no good reason, so re-adding:
Ramiro Polla ram...@lisha.ufsc.br added the comment:
It seems this is where it downloads ffmpeg from:
http
Ronald S. Bultje rsbul...@gmail.com added the comment:
I'll email him.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue717
Ronald S. Bultje rsbul...@gmail.com added the comment:
EULA is fine now. I'll check the other software products soon. :-).
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue272
Ronald S. Bultje rsbul...@gmail.com added the comment:
The software download has been removed, presumably because of the recent legal
action against TPB in Europe.
This issue can probably be closed.
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
Hi,
On Fri, Dec 4, 2009 at 11:49 AM, Michael Niedermayer
iss...@roundup.ffmpeg.org wrote:
On Fri, Dec 04, 2009 at 04:14:40PM +, Carl Eugen Hoyos wrote:
[..]
Can we please create a new issue for this? I volunteer to contact
them
Ronald S. Bultje rsbul...@gmail.com added the comment:
Downloaded the file today 12/4/'09, 1:30 EST:
$ ls -la av*
-rw-r--r-- 1 ronaldbultje ronaldbultje 4231680 May 2 2008 avcodec-51.dll
-rw-r--r-- 1 ronaldbultje ronaldbultje40960 May 2 2008 avutil-49.dll
$ grep libx264_encoder
Ronald S. Bultje rsbul...@gmail.com added the comment:
Can someone translate the EULA into English?
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1587
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
Part 3:
This software is in Turkish Telekom's ownership of intellectual property law and
other laws of the Republic of Turkey and is protected by international law.
[..]
In addition, the Software can not say, can not create derivative
Ronald S. Bultje rsbul...@gmail.com added the comment:
I emailed their legal team.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1587
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
That license claim is not true. On SF, ffdshow claims to be GPL.
http://sourceforge.net/projects/ffdshow/. Where do they claim to be LGPL?
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
OK, let's take this easy, calm down, we're not the maffia and we're not gonna
shoot you. Now, first, take a good night sleep.
Second, you're a free project (as far as I can see), so we won't give you all
that hard a time. Calm down, relax
Ronald S. Bultje rsbul...@gmail.com added the comment:
@stanley: You should work together with these guys to get things done.
+1 - fully agree.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Ronald S. Bultje rsbul...@gmail.com added the comment:
I checked your latest. Minor problem in the EULA (not a violation, just a
problem):
This program contains
* libavcodec (libavcodec.dll)
* libavformat (libavformat.dll)
* libavutil (libavutil.dll)
from FFmpeg (),
[..]
under the GNU
New submission from Ronald S. Bultje rsbul...@gmail.com:
$subj.
The length argument could easily be folded into init_get_bits(a, b, THIS
ARGUMENT) and then BITS_LEFT() becomes an identical copy of get_bits_left().
--
messages: 7896
priority: normal
status: new
substatus: new
title
Ronald S. Bultje rsbul...@gmail.com added the comment:
Here's how it usually works:
1) we demand acknowledgement of (past violation). This is required, it is not
optional, and it is important. Regardless of the state of the current version
(it might even be compliant! who knows), past violations
Ronald S. Bultje rsbul...@gmail.com added the comment:
Huh?
http://anvsoft.com/download-photo-dvd-maker.html for example doesn't. are you
sure they're the same? I think they all violate FFmpeg license.
_
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
PhotoToDVD latest looks good on first sight. EULA looks good also. ConvertXToDVD
was no longer available so I couldn't check it. Please make it available
somewhere where we can permanently find it (e.g. upload.mplayerhq.hu).
Note
Ronald S. Bultje rsbul...@gmail.com added the comment:
That looks good from the web-point-of-view. What about people who received the
software through some other method, e.g. a cnet download, pre-installed, on a
CD, etc? You might want to add a pointer to that location in your software as
well
Ronald S. Bultje rsbul...@gmail.com added the comment:
Diego asked me to convey one more issue:
Your about dialog text is - by my reading of the LGPL - not sufficient (although
not too bad). I'd prefer if the about dialog actually carried something along
the line of ... FFmpeg [a great video
Ronald S. Bultje rsbul...@gmail.com added the comment:
EULA attached of latest version.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue272
Ronald S. Bultje rsbul...@gmail.com added the comment:
In-software credit is OK also. About dialog states:
This software uses portion of FFmpeg, a good video library. linkFFmpeg
information/link
I don't know what the link does because that doesn't work, but I assume that it
brings you
Ronald S. Bultje rsbul...@gmail.com added the comment:
Please stay off the priority. Stanley has been in violation and thus until we
reinstate his license, he remains in violation.
--
priority: wish - normal
_
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
Fixed differently by Kostya in r20178.
--
status: open - closed
substatus: open - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Ronald S. Bultje rsbul...@gmail.com added the comment:
They have at some point been in violation and they know it - they would thus
have to explicitely talk with us to get it re-enabled.
I'm tempted to throw this to the SFLC bunch since it's $$$. Anyone against
Ronald S. Bultje rsbul...@gmail.com added the comment:
I cannot reproduce:
$ ./ffplay ~/Desktop/10-YA\ BUDU\ SLAVIT.wma
FFplay version SVN-r19703, Copyright (c) 2003-2009 Fabrice Bellard, et al.
configuration: --disable-optimizations --disable-mmx
libavutil 50. 3. 0 / 50. 3. 0
Ronald S. Bultje rsbul...@gmail.com added the comment:
In that case, duplicate of 1055.
--
status: open - closed
substatus: reproduced - duplicate
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup
Ronald S. Bultje rsbul...@gmail.com added the comment:
Issue1236 has another sample file showing the same problem.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1055
_
New submission from Ronald S. Bultje rsbul...@gmail.com:
http://www.google.com/search?ie=UTF-8oe=UTF-8sourceid=navclientgfns=1q=ffmpeg+site%3Avirtualdj.com
suggests that they use FFmpeg and even acknowledge their use.
However, they are not presenting source, offering credits or showing
Ronald S. Bultje rsbul...@gmail.com added the comment:
- me (I suppose)
--
assignedto: - rbultje
nosy: +rbultje
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue786
Ronald S. Bultje rsbul...@gmail.com added the comment:
Changing priority back to what it should be so it doesn't show up on top of my
list.
--
priority: critical - normal
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Ronald S. Bultje rsbul...@gmail.com added the comment:
Clear violation of GPL + corporate payware - SFLC.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue723
Ronald S. Bultje rsbul...@gmail.com added the comment:
Same domain owner as issue 723:
8939 S. Sepulveda Blvd. #110 - 732
Westchester, CA 90045
Therefore, let's place them all together in one nice entry.
--
status: open - closed
substatus: reproduced - duplicate
Ronald S. Bultje rsbul...@gmail.com added the comment:
Registrant:
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
Registered through: GoDaddy.com, Inc. (http://www.godaddy.com)
Domain Name: ANY-DVD-CONVERTER.COM
Created
Ronald S. Bultje rsbul...@gmail.com added the comment:
Payware (iPhone part = $8) + GPL - SFLC.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1266
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
Passing stsd isn't going to make it remuxable to other codecs...
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1322
_
Ronald S. Bultje rsbul...@gmail.com added the comment:
argon, if you want I can simply forward this to our lawyers and they'll suck the
life out of you (and all your money with it). Keep your cool, please.
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
Also, term 2.3 (especially c/d, but also other parts) is not in accordance with
the LGPL:
2.3 You may not do any of the following yourself, or through any other third
party:
[..]
c. reverse engineer, decompile or disassemble the Software
Ronald S. Bultje rsbul...@gmail.com added the comment:
We do this in our free time, please be patient.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue455
Ronald S. Bultje rsbul...@gmail.com added the comment:
hi,
if your product is GPL, we are happy to help you. Simply come on IRC and we'll
try to assist you where you can. Basic rules:
- release all sources under GPL/LGPL (and no EULA saying otherwise)
- give proper credit
- send us patches
Ronald S. Bultje rsbul...@gmail.com added the comment:
Ask on the mailinglist (ffmpeg-devel) or IRC channel. Alternatively, if you
prefer discretion, email Diego or me (or anyone that you trust/like/whatever :-)
) privately and we can put you in touch with people that do contract work on
FFmpeg
Ronald S. Bultje rsbul...@gmail.com added the comment:
Don't close reports, this is for internal tracking unless you want to be on
shame forever.
--
status: closed - open
substatus: works_for_me - new
_
FFmpeg issue tracker iss
Ronald S. Bultje rsbul...@gmail.com added the comment:
Just to give an example, on your mozilla page, License:
https://addons.mozilla.org/en-US/firefox/addon/3006
Video DownloadHelper is provided AS IS, at no charge, without warranties as
to performance or merchantability
or any other
Ronald S. Bultje rsbul...@gmail.com added the comment:
Hi Michael,
Media Cell was moved to issue1241 - I'm certainly intending to go after them
first and foremost. I'll try to contact the TPB people and see what they have to
say.
FFmpeg
Ronald S. Bultje rsbul...@gmail.com added the comment:
Add topic.
--
topic: +(L)GPL violation
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue392
Ronald S. Bultje rsbul...@gmail.com added the comment:
From issue992:
http://www.h264encoder.com/ is a free application which encodes to h264
and the formats supported by x264. It does not mention any other
software or licenses, but installs h264decoder.dll, which contains lavc
and lavf
Ronald S. Bultje rsbul...@gmail.com added the comment:
Duplicate of issue787.
--
status: open - closed
substatus: open - duplicate
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue992
101 - 200 of 214 matches
Mail list logo