> case 1:
> use the hexdump -C SMM0005.rcv get:
> size skip (size - 4)
> ||
> VV
> 18 00 00 c5 05 00 00 00 4d f1 0a 11 00 e0 01 00
> 0010 00 d0 02 00 00 0c 0
On Mon, Oct 15, 2018 at 3:15 PM Jerome Borsboom
wrote:
>
> > case 1:
> > use the hexdump -C SMM0005.rcv get:
> > size skip (size - 4)
> > ||
> > VV
> > 18 00 00 c
Hi,
it looks like to me that the issue is still present.
source.mp4 is a vertical video from an iphone, with a 90degres rotation.
mediainfo source.mp4 | grep -i rot
Rotation : 90?
I run:
/usr/local/bin/ffmpeg -autorotate 0 -i ./source.mp4 -metadata:s:v:0
rotate
On Sun, Oct 14, 2018 at 10:24:22AM -0300, James Almer wrote:
> On 10/14/2018 9:59 AM, Michael Niedermayer wrote:
> > On Sun, Oct 14, 2018 at 01:29:53PM +0300, Jan Ekström wrote:
> >> On Sun, Oct 14, 2018 at 1:27 PM Jan Ekström wrote:
> >>>
> >>> On Sun, Oct 14, 2018 at 3:17 AM Michael Niedermayer
Hi Martin,
For my point of view, the AVFrame contains the colorspace for each frame,
which can be different (maybe not volunteer..).
The colorspace in AVCodecContext is the "pre-computed" colorspace, used to
generate the output file, as header/footer of wrappers can require
colorspace informations
2018-10-15 10:29 GMT+02:00, Gilles :
> it looks like to me that the issue is still present.
Which issue? Please fix the commit message accordingly.
Please do not top-post here, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffm
Hi,
the one in the first post: https://trac.ffmpeg.org/ticket/4560
Le lun. 15 oct. 2018 à 11:40, Carl Eugen Hoyos a
écrit :
> 2018-10-15 10:29 GMT+02:00, Gilles :
>
> > it looks like to me that the issue is still present.
>
> Which issue? Please fix the commit message accordingly.
>
> Please do
Le lun. 15 oct. 2018 à 11:24, Marc-Antoine ARNAUD <
arnaud.marcanto...@gmail.com> a écrit :
> Hi Martin,
>
> For my point of view, the AVFrame contains the colorspace for each frame,
> which can be different (maybe not volunteer..).
> The colorspace in AVCodecContext is the "pre-computed" colorspa
2018-10-15 12:11 GMT+02:00, Gilles :
> the one in the first post: https://trac.ffmpeg.org/ticket/4560
Again:
This ticket was fixed years ago and is not reproducible with
current FFmpeg git head.
Please stop top-posting here, Carl Eugen
___
ffmpeg-devel
Oh my bad, I had 2 tickets on this subject and the one that is still opened
is:
https://trac.ffmpeg.org/ticket/6370
Anyway, the issue is still around
Le lun. 15 oct. 2018 à 13:27, Carl Eugen Hoyos a
écrit :
> 2018-10-15 12:11 GMT+02:00, Gilles :
>
> > the one in the first post: https://tra
From: Josh de Kock
This test ensures that you are able to send N number of slice NALUs in slice
threaded mode to be decoded simultaneously
---
Tested on Linux 32/64, MinGW + WINE 32/64.
tests/api/Makefile | 1 +
tests/api/api-h264-slice-test.c | 216 ++
test
case 1:
use the hexdump -C SMM0005.rcv get:
size skip (size - 4)
||
VV
18 00 00 c5 05 00 00 00 4d f1 0a 11 00 e0 01 00
0010 00 d0 02 00 00 0c 00 00 00 88 13
v4: - add size check to avoid overread
v3: - add size check when probe as Michael's comments.
- update commit msg
- for Jerome's comments, I don't find a way to adjusted the handle for
"0x000c"
v2: - split the patch (Carl Eugen Hoyos's comments).
Jun Zhao (2):
lavf/vc1test: fix vc1t
rcv is commonly used as extension for vc1 test stream files.
Signed-off-by: Jun Zhao
---
libavformat/vc1test.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/libavformat/vc1test.c b/libavformat/vc1test.c
index 2427660..8aaad93 100644
--- a/libavformat/vc1test.c
+++ b/li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Just a quick question. Did I do everything right with the patch
submission? I haven't subitted anything for a very long time here, so
I hope the procedure hasn't changed.
Cheers,
K. C.
On 2018-10-15 00:49, Helmut K. C. Tessarek wrote:
> --- src/d
On Thu, Oct 11, 2018 at 5:28 PM Jan Ekström wrote:
> On Thu, Oct 11, 2018 at 10:58 PM Alex Sukhanov
> wrote:
> >
> > Hi Mark,
> >
> > at Google we have some old service which is still running and it works
> only
> > with the IVF container. It would be great if ffmpeg could generate such
> > vide
On 10/15/2018 1:33 PM, Helmut K. C. Tessarek wrote:
> Just a quick question. Did I do everything right with the patch
> submission? I haven't subitted anything for a very long time here, so
> I hope the procedure hasn't changed.
>
> Cheers,
> K. C.
It's fine, but maybe instead of "doc" use "dow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-10-15 14:27, James Almer wrote:
> It's fine, but maybe instead of "doc" use "download" for the
> commit message since that's the page you're updating.
Thanks for the reply. Shall I send the patch again with a different
commit message?
The re
Anssi Hannula kirjoitti 2018-10-15 00:07:
---
Unfortunately I haven't really had the time lately to maintain the HLS
demuxer properly and I don't see that changing in the near future. So I
intend to apply this removal tomorrow.
If anyone is interested in taking over, please do :)
I'll continue
Flush the buffered data in libmfx before video param reinit
in case the frames drop.
Cache the first frame causing the reinit and decode zero-size
pkt to flush the buffered pkt before reinit. After all the
buffered pkts being flushed, resume to reinit and decode.
Fix the issue in ticket #7399.
M
---
src/download | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/download b/src/download
index 0bda5a0..40f4706 100644
--- a/src/download
+++ b/src/download
@@ -95,7 +95,7 @@
https://evermeet.cx/ffmpeg/";>
-Static builds for OS
> 在 2018年10月11日，下午4:56，Charles Liu 写道：
>
> In fmp4 & sub-range mode, the output's duration always smaller than expected,
> because the size of the last #EXT-X-BYTERANGE is too small.
>
> Signed-off-by: Charles Liu
> ---
> libavformat/hlsenc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 delet
22 matches
Mail list logo
