---
After these patches, one can do a build for Windows Phone/ARM with
as little configure flags as this:
--toolchain=msvc --target-os=win32 --enable-cross-compile --arch=arm
--cpu=armv7-a --extra-cflags='-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP'
---
configure | 14 ++
1 file changed,
On Sun, 26 Jul 2015, Martin Storsjö wrote:
---
After these patches, one can do a build for Windows Phone/ARM with
as little configure flags as this:
--toolchain=msvc --target-os=win32 --enable-cross-compile --arch=arm
--cpu=armv7-a --extra-cflags='-DWINAPI_FAMILY=WINAPI_FAMILY_PHON
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
+# found in the SDK headers by default. (Alternatively, we could force
+# _WIN32_WINNT to 0x0602 in that case.)
Why don't you force to 0x0603 in those partition cases?
Wouldn't that
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index 446a786..77eb8f5 100755
--- a/configure
+++ b/configure
@@ -4007,6 +4007,7 @@ elif enabled alpha; then
elif enabled
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
The static CRT (libcmt.lib, as used by default or with -MT) doesn't
work when targeting these API subsets.
Only do this if no cflags for CRT selection have been specified,
to allow users to override this de
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
This isn't necessary any longer on MSVC 2013.
I agree with the patch, but IIRC, it can still fail on MSVC 2013, if you
don't have the latest version (4).
Hmm, possibly, I might have used that v
On Sun, 26 Jul 2015, Hendrik Leppkes wrote:
On Sun, Jul 26, 2015 at 11:57 AM, Martin Storsjö wrote:
If _WIN32_WINNT is unset, we force it to a new enough value to
make sure the necessary definitions are visible.
When targeting Windows Phone or Windows RT, _WIN32_WINNT should
be at least
On Sun, 26 Jul 2015, Steve Lhomme wrote:
On Sun, Jul 26, 2015 at 11:23 AM, Martin Storsjö wrote:
On Sun, 26 Jul 2015, Martin Storsjö wrote:
From: Steve Lhomme
The struct definitions in dxva.h, which are necessary in order to
actually use d3d11va, are hidden when WINAPI_FAMILY targets
On Sun, 26 Jul 2015, Steve Lhomme wrote:
The struct definitions in dxva.h, which are necessary in order to
actually use d3d11va, are hidden when WINAPI_FAMILY targets Windows Phone
or WindowsRT.
Building with WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP is disallowed
when targeting ARM. ("Compiling
On Sun, 26 Jul 2015, Steve Lhomme wrote:
On Sun, Jul 26, 2015 at 12:00 PM, Martin Storsjö wrote:
On Sun, 26 Jul 2015, Martin Storsjö wrote:
---
After these patches, one can do a build for Windows Phone/ARM with
as little configure flags as this:
--toolchain=msvc --target-os=win32 --enable
On Sun, 26 Jul 2015, Steve Lhomme wrote:
On Sun, Jul 26, 2015 at 12:58 PM, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
+# found in the SDK headers by default. (Alternatively, we could force
+# _WIN32_WINNT to 0x0602 in that case.)
Why don't you for
On Sun, 26 Jul 2015, Steve Lhomme wrote:
On Sun, Jul 26, 2015 at 11:57 AM, Martin Storsjö wrote:
This is only necessary on MSVC 2010/2012 (and possibly on some
ICL versions). This both avoids an extra hack on newer MSVC
versions, and better documents what the extra compiler option
is used for
On Sun, 26 Jul 2015, Martin Storsjö wrote:
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index 446a786..77eb8f5 100755
--- a/configure
+++ b/configure
@@ -4007,6
On Sun, 26 Jul 2015, Martin Storsjö wrote:
On Sun, 26 Jul 2015, Steve Lhomme wrote:
The struct definitions in dxva.h, which are necessary in order to
actually use d3d11va, are hidden when WINAPI_FAMILY targets Windows Phone
or WindowsRT.
Building with WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP
---
doc/platform.texi | 6 --
1 file changed, 6 deletions(-)
diff --git a/doc/platform.texi b/doc/platform.texi
index edd7577..07c8575 100644
--- a/doc/platform.texi
+++ b/doc/platform.texi
@@ -168,12 +168,6 @@ Notes:
@itemize
-@item It is possible that coreutils' @code{link.exe} conflic
If _WIN32_WINNT is unset, we force it to a new enough value to
make sure the necessary definitions are visible.
When targeting Windows Phone or Windows RT, _WIN32_WINNT should
be at least 0x0602 - otherwise the windows headers themselves
can cause errors (which technically are bugs in the headers)
---
Checking if _M_ARMT is defined, instead of checking _M_ARM >= 7.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index d37341e..898205b 100755
--- a/configure
+++ b/configure
@@ -4007,6 +4007,7 @@ elif enabled alpha; then
elif enabled arm; then
+
On Sun, 26 Jul 2015, Janne Grunau wrote:
On 2015-07-26 23:13:15 +0300, Martin Storsjö wrote:
---
Checking if _M_ARMT is defined, instead of checking _M_ARM >= 7.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index d37341e..898205b 100755
--
This simplifies recently added code from 5fd553d31.
---
configure | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configure b/configure
index 215f5aa..dfab84d 100755
--- a/configure
+++ b/configure
@@ -4749,8 +4749,7 @@ EOF
fi
for pfx in "" host_; do
-pfx_no_=${pfx%_}
On Mon, 27 Jul 2015, Janne Grunau wrote:
On 2015-07-26 12:57:57 +0300, Martin Storsjö wrote:
This isn't necessary on MSVC 2015 any longer.
---
configure | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index b67c4b5..ab174f2 100755
On Sun, 26 Jul 2015, Martin Storsjö wrote:
If _WIN32_WINNT is unset, we force it to a new enough value to
make sure the necessary definitions are visible.
When targeting Windows Phone or Windows RT, _WIN32_WINNT should
be at least 0x0602 - otherwise the windows headers themselves
can cause
On Sun, 26 Jul 2015, Martin Storsjö wrote:
On Sun, 26 Jul 2015, Jean-Baptiste Kempf wrote:
On 26 Jul, Martin Storsjö wrote :
The static CRT (libcmt.lib, as used by default or with -MT) doesn't
work when targeting these API subsets.
Only do this if no cflags for CRT selection have
On Fri, 24 Jul 2015, Luca Barbato wrote:
Make possible to send the custom headers and override the user agent.
Reported-by: BenWonder
---
libavformat/hls.c | 90 ++-
1 file changed, 83 insertions(+), 7 deletions(-)
diff --git a/libavformat/hls
On Mon, 27 Jul 2015, James Almer wrote:
This set aims at making the API of these four modules more consistent with
the rest of libavutil crypto stuff by adding alloc functions as well as
making the contexts opaque starting with the next lavu major version.
The last three patches are untested as
On Tue, 28 Jul 2015, Luca Barbato wrote:
On 28/07/15 19:07, Martin Storsjö wrote:
Umm, no.
What happens if one of the options isn't found? av_opt_get will return
an error, and the HLS demuxer will refuse to work, even though things
are just fine. Keep in mind that the HLS demuxer works
On Wed, 29 Jul 2015, Luca Barbato wrote:
Make possible to send the custom headers and override the user agent.
Reported-by: BenWonder
---
Kept a single dictionary and grouped the open functions as Martin suggested.
libavformat/hls.c | 91 +++
On Tue, 28 Jul 2015, James Almer wrote:
Signed-off-by: James Almer
---
libavutil/hmac.c | 31 ++-
libavutil/hmac.h | 2 ++
2 files changed, 28 insertions(+), 5 deletions(-)
Ok with me
// Martin
___
libav-devel mailing lis
On Tue, 28 Jul 2015, James Almer wrote:
Also replace custom tests for MD5 with those published in RFC 2202
Signed-off-by: James Almer
---
libavutil/hmac.c| 46 --
tests/ref/fate/hmac | 20 +---
2 files changed, 53 insertions(+), 13
On Wed, 29 Jul 2015, James Almer wrote:
Signed-off-by: James Almer
---
libavformat/rtmp.h | 3 ---
libavformat/rtmpproto.c | 39 ++-
2 files changed, 10 insertions(+), 32 deletions(-)
Ok
// Martin
___
libav-d
configure does check for isatty, and checkasm properly checks
HAVE_ISATTY, but on some platforms (e.g. WinRT), io.h needs to be
included for isatty to be available.
---
tests/checkasm/checkasm.c | 4
1 file changed, 4 insertions(+)
diff --git a/tests/checkasm/checkasm.c b/tests/checkasm/chec
On Thu, 30 Jul 2015, James Almer wrote:
Signed-off-by: James Almer
---
libavformat/rtmpproto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/rtmpproto.c b/libavformat/rtmpproto.c
index 1db7495..ec4b0e7 100644
--- a/libavformat/rtmpproto.c
+++ b/libavformat/rtmpp
On Thu, 30 Jul 2015, James Almer wrote:
Signed-off-by: James Almer
---
Forgot about this, my bad.
doc/APIchanges | 3 +++
libavutil/version.h | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
Ok
// Martin
___
libav-devel mailing list
liba
On Wed, 21 Jan 2015, Luca Barbato wrote:
On 21/01/15 14:41, Martin Storsjö wrote:
Allow $ as character anywhere within normal RTSP replies - both
within the lines, and as the first character of RTSP header lines.
(The existing old comment indicated that an inline packet could
start at any line
On Thu, 30 Jul 2015, Martin Storsjö wrote:
On Wed, 21 Jan 2015, Luca Barbato wrote:
On 21/01/15 14:41, Martin Storsjö wrote:
Allow $ as character anywhere within normal RTSP replies - both
within the lines, and as the first character of RTSP header lines.
(The existing old comment indicated
On Mon, 3 Aug 2015, Luca Barbato wrote:
Makes easier spot typos while passing --cc --as --ld to configure.
---
configure | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configure b/configure
index 482be43..056147e 100755
--- a/configure
+++ b/configure
@@ -2932,6 +2932,9 @@ probe_cc(){
On Mon, 3 Aug 2015, Luca Barbato wrote:
On 03/08/15 13:31, Luca Barbato wrote:
On 03/08/15 12:44, Shiz wrote:
On Xcode's clang on OS X, $cc --version will output a 'Configured with:'
line to stderr, which clobbers the configure script output. As this line
serves no further purpose, it should b
On Mon, 3 Aug 2015, Luca Barbato wrote:
---
libavutil/avstring.c | 5 +++--
libavutil/avstring.h | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
This breaks const-correctness when using these functions on non-const
input data. The standard C functions strstr and similar have the sam
On Wed, 5 Aug 2015, Luca Barbato wrote:
From: Jake Sebastian-Jones
And report why it fails.
Signed-off-by: Luca Barbato
---
You can write comments to patches below the --- marker,
I use git send-email --annotate to do that.
Here your amended patch I changed the commit title and message
acc
On Sat, 8 Aug 2015, Andreas Cadhalpun wrote:
It is used in libavutil/eval.c.
Is there any other user of this, anywhere?
The use within libavutil is only transitionary and will/should be removed
at the same time when this public symbol is removed.
As Hendrik said, public data symbols are pr
On Sat, 8 Aug 2015, Martin Storsjö wrote:
On Sat, 8 Aug 2015, Andreas Cadhalpun wrote:
It is used in libavutil/eval.c.
Is there any other user of this, anywhere?
Ok, so after reading older mails, I see that mplayer and mplayer2 are the
ones affected by this.
Anyway, the agreed upon
On Sat, 8 Aug 2015, Andreas Cadhalpun wrote:
On 08.08.2015 18:40, Martin Storsjö wrote:
As Hendrik said, public data symbols are problematic from a portability point
of view
(they behave differently than public functions in DLLs and require jumping
through
extra hoops, which we've chose
This fixes crashes with pathological cases when trying to write
a sidx index (via the -movflags faststart option, in combination
with fragmenting options), when no fragments actually have been
written. (This is possible if the empty_moov flag isn't used,
so that all actual packet data is written in
The same field is also used for writing the sidx index header,
for fragmented files, when the faststart flag is used.
---
libavformat/movenc.c | 14 +++---
libavformat/movenc.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc
For fragmented files with non-empty moov, with a fragment index
(sidx), place the index after the initial moov/mdat pair.
Previously, for this pathological case, the index was written
at the start of the file.
---
libavformat/movenc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavfo
The double meaning of the faststart flag (moving a moov atom
to the start of files, making them streamable, for non-fragmented
files, vs inserting a global sidx index at the start of files
for fragmented files) is confusing - see 40ed1cbf1 for
explanation of its origins.
Since the second meaning o
On Mon, 10 Aug 2015, Luca Barbato wrote:
On 09/08/15 21:45, Martin Storsjö wrote:
This fixes crashes with pathological cases when trying to write
a sidx index (via the -movflags faststart option, in combination
with fragmenting options), when no fragments actually have been
written. (This is
On Tue, 11 Aug 2015, Anton Khirnov wrote:
Quoting Luca Barbato (2015-08-03 22:51:50)
The resulting mapped array is used as non-const.
---
libavutil/samplefmt.c | 2 +-
libavutil/samplefmt.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavutil/samplefmt.c b/libavutil
The current automatic detection might not always succeed.
On Xcode 7 with -fembed-bitcode, the current detection fails.
In this case, the detection is to try to compile and link a file
containing '__asm__ (".eabi_attribute 28, 1");'
With -fembed-bitcode, the assembler does print an error, but the
On Wed, 12 Aug 2015, Luca Barbato wrote:
On 12/08/15 12:12, Martin Storsjö wrote:
The current automatic detection might not always succeed.
On Xcode 7 with -fembed-bitcode, the current detection fails.
In this case, the detection is to try to compile and link a file
containing '__
On Sun, 9 Aug 2015, Martin Storsjö wrote:
On Sat, 8 Aug 2015, Andreas Cadhalpun wrote:
On 08.08.2015 18:40, Martin Storsjö wrote:
As Hendrik said, public data symbols are problematic from a portability
point of view
(they behave differently than public functions in DLLs and require jumping
Don't try to detect the float ABI by checking at the toolchain
name or by trying to assemble and link files with eabi_attributes.
This fixes the float ABI detection when building using clang
with -fembed-bitcode, where the current eabi_attributes check
accidentally passes.
CC: libav-sta...@libav.
Previously most of the error paths leaked.
Also add FF_CODEC_CAP_INIT_THREADSAFE while adding caps_internal;
this decoder wrapper doesn't have any static data that is initialized.
---
Not CCing this to stable, since FF_CODEC_CAP_INIT_CLEANUP isn't
in stable.
---
libavcodec/libfdk-aacdec.c | 17 ++
In the latest version of fdk-aac, the decoder can output up to 8
channels; take this into account when preallocating buffers that
need to fit the output from any packet.
CC: libav-sta...@libav.org
---
libavcodec/libfdk-aacdec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/l
For ADTS streams, the output format (number of channels, frame size)
can change at any point (with the latest version of fdk-aac, the decoder
seems to change format after a handful of frames, not outputting the
right format immediately, for cases that worked fine with the earlier
version of the lib
On Fri, 14 Aug 2015, Luca Barbato wrote:
On 14/08/15 10:36, Martin Storsjö wrote:
For ADTS streams, the output format (number of channels, frame size)
can change at any point (with the latest version of fdk-aac, the decoder
seems to change format after a handful of frames, not outputting the
On Fri, 14 Aug 2015, Luca Barbato wrote:
On 14/08/15 13:21, Martin Storsjö wrote:
On Fri, 14 Aug 2015, Luca Barbato wrote:
On 14/08/15 10:36, Martin Storsjö wrote:
For ADTS streams, the output format (number of channels, frame size)
can change at any point (with the latest version of fdk
On Fri, 14 Aug 2015, Luca Barbato wrote:
Use only the video packets to compute the duration the video
track is present.
---
libavformat/hlsenc.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
Why is this "correctly", what issue does it fix?
// Martin
_
On Fri, 14 Aug 2015, Luca Barbato wrote:
On 14/08/15 16:06, Martin Storsjö wrote:
Nope, and more problematically; if the lib suddenly decides to decode a
whole lot more channels, it will overflow the buffer we've allocated
(and it ignores the buf_size parameter that we give it).
I
On Fri, 14 Aug 2015, Luca Barbato wrote:
On 14/08/15 18:45, Martin Storsjö wrote:
On Fri, 14 Aug 2015, Luca Barbato wrote:
Use only the video packets to compute the duration the video
track is present.
---
libavformat/hlsenc.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions
On Fri, 14 Aug 2015, Luca Barbato wrote:
Do not risk mixing different timebases.
CC: libav-sta...@libav.org
---
Now addressing the core issue, possibly properly.
Thanks a lot Martin!
libavformat/hlsenc.c | 28 +++-
1 file changed, 15 insertions(+), 13 deletions(-)
Loo
On Thu, 27 Aug 2015, Alexandra Hájková wrote:
the error message if there is some error. MOV has its header
at the end of the file so the output will be corrupted if
writing to the output will fail before header is written.
This isn't true for all mov modes, only the non-fragmented ones.
Bug-
On Thu, 27 Aug 2015, Sean McGovern wrote:
Bug-Id: 881
CC: libav-sta...@libav.org
---
libavformat/mux.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/mux.c b/libavformat/mux.c
index 3cff264..cae8f19 100644
--- a/libavformat/mux.c
+++ b/libavformat/mux.c
@@ -591,6 +591,9 @@
On Sat, 29 Aug 2015, Luca Barbato wrote:
From: Federico Tomassetti
It is useful to support an eventual staging branch and to have a first
layer fate-check on github pull requests.
---
Now updated to be much faster, thanks again to Federico for his
effort.
.travis.yml | 19 +++
On Sat, 29 Aug 2015, Vittorio Giovara wrote:
---
Related to
./libav/tools/ismindex.c:378:29: warning: absolute value
function 'abs' given an argument of type 'long long' but has parameter of
type 'int' which may cause truncation of value [-Wabsolute-value]
if (duration > 0 && a
On Sat, 29 Aug 2015, Vittorio Giovara wrote:
---
libavcodec/libfdk-aacdec.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/libavcodec/libfdk-aacdec.c b/libavcodec/libfdk-aacdec.c
index 5ac8fb7..cdf7a05 100644
--- a/libavcodec/libfdk-aacdec.c
+++ b/libavcodec/libfdk-aacdec.c
@@ -209,7 +209,6 @
On Sat, 29 Aug 2015, Vittorio Giovara wrote:
---
Related to
In file included from libavutil/des.h.c:1:
/Users/GiovaraV/src/libav/libavutil/des.h:33:5: warning:
'FF_API_CRYPTO_CONTEXT' is not defined, evaluates to 0 [-Wundef]
#if FF_API_CRYPTO_CONTEXT
^
Vittorio
libavutil/des.h |
On Sun, 30 Aug 2015, Vittorio Giovara wrote:
On Sat, Aug 29, 2015 at 10:33 PM, Martin Storsjö wrote:
On Sat, 29 Aug 2015, Vittorio Giovara wrote:
---
Related to
In file included from libavutil/des.h.c:1:
/Users/GiovaraV/src/libav/libavutil/des.h:33:5: warning:
'FF_API_CRYPTO_CO
The previous restriction was partially designed to fix certain
(broken) samples from bug 215. There should be no restriction on the
number of keyframes per fragment or trun.
The spec suggests that all frames lacking MOV_FRAG_SAMPLE_FLAG_IS_NON_SYNC
are key frames, but we require the flag MOV_FRAG_
On Mon, 7 Sep 2015, Anton Khirnov wrote:
Quoting Martin Storsjö (2015-09-05 19:33:39)
The previous restriction was partially designed to fix certain
(broken) samples from bug 215. There should be no restriction on the
number of keyframes per fragment or trun.
So what happens now to those
Since the actual max length of the jitter buffer is restricted by
max_delay, this shouldn't harm the overall latency (assuming that
max_delay is set properly), while allowing packet reordering with
a larger number of packets (which may be required with high bitrate
video).
---
libavformat/rtpdec.h
On Mon, 14 Sep 2015, Luca Barbato wrote:
On 14/09/15 13:49, Martin Storsjö wrote:
Since the actual max length of the jitter buffer is restricted by
max_delay, this shouldn't harm the overall latency (assuming that
max_delay is set properly), while allowing packet reordering with
a l
On Mon, 14 Sep 2015, Eloi BAIL wrote:
This commit adds an error trace when jitter buffer
is full. It helps to understand leading decoding issues.
Signed-off-by: Eloi BAIL
---
libavformat/rtpdec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/rtpdec.c b/libavformat/rtpdec.c
On Tue, 15 Sep 2015, Luca Barbato wrote:
On 14/09/15 22:29, Eloi BAIL wrote:
This commit print as AV_LOG_INFO the jitter buffer
size. It might be the default value or the value set by application.
Signed-off-by: Eloi BAIL
---
libavformat/rtpdec.c | 4
1 file changed, 4 insertions(+)
On Tue, 15 Sep 2015, Alexandra Hájková wrote:
to make dca_decode_frame more readable
---
libavcodec/dcadec.c | 118
1 file changed, 64 insertions(+), 54 deletions(-)
diff --git a/libavcodec/dcadec.c b/libavcodec/dcadec.c
index abf762d..43765cc
On Tue, 15 Sep 2015, Martin Storsjö wrote:
On Tue, 15 Sep 2015, Alexandra Hájková wrote:
to make dca_decode_frame more readable
---
libavcodec/dcadec.c | 118
1 file changed, 64 insertions(+), 54 deletions(-)
diff --git a/libavcodec
On Tue, 15 Sep 2015, Eloi BAIL wrote:
This commit adds a warning trace when jitter buffer
is full. It helps to understand leading decoding issues.
Signed-off-by: Eloi BAIL
---
libavformat/rtpdec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavformat/rtpdec.c b/libavformat/rtpdec.c
On Tue, 15 Sep 2015, Luca Barbato wrote:
On 15/09/15 17:38, Eloi BAIL wrote:
This patchset adds information about jitter buffer used in rtpdec.
The first patch prints as warning when jitter buffer is full.
The second patch prints as verbose jitter buffer size set by default in
libav headers or
On Wed, 16 Sep 2015, Luca Barbato wrote:
And avoid a memory leak.
---
I need to doublecheck what happens to buf.
If we don't do *bufptr, the caller still owns the buffer (and it isn't
leaked).
So this seems fine to me. In practice it doesn't make much difference
though since the return va
This allows changing the log level on the fly at any time.
This causes all messages to actually be formatted within OpenH264
(OpenH264 only snprintf formats the log messages that actually
are going to be printed, just like av_log), even ones that will
be discarded by the libav log level. This coul
enh264 log level. This
log level, and a message logging function that invokes av_log() to
actually log messages, are then set on the encoder.
This contains further changes by Michael Niedermayer and
Martin Storsjö.
---
In addition to the cleanups done by Michael, I further fixed the
coding style to
On Wed, 23 Sep 2015, Derek Buitenhuis wrote:
There's no reason this should be required.
Signed-off-by: Derek Buitenhuis
---
As far as I know, anyway.
---
libavformat/movenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index ee
On Wed, 23 Sep 2015, Martin Storsjö wrote:
This allows changing the log level on the fly at any time.
This causes all messages to actually be formatted within OpenH264
(OpenH264 only snprintf formats the log messages that actually
are going to be printed, just like av_log), even ones that will
On Mon, 28 Sep 2015, Anton Khirnov wrote:
Quoting Martin Storsjö (2015-09-23 11:18:15)
This allows changing the log level on the fly at any time.
This causes all messages to actually be formatted within OpenH264
(OpenH264 only snprintf formats the log messages that actually
are going to be
On Wed, 30 Sep 2015, Sean McGovern wrote:
Currently, if I want to build shared libraries with suncc, I can complete
the build from the following command line:
./configure --disable-static --enable-shared --cc='suncc -m64'
--disable-debug
If I remove --disable-debug, it complains about undefine
On Thu, 1 Oct 2015, Martin Storsjö wrote:
On Wed, 30 Sep 2015, Sean McGovern wrote:
Currently, if I want to build shared libraries with suncc, I can complete
the build from the following command line:
./configure --disable-static --enable-shared --cc='suncc -m64'
--disable-debug
I
From: Michael Niedermayer
In one case it was written as zero, one case left it uninitialized,
missed the 11 bytes for the flv header.
---
libavformat/rtmpproto.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libavformat/rtmpproto.c b/libavformat/rtmpproto.c
index ec4
From: Carl Eugen Hoyos
Some overly strict implementations require this, even though it
technically is incorrect according to the spec.
In practice many other implementations seem to be using quotes here,
including cURL.
---
libavformat/httpauth.c | 5 -
1 file changed, 4 insertions(+), 1 de
From: Andrey Utkin
This fixes access to Grandstream cameras, which return 401 to ffmpeg
otherwise.
VLC sends Authorization: header with spaces between parameters, and it
is known to work with Grandstream devices and broad range of other HTTP
and RTSP servers, so author considers switching to such
On Tue, 13 Oct 2015, Hendrik Leppkes wrote:
On Tue, Oct 13, 2015 at 11:56 AM, Christophe Gisquet
wrote:
Hi
2015-10-06 12:41 GMT+02:00 Hendrik Leppkes :
+static av_unused int pthread_once(pthread_once_t *once_control, void
(*init_routine)(void))
[...]
+MemoryBarrier();
Th
On Tue, 13 Oct 2015, Luca Barbato wrote:
From: Michael Niedermayer
In one case it was written as zero, one case left it uninitialized,
missed the 11 bytes for the flv header.
Signed-off-by: Luca Barbato
---
There is an handy define, let's not add magic numbers when there.
Sure
// Martin
On Tue, 13 Oct 2015, Rémi Denis-Courmont wrote:
Le 2015-10-13 12:44, Martin Storsjö a écrit :
From: Carl Eugen Hoyos
Some overly strict implementations require this, even though it
technically is incorrect according to the spec.
That's not overly strict, that's just plain brok
This also makes sure that a fragmented file without the empty_moov
flag (i.e. with a non-empty initial moov fragment) actually gets
written, if some of the tracks turn out to not have any samples.
---
libavformat/movenc.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff
Some RTSP servers ("HiIpcam/V100R003 VodServer/1.0.0") respond to
our keepalive GET_PARAMETER request by a truncated RTSP header
(lacking the final empty line to indicate a complete response
header). Prior to 764ec70149, this worked just fine since we
reacted to the $ as interleaved packet indicato
On Tue, 27 Oct 2015, Luca Barbato wrote:
The end user reading 'wrapped_avframe' would be otherwise puzzled.
Reported-By: Daemon404
---
libavcodec/wrapped_avframe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Please use proper realnames in references in commit messages, where easily
This allows enabling the frame skipping, which is required for the
encoder to properly hit the target bitrate.
---
libavcodec/libopenh264enc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c
index 1553b6d..302d20e 100
---
libavcodec/libopenh264enc.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c
index 302d20e..7147715 100644
--- a/libavcodec/libopenh264enc.c
+++ b/libavcodec/libopenh264enc.c
@@ -39,6 +39,7 @@ typedef struct SVCContext {
cha
This allows enabling the frame skipping, which is required for the
encoder to properly hit the target bitrate.
---
Renamed the option to allow_skip_frames, to avoid potential
confusion with the similarly named AVCodecContext option skip_frame,
as pointed out by Clément.
---
libavcodec/libopenh264e
From: Clément Gregoire
On systems lacking getservbyport, struct servent might not be defined,
causing a compilation error when trying to access its member s_name
(ent->s_name).
There is no point in keeping the if(ent) branch when getservbyport is not
available.
Signed-off-by: Clément Grégoire
On Wed, 28 Oct 2015, Vittorio Giovara wrote:
On Wed, Oct 28, 2015 at 4:05 PM, Luca Barbato wrote:
Signed-off-by: Vittorio Giovara
---
libavcodec/avcodec.h | 6 ++
libavcodec/mpegvideo_enc.c | 8
libavcodec/version.h | 3 +++
3 files changed, 17 insertions(+)
amend
This silences warnings like this one:
libavformat/file.c(62) : warning C4996: 'read': The POSIX name for this
item is deprecated. Instead, use the ISO C++ conformant name: _read.
See online help for details.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configur
501 - 600 of 6480 matches
Mail list logo
