This allows user set hw_device_ctx instead of hw_frames_ctx for QSV
decoders, hence we may remove the ad-hoc libmfx setup code from FFmpeg.
"-hwaccel_output_format format" is applied to QSV decoders after
removing the ad-hoc libmfx code. To keep compatibility with old
commandlines, the default for
---
doc/examples/qsvdec.c | 45 +--
1 file changed, 9 insertions(+), 36 deletions(-)
diff --git a/doc/examples/qsvdec.c b/doc/examples/qsvdec.c
index 7415eefca5..571d868f93 100644
--- a/doc/examples/qsvdec.c
+++ b/doc/examples/qsvdec.c
@@ -44,38 +44,10 @@
> -原始邮件-
> 发件人: "Jiaxun Yang"
> 发送时间: 2021-07-29 14:32:35 (星期四)
> 收件人: ffmpeg-devel@ffmpeg.org
> 抄送: yinshiyou...@loongson.cn, "Jiaxun Yang"
> 主题: [PATCH] avcodec/mips: Support old style mmi instruction mnemonics
>
> Loongson had renamed serval instruction mnemonics to distinguish
> inte
On 2021-07-29 02:33, Michael Niedermayer wrote:
On Wed, Jul 28, 2021 at 09:56:35AM +0530, Gyan Doshi wrote:
---
doc/bitstream_filters.texi | 64 ---
libavcodec/noise_bsf.c | 161 +
tests/fate/matroska.mak| 2 +-
3 files changed,
James Almer:
> On 7/28/2021 7:43 PM, Andreas Rheinhardt wrote:
>> James Almer:
>>> Since we can't blindly trust the keyframe flag in packets and assume its
>>> contents are a valid Sync Sample, do some basic bitstream parsing to
>>> build the
>>> Sync Sample table in addition to a Random Access Rec
在2021年7月29日七月 下午5:29，yinshiyou...@loongson.cn写道：
> > -原始邮件-
> > 发件人: "Jiaxun Yang"
> > 发送时间: 2021-07-29 14:32:35 (星期四)
> > 收件人: ffmpeg-devel@ffmpeg.org
> > 抄送: yinshiyou...@loongson.cn, "Jiaxun Yang"
> > 主题: [PATCH] avcodec/mips: Support old style mmi instruction mnemonics
> >
> > Loon
Nicolas George:
> It was only still supported for subfile and only used by dvd2concat.
>
The latter statement is not true: This is public API; anyone can have
used it for any purpose. Your 2/5 adds a replacement for using it with
dvd2concat, but there are other usages, too; e.g. concatenating sev
On 2021-07-29 15:31, Gyan Doshi wrote:
On 2021-07-29 02:33, Michael Niedermayer wrote:
On Wed, Jul 28, 2021 at 09:56:35AM +0530, Gyan Doshi wrote:
---
doc/bitstream_filters.texi | 64 ---
libavcodec/noise_bsf.c | 161
+
tests/fate/m
On Thu, Jul 22, 2021 at 9:02 PM Christopher Degawa
wrote:
> these fields are only available past svt-av1 0.8.7
>
> Signed-off-by: Christopher Degawa
> ---
> libavcodec/libsvtav1.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/libavcodec/libsvtav1.c b/libavcodec/
On Tue, Jul 27, 2021 at 10:08:20AM -0300, James Almer wrote:
> Since we can't blindly trust the keyframe flag in packets and assume its
> contents are a valid Sync Sample, do some basic bitstream parsing to build the
> Sync Sample table in addition to a Random Access Recovery Point table.
>
> Sugg
On Thu, Jul 29, 2021 at 01:07:39AM +0200, Lynne wrote:
> 9 Jul 2021, 12:59 by d...@lynne.ee:
>
> > 8 Jul 2021, 22:32 by stefa...@gmail.com:
> >
> >> On Mon, Jun 28, 2021 at 2:50 AM Lynne wrote:
> >>
> >>>
> >>> 27 Jun 2021, 19:33 by kier...@obe.tv:
> >>>
> >>> >>
> >>> >> I'm thinking of getting
On 7/29/2021 2:58 PM, Michael Niedermayer wrote:
On Tue, Jul 27, 2021 at 10:08:20AM -0300, James Almer wrote:
Since we can't blindly trust the keyframe flag in packets and assume its
contents are a valid Sync Sample, do some basic bitstream parsing to build the
Sync Sample table in addition to a
Gyan Doshi:
> ---
> doc/bitstream_filters.texi | 64 ---
> libavcodec/noise_bsf.c | 161 +
> tests/fate/matroska.mak| 2 +-
> 3 files changed, 199 insertions(+), 28 deletions(-)
>
> diff --git a/doc/bitstream_filters.texi b/doc/bitstream_
This allow to specify additional parameters with
`./configure -ar='ar -...`.
Previously this resulted in an error (no operation specified).
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsu
On Fri, 23 Jul 2021, emco...@ffastrans.com wrote:
Am 2021-07-04 20:31, schrieb emco...@ffastrans.com:
Am 2021-07-04 20:28, schrieb emco...@ffastrans.com:
Am 2021-07-04 17:28, schrieb Marton Balint:
On Sat, 3 Jul 2021, Tomas Härdin wrote:
lör 2021-07-03 klockan 15:13 +0200 skrev emco...@ffa
On Sat, 24 Jul 2021, Pierre-Anthony Lemieux wrote:
Great. Let me know if you need anything else to process the patch,
which is necessary to process MXF files used by the Interoperable
Master Format (IMF, SMPTE ST 2067).
Thanks, applied.
Regards,
Marton
On Sun, Jul 18, 2021 at 1:03 PM Ma
Ensure instead that it's the correct value.
Signed-off-by: James Almer
---
libavformat/movenc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index 57062f45c5..fedc9c0e18 100644
--- a/libavformat/movenc.c
+++ b/libavformat
Since we can't blindly trust the keyframe flag in packets and assume its
contents are a valid Sync Sample, do some basic bitstream parsing to build the
Sync Sample table in addition to a Random Access Recovery Point table.
Suggested-by: ffm...@fb.com
Signed-off-by: James Almer
---
libavformat/mo
On Wed, 28 Jul 2021, Nicolas George wrote:
Marton Balint (12021-07-27):
You should mention the relevant rfc - RFC8089.
Locally added.
Also there are a couple of common deviations/extensions from the normative
standard, referenced in the RFC:
https://datatracker.ietf.org/doc/html/rfc8089
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index b61a189b07..428180273b 100755
--- a/configure
+++ b/configure
@@ -4869,10 +4869,10 @@ if $ar 2>&1 | grep -q Microsoft; then
arflags="-nologo"
ar_o='-out:$@'
elif $ar 2>&1 |
Fixes: reading over the end
Fixes:
36346/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ARGO_fuzzer-5366943107383296
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/argo.c | 2 ++
1 file ch
Michael Niedermayer:
> Fixes: reading over the end
> Fixes:
> 36346/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ARGO_fuzzer-5366943107383296
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael Niedermayer
> ---
On 7/29/2021 1:39 AM, James Almer wrote:
> It's not a problem for AV1 (we correctly tag all packets that should be
> sync samples).
I meant for the rest of the boxes ;)
> I'm not going to bother with HEVC right now, but this all can be
> simplified once we introduce a new parser API that expose
On 7/29/2021 2:31 AM, ffmpegandmahanstreamer@e.email wrote:
> I always meant to ask what is meaning of your profile picture?
What?
I don't know which picture you're referring to, but it doesn't matter.
This is neither the appropriate place nor thread.
- Derek
___
Andreas Rheinhardt:
> Michael Niedermayer:
>> Fixes: reading over the end
>> Fixes:
>> 36346/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ARGO_fuzzer-5366943107383296
>>
>> Found-by: continuous fuzzing process
>> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
>> Signed-off-by
James Almer:
> Since we can't blindly trust the keyframe flag in packets and assume its
> contents are a valid Sync Sample, do some basic bitstream parsing to build the
> Sync Sample table in addition to a Random Access Recovery Point table.
>
> Suggested-by: ffm...@fb.com
> Signed-off-by: James A
The function ff_qsvvpp_filter_frame should return a FFmpeg error code if
there is an error. However it might return a SDK error code without this
patch.
---
libavfilter/qsvvpp.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/libavfilter/qsvvpp.c b/libavfilter/q
Hi,
Our RTSP video server reply two streams in SDP are UDP and RTP/AVP/UDP.
>> m=video 0 UDP 33
>> m=video 0 RTP/AVP/UDP 33
ffmpeg now setup twice with the same transport "RTP/AVP/UDP"
The first time is
>> SETUP rtsp://192.168.1.100:554/MOV_12353521.mpg RTSP/1.0
>> Transport: RTP/AVP/UDP;uni
On 2021-07-30 00:00, Andreas Rheinhardt wrote:
Gyan Doshi:
---
doc/bitstream_filters.texi | 64 ---
libavcodec/noise_bsf.c | 161 +
tests/fate/matroska.mak| 2 +-
3 files changed, 199 insertions(+), 28 deletions(-)
diff --git a/
> On Jul 30, 2021, at 10:55 AM, Chiu, Yung-Hsiang wrote:
>
> Hi,
>
> Our RTSP video server reply two streams in SDP are UDP and RTP/AVP/UDP.
>>> m=video 0 UDP 33
>>> m=video 0 RTP/AVP/UDP 33
>
> ffmpeg now setup twice with the same transport "RTP/AVP/UDP"
>
> The first time is
>>> SETUP rtsp
30 matches
Mail list logo
