I checked:
fate-list unchanged with basic setup
--disable-protocol=file pass
--disable-protocol=pipe pass
--disable-muxer=crc pass
--disable-muxer=framecrc pass
--disable-muxer=md5 pass
--disable-muxer=framemd5 pass
So I shouldn't have made any major mistake.
Nicolas Gaullier (4):
fate/all: add
SAO is 100% reusable
deblock is partial reusable
Nuo Mi (4):
hevcdec: move sao template to xvc_sao_template.c
vvcdec: reuse xvc_sao_template.c
hevcdec: move deblock template to xvc_deblock_template.c
vvcdec: reuse xvc_deblock_template.c
libavcodec/hevcdsp_template.c| 292 ++--
L. E. Segovia:
> Hi all,
>
> This is a patch to fix building FFmpeg without having DCE enabled.
> This was previously attempted by Andreas Rheinhardt in commit
> 40e6575aa3eed64cd32bf28c00ae57edc5acb25a. However, this is not remotely
> enough for MSVC; one can quickly check for this by configurin
Hi all,
This is a patch to fix building FFmpeg without having DCE enabled.
This was previously attempted by Andreas Rheinhardt in commit
40e6575aa3eed64cd32bf28c00ae57edc5acb25a. However, this is not remotely
enough for MSVC; one can quickly check for this by configuring the build
without any opt
On Sun, Oct 30, 2022 at 1:48 PM Mark Reid wrote:
>
>
> On Wed, Oct 12, 2022 at 3:06 PM Mark Reid wrote:
>
>>
>>
>> On Thu, Sep 29, 2022 at 11:08 AM wrote:
>>
>>> From: Mark Reid
>>>
>>> This patch series adds swscale input/output support for the packed rgb
>>> float formats.
>>> A few of the f
On Wed, Oct 12, 2022 at 3:06 PM Mark Reid wrote:
>
>
> On Thu, Sep 29, 2022 at 11:08 AM wrote:
>
>> From: Mark Reid
>>
>> This patch series adds swscale input/output support for the packed rgb
>> float formats.
>> A few of the filters also needed support the larger 96/128 bit packed
>> pixel si
Provide arm64 neon optimized functions from swscale family.
Hubert Mazur (4):
sw_scale: Add specializations for hscale 8 to 19
tests/sw_scale: Add test cases for input sizes 16
sw_scale: Add specializations for hscale 16 to 15
sw_scale: Add specializations for hscale 16 to 19
libswscale/
On Thu, Sep 29, 2022 at 11:08 AM wrote:
> From: Mark Reid
>
> This patch series adds swscale input/output support for the packed rgb
> float formats.
> A few of the filters also needed support the larger 96/128 bit packed
> pixel sizes.
>
> I also plan to eventually add lossless unscaled convers
Hello,
The following changes since commit b0c7352cd494c88d33f032be60b5e1c4e8b092a0:
avcodec/mjpegdec: Fix compilation (2022-09-30 19:30:29 +0200)
are available in the Git repository at:
git.remlab.net:git/ffmpeg.git remlab/rv-bswap
for you to fetch changes up to cb5a7b0834cbb3c8264
From: Mark Reid
This patch series adds swscale input/output support for the packed rgb float
formats.
A few of the filters also needed support the larger 96/128 bit packed pixel
sizes.
I also plan to eventually add lossless unscaled conversions between the planer
and packed formats.
Mark Rei
This is a series of patches that fix, enhance and cleanup support for audio and
video input on macos using avfoundation in libavdevice.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscri
> -Original Message-
> From: ffmpeg-devel On Behalf Of Hendrik
> Leppkes
> Sent: Monday, January 10, 2022 11:31 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 0/4] avcodec/dvbsubdec, dvdsubdec: don't
> dump images to
On Fri, Jan 7, 2022 at 5:14 PM Soft Works wrote:
>
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Hendrik
> > Leppkes
> > Sent: Friday, January 7, 2022 11:32 AM
> > To: FFmpeg development discussions and patches
> > Su
> -Original Message-
> From: ffmpeg-devel On Behalf Of Marton
> Balint
> Sent: Friday, January 7, 2022 10:53 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 0/4] avcodec/dvbsubdec, dvdsubdec: don't
> dump images to
On Fri, 7 Jan 2022, Soft Works wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of Marton
Balint
Sent: Friday, January 7, 2022 8:57 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH 0/4] avcodec/dvbsubdec, dvdsubdec: don't
dump imag
> -Original Message-
> From: ffmpeg-devel On Behalf Of Marton
> Balint
> Sent: Friday, January 7, 2022 8:57 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 0/4] avcodec/dvbsubdec, dvdsubdec: don't
> dump images to
On Fri, 7 Jan 2022, ffmpegagent wrote:
It's annoying and unexpected, but still useful at times (as I've realized
just recently).
This is a follow-up to the earlier submission here:
https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg128080.html
There has been a comment from Anton, quest
> -Original Message-
> From: ffmpeg-devel On Behalf Of Hendrik
> Leppkes
> Sent: Friday, January 7, 2022 11:32 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH 0/4] avcodec/dvbsubdec, dvdsubdec: don't
> dump images to
On Fri, Jan 7, 2022 at 11:20 AM Hendrik Leppkes wrote:
>
> On Fri, Jan 7, 2022 at 5:50 AM ffmpegagent wrote:
> >
> > It's annoying and unexpected, but still useful at times (as I've realized
> > just recently).
> >
> > This is a follow-up to the earlier submission here:
> > https://www.mail-archi
On Fri, Jan 7, 2022 at 5:50 AM ffmpegagent wrote:
>
> It's annoying and unexpected, but still useful at times (as I've realized
> just recently).
>
> This is a follow-up to the earlier submission here:
> https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg128080.html
>
> There has been a comme
It's annoying and unexpected, but still useful at times (as I've realized
just recently).
This is a follow-up to the earlier submission here:
https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg128080.html
There has been a comment from Anton, questioning whether the dump-feature is
useful. Me
These four patches fix three small new issues i found looking through
the dshow code (needd cleanup not being done), and fix a regression
introduced by my recent patches due to which devices that seem to not
behave according to spec but worked fine before my patches could no
longer be used.
Dieder
This series switches mmaldec to use the decoupled dataflow API to reduce
excessive buffering in the driver.
At the same time, remove dependency on sizeof(AVPacket) which is
deprecated. Also fix all compile warnings.
Ho Ming Shun (4):
avcodec/mmaldec: use decoupled dataflow
avcodec/mmaldec: u
Reorganized a bit for easier replying.
Also, while i think this is an important discussion, i do not see why
it should stop de-deprecation of a good API. Deprecating the device
capabilities API cleaned up avformat a bit, but various other function
pointers are left. A redesign would clean them all
Nicolas, I agree with what you said, and you obviously have given this
more thought than me. Your and Anton's replies provide two by now
pretty clear different views, I hope more will chime in.
I will only highlight some things below.
On Fri, Jun 11, 2021 at 3:17 PM Nicolas George wrote:
> Input
Anton Khirnov (12021-06-11):
> And it would be really really REALLY nice if you finally learned to
> distinguish between your personal opinions, official project policy, and
> objective truth.
Have you missed the part where I ask you to give arguments?
Regards,
--
Nicolas George
signature.a
Quoting Nicolas George (2021-06-11 14:14:57)
> Anton Khirnov (12021-06-09):
> > > > There is no timeline, it depends on someone sitting down and doing the
> > > > work. The options proposed so far were
> > > > 1) merging libavdevice into libavformat
> > > > 2) making libavdevice into an independent
Quoting Diederick C. Niehorster (2021-06-10 15:29:57)
> > The problem is that libavdevice is a separate library from libavformat,
> > but fundamentally depends on accessing libavformat internals.
>
> Ah ok, so this is at first instance about cleanup/separation, not
> necessarily about adding new f
Diederick C. Niehorster (12021-06-10):
> Let me respond on two levels.
>
> Before exploring the design space of a separation of libavdevice and
> libavformat below, I think it is important to first comment on the
> current state (and whether the AVDevice Capabilities part of my patch
> series shou
Anton Khirnov (12021-06-09):
> > > There is no timeline, it depends on someone sitting down and doing the
> > > work. The options proposed so far were
> > > 1) merging libavdevice into libavformat
> > > 2) making libavdevice into an independent library with an independent
> > >API
> > > 3) movi
Let me respond on two levels.
Before exploring the design space of a separation of libavdevice and
libavformat below, I think it is important to first comment on the
current state (and whether the AVDevice Capabilities part of my patch
series should be blocked by this discussion).
Importantly, I
Quoting Diederick C. Niehorster (2021-06-09 21:49:28)
> On Wed, Jun 9, 2021 at 8:18 PM Anton Khirnov wrote:
> >
> > Quoting Diederick C. Niehorster (2021-06-05 16:51:32)
> > > On Sat, Jun 5, 2021 at 4:36 PM Anton Khirnov wrote:
> > > > Sorry to rain on your parade, but I don't think we should go
On Wed, Jun 9, 2021 at 8:18 PM Anton Khirnov wrote:
>
> Quoting Diederick C. Niehorster (2021-06-05 16:51:32)
> > On Sat, Jun 5, 2021 at 4:36 PM Anton Khirnov wrote:
> > > Sorry to rain on your parade, but I don't think we should go ahead with
> > > this before deciding what is to be done with li
Quoting Diederick C. Niehorster (2021-06-05 16:51:32)
> On Sat, Jun 5, 2021 at 4:36 PM Anton Khirnov wrote:
> > Sorry to rain on your parade, but I don't think we should go ahead with
> > this before deciding what is to be done with libavdevice. The last
> > discussion about it died without being
Anton Khirnov (12021-06-05):
> Sorry to rain on your parade, but I don't think we should go ahead with
> this before deciding what is to be done with libavdevice. The last
> discussion about it died without being resolved, but the issues are
> still present.
So, now we have somebody who wants to w
On Sat, Jun 5, 2021 at 4:36 PM Anton Khirnov wrote:
> Sorry to rain on your parade, but I don't think we should go ahead with
> this before deciding what is to be done with libavdevice. The last
> discussion about it died without being resolved, but the issues are
> still present.
I understand. I
Quoting Diederick Niehorster (2021-06-04 00:45:48)
> ** Resending as it seems they didn't all make it..**
>
> Undeprecating the avdevice capabilities API and implementing it for the
> dshow device. Much needed. Together with the other patches i sent, a
> dshow device can now be properly used progr
** Resending as it seems they didn't all make it..**
Undeprecating the avdevice capabilities API and implementing it for the
dshow device. Much needed. Together with the other patches i sent, a
dshow device can now be properly used programmatically by programs using
ffmpeg under the hood.
Diederi
Undeprecating the avdevice capabilities API and implementing it for the
dshow device. Much needed. Together with the other patches i sent, a
dshow device can now be properly used programmatically by programs using
ffmpeg under the hood.
Diederick Niehorster (4):
avdevice/avdevice: Revert "Deprec
Now sets alignment, font size, font family and the region's position
and size according to the ASS styles passed to the encoder. Regions are
relatively important in TTML, since the spec-defined default region is in
raster location (similar to the default with HTML) - it starts from the
top left cor
在 2021/2/23 下午2:47, 殷时友 写道:
2021年2月19日 下午1:28，Jiaxun Yang 写道：
Get MMI optimizations build for Loongson-2 again.
Tested on Loongson-2 and Loongson-3A.
Jiaxun Yang (4):
avutil/mips: Use MMI_{L,S}QC1 macro in {SAVE,RECOVER}_REG
avutil/mips: Extract load store with shift C1 pair marco
av
On Tue, Feb 23, 2021, at 2:47 PM, 殷时友 wrote:
>
> > 2021年2月19日 下午1:28，Jiaxun Yang 写道：
> >
> > Get MMI optimizations build for Loongson-2 again.
> > Tested on Loongson-2 and Loongson-3A.
> >
> > Jiaxun Yang (4):
> > avutil/mips: Use MMI_{L,S}QC1 macro in {SAVE,RECOVER}_REG
> > avutil/mips: Ex
> 2021年2月19日 下午1:28，Jiaxun Yang 写道：
>
> Get MMI optimizations build for Loongson-2 again.
> Tested on Loongson-2 and Loongson-3A.
>
> Jiaxun Yang (4):
> avutil/mips: Use MMI_{L,S}QC1 macro in {SAVE,RECOVER}_REG
> avutil/mips: Extract load store with shift C1 pair marco
> avcodec/mips: Use MM
Get MMI optimizations build for Loongson-2 again.
Tested on Loongson-2 and Loongson-3A.
Jiaxun Yang (4):
avutil/mips: Use MMI_{L,S}QC1 macro in {SAVE,RECOVER}_REG
avutil/mips: Extract load store with shift C1 pair marco
avcodec/mips: Use MMI marcos to replace Loongson3 instructions
avutil/
Am Sa., 30. Jan. 2021 um 10:20 Uhr schrieb Christophe Gisquet
:
>
> Nobody complained so the CIDs are likely litle used.
https://trac.ffmpeg.org/ticket/7342
There are also tickets #7258 and #3707.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffm
Nobody complained so the CIDs are likely litle used.
This was developped without reference to the ST2019-1:2016 specs (some
fields are therefore guessed) but with reference to (unredistributable)
samples likely generated by the Avid SDK.
I have no idea how the alpha is coded, but it is variable-le
checkasm: all 657 tests passed
hevc_add_res_4x4_8_c: 49.7
hevc_add_res_4x4_8_neon: 20.5
hevc_add_res_4x4_10_c: 45.7
hevc_add_res_4x4_10_neon: 18.7
hevc_add_res_8x8_8_c: 211.0
hevc_add_res_8x8_8_neon: 24.5
hevc_add_res_8x8_10_c: 195.7
hevc_add_res_8x8_10_neon: 24.0
hevc_add_res_16x16_8_c: 787.2
hevc
On 11.11.2020 13:58, Timo Rothenpieler wrote:
Will push series soon if no one objects.
applied
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-de
Will push series soon if no one objects.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Timo Rothenpieler (4):
avcodec/av1dec: expose skip mode frame index
avcodec/av1dec: expose coded_lossless
avcodec/nvdec: add support for separate reference frame
avcodec/nvdec: add av1 hwaccel
Changelog | 1 +
configure | 2 +
libavcodec/Makefile| 1 +
This patch set started with a very simple wish to not have to set color
related values manually each time when utilizing ffmpeg.c.
As of the second iteration, this patch set passes FATE on both of my machines.
Only the MXF muxer tests actually needed changing, as the MXF muxer can now
write the co
This patch set started with a very simple wish to not have to set color
related values manually each time when utilizing ffmpeg.c.
I do not have the whole FATE suite locally, so most likely some test will
fail due to expectations of the metadata not being set for video - or due to
me failing to ha
On Wed, Jul 29, 2020 at 06:10:57PM +0800, Shiyou Yin wrote:
> Fixed four prob encountered when compiling ffmpeg with clang on mips.
> configure: ./configure --disable-mmi --cc=clang --cxx=clang++ --ld=clang
>
> [PATCH 1/4] [mips]: Fix register constraint error reported by clang.
> [PATCH 2/4] [mi
Fixed four prob encountered when compiling ffmpeg with clang on mips.
configure: ./configure --disable-mmi --cc=clang --cxx=clang++ --ld=clang
[PATCH 1/4] [mips]: Fix register constraint error reported by clang.
[PATCH 2/4] [mips]: Fix prob that 'ulw' and 'uld' unsupported by clang.
[PATCH 3/4] [
Adds support for the .TUN and .PCM files used by some
High Voltage Software games.
Zane van Iperen (4):
avcodec: add decoder for High Voltage Software's ALP ADPCM
avformat: add demuxer for LEGO Racers' ALP format
changelog: add adpcm_ima_alp decoder and alp demuxer
doc: add adpcm_ima_alp
Am 04.07.19 um 16:28 schrieb Thilo Borgmann:
> Am 30.06.19 um 14:11 schrieb Thilo Borgmann:
>> Hi,
>>
>> some cleanup and $SUBJECT.
>>
>> Documentation and reindent follows afterwards.
>
> Will add docs and push with remarks from Moritz soonish - if there are no
> more comments coming in.
Pushed
Am 30.06.19 um 14:11 schrieb Thilo Borgmann:
> Hi,
>
> some cleanup and $SUBJECT.
>
> Documentation and reindent follows afterwards.
Will add docs and push with remarks from Moritz soonish - if there are no more
comments coming in.
-Thilo
___
ffmpeg-
Hi,
some cleanup and $SUBJECT.
Documentation and reindent follows afterwards.
Thanks,
Thilo
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-
On 20/05/2019 23:33, Mark Thompson wrote:
> On 12/05/2019 20:00, Jonas Karlman wrote:
>> From what I understand support for composed layers wont be added to AMD as
>> it technically are multiple objects. I am not even sure if AMD have support
>> for NV12 as a drm plane format.
>
> Yeah. Mesa de
On 12/05/2019 20:00, Jonas Karlman wrote:
> On 2019-05-12 19:28, Mark Thompson wrote:
>> On 09/05/2019 20:38, Jonas Karlman wrote:
>>> Hello,
>>>
>>> When a multi-layer AVDRMFrameDescriptor is used to describe a frame the
>>> overall
>>> frame format is missing and applications need to deduce the
On 2019-05-12 19:28, Mark Thompson wrote:
> On 09/05/2019 20:38, Jonas Karlman wrote:
>> Hello,
>>
>> When a multi-layer AVDRMFrameDescriptor is used to describe a frame the
>> overall
>> frame format is missing and applications need to deduce the frame
>> DRM_FORMAT_*
>> based on sw_format or th
On 09/05/2019 20:38, Jonas Karlman wrote:
> Hello,
>
> When a multi-layer AVDRMFrameDescriptor is used to describe a frame the
> overall
> frame format is missing and applications need to deduce the frame DRM_FORMAT_*
> based on sw_format or the layers format.
>
> This patchset adds a AVDRMFrame
Hello,
When a multi-layer AVDRMFrameDescriptor is used to describe a frame the overall
frame format is missing and applications need to deduce the frame DRM_FORMAT_*
based on sw_format or the layers format.
This patchset adds a AVDRMFrameDescriptor.format field to remove any ambiguity
of what fra
Hello,
mpeg2_metadata currently has a bug wrt its handling of the
colour_description elements in case the input already had a
sequence_display_extension, but with colour_description set to zero.
Then the colour_description elements are zero at the end of the read
process; but zero is a forbidden v
With the official release of the Video SDK 9.0, I'm resending my
previous patch series for the new decode capabilities. I have left out
the new pixel formats representing MSB packed 444p10 and 444p12 due to
the lack of concensus on introducing these pixel formats. That means we
will always treat th
This patch set adds a native On2 VP4 decoder to FFmpeg, and completes the
set of Duck/On2/Google authored codecs.
VP4 is similar to VP3, adding new tables and some new tricks. Loop
filtering is performed between the motion compensation and apply idct steps.
For all my test streams, output is bit
The aim of this patchset is to avoid the memcpy that currently happens in
cbs_h2645_fragment_add_nals during the reading stage of cbs_h2645. This is
done by taking advantage of the way ff_h2645_packet_split (and internally
ff_h2645_extract_rbsp) works: If the NAL initially didn't contain any 0x03
e
There are currently several issues with level 1b in h264_levels and
h264_metadata:
1. The most obvious is that the table in h264_levels.c is simply wrong:
The level_idc for 1b and profile 66, 77 or 88 is 11, not 10. The first
patch corrects this.
2. If profile is 66, 77 or 88 and one lets h264_meta
Amit Kale 于2018年9月26日周三 下午1:50写道：
>
> Hi,
>
> I am sending an HLS manifest file output patch containing fixes broken down
> in four parts as follows
> 0001-Fix-computation-of-vs-start_pos.patch
> 0002-Add-a-new-hls_flag-peak_segment_bw.patch
> 0003-Adds-a-new-hls_flag-avg_bw.patch
> 0004-fix-mast
Hi,
I am sending an HLS manifest file output patch containing fixes broken down in
four parts as follows
0001-Fix-computation-of-vs-start_pos.patch
0002-Add-a-new-hls_flag-peak_segment_bw.patch
0003-Adds-a-new-hls_flag-avg_bw.patch
0004-fix-master_pl-segfault.patch
The overall description is th
On Mon, Aug 13, 2018 at 9:52 PM Jun Zhao wrote:
>
> V1: - add a new avfilter_graph_get_class function for AVFilterGraph
options.
> - fix can't dump "slice" sub-option for AVFilter.
> - fix can't dump mpeg4videodec options issue. (use command "ffmpeg -h
decoder=mpeg4")
>
> Jun Zhao (4):
>
V1: - add a new avfilter_graph_get_class function for AVFilterGraph options.
- fix can't dump "slice" sub-option for AVFilter.
- fix can't dump mpeg4videodec options issue. (use command "ffmpeg -h
decoder=mpeg4")
Jun Zhao (4):
lavfi: fix can't dispaly "slice" sub-option in "ffmpeg -h fu
V1: - check return value of setsockopt in network/tcp.
- move log_net_error as ff_log_net_error for udp/tcp error log reuse.
Jun Zhao (4):
lavf/network: add a ff_log_net_error function.
lavf/network: check return value of setsockopt.
lavf/tcp: check return value of setsockopt.
lavf/udp
Today, we have a colour range property on decoders and encoders. The
decoder sets the property on itself to reflect what it is decoding,
and the user sets it on the encoder to reflect what is being encoded.
However, we don't support a way to pass it through filter chains and
'ffmpeg' does not make
Hi,
The following patch series adds support for writing reel names to mxf files.
The extra metadata is only written if the metadata key "reel_name" is present.
The mxf fate tests needed to be updated because I slightly change to the way
internal uuids for tracks and component metadata are calculat
Hello all,
Below please find several patches which fix a couple of bugs as well
as adding support for 10-bit video on output and the "-sources" and
"-sinks" argument when specified by ffmpeg.c.
If you have any question/concerns, please don't hesitate to reply.
Thanks,
Devin Heitmueller
Devin H
Fixed since last time:
* The WebP decoder is modified to be slightly less abusive with the VP8 decoder
internals, so this no longer breaks images with alpha.
* The deinterlacer now works with iHD driver.
Mark Thompson (4):
vp8: Add hwaccel hooks
lavc/vaapi: Add VP8 decode hwaccel
vaapi_deco
This patchset was already sent but various cleaning has been done and it has
been rebased to the latest master.
The main goal is to have patch 3/4 that allows more flexibility on the decoder
pool in D3D11VA, which we need in VLC for better efficiency. Patch 4/4 is the
one that enables this flexibi
Hi,
On Tue, Dec 6, 2016 at 7:04 AM, James Darnley wrote:
> On 2016-12-05 19:32, James Darnley wrote:
> > Fixed the problem Michael highlighted. Dropped the intra functions
> until it
> > becomes clear why their performance is unexpected. Updated the
> benchmarks with
> > results from a Nehalem
On 2016-12-05 19:32, James Darnley wrote:
> Fixed the problem Michael highlighted. Dropped the intra functions until it
> becomes clear why their performance is unexpected. Updated the benchmarks with
> results from a Nehalem and used (slightly) more accurate data.
>
> Regarding the age of MMX:
Fixed the problem Michael highlighted. Dropped the intra functions until it
becomes clear why their performance is unexpected. Updated the benchmarks with
results from a Nehalem and used (slightly) more accurate data.
Regarding the age of MMX: I have written it so unless someone tells me to
remo
- Addresses all things mentioned by Anssi Hannula about HLS
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 1 +
libavcodec/codec_desc.c | 6 +
libavformat/Makefile| 2 +-
liba
On Tue, 4 Oct 2016, Josh de Kock wrote:
On 01/10/2016 18:27, Carlos Fernandez Sanz wrote:
- Addresses new comments such as like idx value checking and filename
checking
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct In
On Tue, Oct 4, 2016 at 12:11 PM, Josh de Kock wrote:
> Putting SCTE35 support in another library like Upipe was suggested as well.
This is something that I don't understand. Should FFmpeg just ignore
the existance of this very important standard in the professional
video world? Drive users to so
On 01/10/2016 18:27, Carlos Fernandez Sanz wrote:
- Addresses new comments such as like idx value checking and filename checking
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 2 +
- Same as V12 except for an empty that shouldn't have been there.
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 2 +
libavcodec/codec_desc.c | 6 +
libavformat/Makefile| 2 +-
- Addresses new comments such as like idx value checking and filename checking
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 2 +
libavcodec/codec_desc.c | 6 +
libavformat/Makefil
Oops, forgot to send this in reply to the previous thread. Should I re-send?
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-September/200092.html
On Wed, Sep 28, 2016 at 11:28 AM, Jon Toohill wrote:
> Trimming trailing_padding samples from the end of the track is not yet
> implemented.
>
> Jon To
Trimming trailing_padding samples from the end of the track is not yet
implemented.
Jon Toohill (4):
ffmpeg: re-copy codec parameters after encoding
lavc/libmp3lame: set trailing_padding after flushing encoder
lavf/mp3enc: write encoder delay/padding upon closing
lavf/mp3dec: read encoder
- Addresses all new comments
- fate now passes all tests
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 2 +
libavcodec/codec_desc.c | 6 +
libavformat/Makefile| 2 +-
libavfo
- Addressed all issues (I think) raised by cus. Major refactor from v9
Carlos Fernandez (4):
Adding SCTE-35 CUI codec
SCTE-35 extraction from mpegts
SCTE-35 support in hlsenc
Correct Indentation
libavcodec/avcodec.h| 3 +-
libavcodec/codec_desc.c | 6 +
libavformat/Makefile|
Trimming trailing_padding samples from the end of the track is not yet
implemented.
Jon Toohill (4):
ffmpeg: re-copy codec contexts after encoding
lavc/libmp3lame: set trailing_padding after flushing encoder
lavf/mp3enc: write encoder delay/padding upon closing
lavf/mp3dec: read encoder de
On Wed, Sep 21, 2016 at 01:42:05PM -0700, Mark Reid wrote:
> Hi
>
> Here is a set of mxf files that contain such metadata
>
> https://dl.dropboxusercontent.com/u/170952/fate/mxf/track_00_v01.mxf
> https://dl.dropboxusercontent.com/u/170952/fate/mxf/track_01_v02.mxf
> https://dl.dropboxusercontent
Hi
Here is a set of mxf files that contain such metadata
https://dl.dropboxusercontent.com/u/170952/fate/mxf/track_00_v01.mxf
https://dl.dropboxusercontent.com/u/170952/fate/mxf/track_01_v02.mxf
https://dl.dropboxusercontent.com/u/170952/fate/mxf/track_02_a01.mxf
https://dl.dropboxusercontent.com
On 15/09/2016 11:11, Thomas Volkert wrote:
[...]
Yes, it is quite a bit of unnecessary overhead, but it's much cleaner
than #ifdeffery in a single source file.
In general, I don't like the idea of having 2 source files with almost
the same content. This usually indicates to me that the code s
On 15.09.2016 08:55, Josh de Kock wrote:
On 14/09/2016 23:44, Thomas Volkert wrote:
On 15.09.2016 00:27, Josh de Kock wrote:
Hi,
Resending this set with ffplay now having two versions, a SDL2 and a
SDL1 version. I've integrated all comments up until now (hopefully).
Josh
Josh de Kock (3):
On 14/09/2016 23:44, Thomas Volkert wrote:
On 15.09.2016 00:27, Josh de Kock wrote:
Hi,
Resending this set with ffplay now having two versions, a SDL2 and a
SDL1 version. I've integrated all comments up until now (hopefully).
Josh
Josh de Kock (3):
lavd: Add SDL2 output device
ffplay: m
On 9/14/2016 7:44 PM, Thomas Volkert wrote:
> On 15.09.2016 00:27, Josh de Kock wrote:
>> Hi,
>>
>> Resending this set with ffplay now having two versions, a SDL2 and a
>> SDL1 version. I've integrated all comments up until now (hopefully).
>>
>> Josh
>>
>> Josh de Kock (3):
>>lavd: Add SDL2 ou
On 15.09.2016 00:27, Josh de Kock wrote:
Hi,
Resending this set with ffplay now having two versions, a SDL2 and a
SDL1 version. I've integrated all comments up until now (hopefully).
Josh
Josh de Kock (3):
lavd: Add SDL2 output device
ffplay: make copy for SDL1
MAINTAINERS: update my
Hi,
Resending this set with ffplay now having two versions, a SDL2 and a
SDL1 version. I've integrated all comments up until now (hopefully).
Josh
Josh de Kock (3):
lavd: Add SDL2 output device
ffplay: make copy for SDL1
MAINTAINERS: update my entries
Marton Balint (1):
ffplay: add SDL2
1 - 100 of 182 matches
Mail list logo
