Jun 12, 2021, 00:26 by t...@rothenpieler.org:
> On 11.06.2021 17:33, Steven Liu wrote:
>
>>
>>
>>> 在 2021年6月11日，22:43，Timo Rothenpieler 写道：
>>>
>> Hi Timo,
>>
>>>
>>> ---
>>> configure | 2 +
>>> doc/filters.texi| 46 ++
>>> libavfilter/Makefile
On 12.06.2021 00:42, Timo Rothenpieler wrote:
+#include
+#include
+#include
+
+int main(int argc, char **argv)
+{
+const char *name = NULL;
+unsigned int length = 0;
+unsigned char data;
+
+if (argc != 2) {
+return 1;
+} else {
+int arglen = strlen(argv[1]);
---
.gitignore | 1 +
compat/cuda/bin2c.c | 58
compat/cuda/ptx2c.sh| 34
configure | 17 ++
ffbuild/.gitignore | 1 +
ffbuild/common.mak | 28 --
libavfilte
Hi ffmpeg-devel community,
I recently encountered a problem with ffmpeg Cuda decoder.
When working with Cuda frame, after calling to the `avcodec_receive_frame`
function, the returned AVFrame (which contains a Cuda buffer) may contain
invalid data.
It doesn't happen often, the frequency of that
On 11.06.2021 17:33, Steven Liu wrote:
在 2021年6月11日，22:43，Timo Rothenpieler 写道：
Hi Timo,
---
configure | 2 +
doc/filters.texi| 46 ++
libavfilter/Makefile| 1 +
libavfilter/allfilters.c| 1 +
libavfilter/cuda/vec
On Fri, Jun 11, 2021 at 10:38 PM Diederick Niehorster wrote:
>
> This function allows formatting an option value stored in a double (such
> as the min and max fields of an AVOption, or min_value and max_value of
> an AVOptionRange) properly, e.g. 1 for a AV_OPT_TYPE_PIXEL_FMT -> yuyv422.
>
> Usefu
On Thu, Jun 10, 2021 at 12:08 PM Diederick C. Niehorster
wrote:
>
> On Thu, Jun 10, 2021 at 11:39 AM Diederick C. Niehorster
> wrote:
> > So in av_opt_get(), I'd do something like this:
> > AVBPrint buf;
> > av_bprint_init(&buf, 0, AV_BPRINT_SIZE_AUTOMATIC);
> > // 1. call internal print function
While the capabilities API is in principle meant to be used with an
allocated format context belonging to an unopened device, small changes
make it work for an opened dshow device as well. So hereby done.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 36 +++---
list_options true would crash when both a video and an audio device were
specified as input. Crash would occur on line 1618 (in this new rev)
because ctx->device_unique_name[otherDevType] would be NULL
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 6 --
1 file changed, 4 inse
No need to query twice, use value we've already unconditionally got.
Improve variable names
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow_pin.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/libavdevice/dshow_pin.c b/libavdevice/d
Signed-off-by: Diederick Niehorster
---
doc/examples/Makefile | 48 +--
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/doc/examples/Makefile b/doc/examples/Makefile
index de707bb3ca..7988ed4226 100644
--- a/doc/examples/Makefile
+++ b/doc/e
Signed-off-by: Diederick Niehorster
---
configure | 2 +
doc/examples/.gitignore| 1 +
doc/examples/Makefile | 1 +
doc/examples/Makefile.example | 1 +
doc/examples/device_get_capabilities.c | 190
avformat_alloc_input_context function analogous to
avformat_alloc_output_context2, except that it does not take a filename
argument as guessing the format by just the filename does not make sense.
avformat_alloc_input_context can be used e.g. with the avdevice
capabilities API, which needs an alloc
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
index 73113acddd..92cfaa062d 100644
--- a/libavdevice/dshow.c
+++ b/libavdevice/dshow.c
@@ -959,6 +959,
This implements avdevice_capabilities_create for the dshow device
(avdevice_capabilities_free not needed as it would be no-op).
This enables configuration discovery of DirectShow devices through the
API, which is important for my use case. It enables making proper GUIs
presenting users with option
After the avdevice capabilities API is implemented, the format context
may be reused after querying device capabilities in a later
avformat_open_input call. To enable this reuse, after releasing
resources, make sure to also set the corresponding pointers back to
NULL. This correctly indicates their
Needs to be moved up in file for upcoming implementation of
avdevice_capabilities_create.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/d
Signed-off-by: Diederick Niehorster
---
libavdevice/internal.h | 31 +++
libavdevice/utils.c| 48 ++
libavdevice/version.h | 2 +-
3 files changed, 80 insertions(+), 1 deletion(-)
diff --git a/libavdevice/internal.h b/libavdev
This function allows formatting an option value stored in a double (such
as the min and max fields of an AVOption, or min_value and max_value of
an AVOptionRange) properly, e.g. 1 for a AV_OPT_TYPE_PIXEL_FMT -> yuyv422.
Useful when printing more info about an option than just its value.
Usage will
AVOptionRange needs a way to encode that an options is not set. Here i
provide a documentation solution. When a range is invalid (value_min >
value_max), it should be considered unset/value not available.
When querying a range of formats of an avdevice, sometimes for a given
format the queried opt
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 2 +-
libavdevice/avdevice.h | 28 +---
libavdevice/internal.h | 33 +
libavdevice/version.h | 2 +-
4 files changed, 36 insertions(+), 29 deletions(-)
diff --git a/libavde
This patch series implements a series of features, mostly enhancing the
dshow avdevice, but also adding new functionality to avformat and
avutil. This whole patchset enabled users of the FFmpeg API to fully
query and control a dshow device, making FFmpeg a nice backend for any
program that needs ac
Draw implementation in line with that of avdevice_list_devices
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/libavdevice/avdevice.c b/libavdevice/avdevice.c
index 695b9143af..e66906e91b 100644
--- a/libav
This reverts commit 4f49ca7bbc75a9db4cdf93f27f95a668c751f160. The next
few patches clean up the API and implement this capability for
avdevice/dshow.
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 71 ++
libavdevice/avdevice.h | 5 ---
l
Some DirectShow devices (Logitech C920 webcam) expose each DirectShow
format they support twice, once without and once with extended color
information. During format selection, both match, this patch ensures
that the format with extended color information is selected if it is
available, else it fal
Enabled discovering a DirectShow device's color range, space, primaries,
transfer characteristics and chroma location, if the device exposes that
information. Sets them in the stream's codecpars.
Signed-off-by: Diederick Niehorster
Co-authored-by: Valerii Zapodovnikov
Signed-off-by: Diederick Ni
The "show config dialog" command message can now also trigger dialog
boxes for the crossbar connecting pins filter the analog tuner
audio / analog tuner filters. _Untested_ as I do not have either device.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 51 +
Cleanup was missing for when the show_analog_tv_tuner_audio_dialog is
true.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow_crossbar.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavdevice/dshow_crossbar.c b/libavdevice/dshow_crossbar.c
index 2438683cde..961defe690 100644
DirectShow source will pop up its configuration dialog when
AV_APP_TO_DEV_CONFIG is received. Implementation for several other
possible configuration dialogs is more involved and will be provided in
the next commit.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 29 +++
This control message can be used to programmatically ask a device to
show one of its configuration dialogs.
Adding documentation of this message's int argument.
Bumping avdevice version.
Signed-off-by: Diederick Niehorster
---
doc/indevs.texi| 34 ++
lib
This allows programmatic users of avdevice to start and stop the
DirectShow Capture graph (i.e. receive frames or not). This is important
because now the buffer fills up and starts dropping samples when
enqueued packets are not read out immediately after the demuxer is
opened.
Signed-off-by: Diede
Control messages are useful for programmatic control of not only outdevs
but also indevs.
Bumping avformat version.
Signed-off-by: Diederick Niehorster
---
libavdevice/avdevice.c | 8 +---
libavformat/avformat.h | 6 ++
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/lib
fftools now print info about what media type(s), if any, are provided by
sink and source avdevices.
Signed-off-by: Diederick Niehorster
---
fftools/cmdutils.c | 34 --
1 file changed, 24 insertions(+), 10 deletions(-)
diff --git a/fftools/cmdutils.c b/fftools/cmd
The list returned by get_device_list now contains info about what media
type(s), if any, can be provided by each device.
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
index 5d7f065a
An avdevice, regardless of whether its category says its an audio or
video device, may provide access to devices providing different media
types, or even single devices providing multiple media types. Also, some
devices may provide no media types. dshow is an example encompassing all
of these cases
the list_devices option of dshow didn't indicate whether a specific
device provides audio or video output. This patch iterates through all
media formats of all pins exposed by the device to see what types it
provides for capture, and prints this to the console for each device.
Importantly, this now
Needed to enable programmatic discovery of DirectShow devices
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow.c | 80 +
1 file changed, 73 insertions(+), 7 deletions(-)
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
index 389daa6380.
avdevice/dshow is a realtime device and as such does not support
seeking. Therefore, its demuxer format should define the
AVFMT_NOBINSEARCH, AVFMT_NOGENSEARCH and AVFMT_NO_BYTE_SEEK flags.
With these flags set, attempting to seek (with, e.g.,
avformat_seek_file()) correctly yields -1 (operation not
GetTime may return an error indication that the sample has not
timestamps, or may return a NULL start time. In those cases, fall back
to graph time.
Better debug message in case sample dropped: could now be audio or
video frame
Signed-off-by: Diederick Niehorster
---
libavdevice/dshow_pin.c | 19
Signed-off-by: Diederick Niehorster
---
doc/indevs.texi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/doc/indevs.texi b/doc/indevs.texi
index b377924c2f..685b1357a6 100644
--- a/doc/indevs.texi
+++ b/doc/indevs.texi
@@ -611,6 +611,12 @@ Save the currently used video capture filter dev
The dshow avdevice ignores timestamps for video frames provided by the
DirectShow device, instead using wallclock time, apparently because the
implementer of this code had a device that provided unreliable
timestamps. Me (and others) would like to use the device's timestamps.
The new use_video_devi
Am 11.06.21 um 21:07 schrieb Thilo Borgmann:
Hi,
$subject seems to be useful depending on the network.
v2 attached with updates to documentation and code.
Please check if I missed the point of it.
Follow-up to add the remark also to TCP documentation.
-Thilo
From 69e6fb2acab42811c442eddafd
Hi,
$subject seems to be useful depending on the network.
v2 attached with updates to documentation and code.
Please check if I missed the point of it.
Thanks!
-Thilo
From 79f1589ba5d9224146d71c2605ca4cc02c852cb2 Mon Sep 17 00:00:00 2001
From: Nick Ruff
Date: Fri, 11 Jun 2021 21:02:02 +0200
On Fri, 2021-06-11 at 10:19 +0800, Haihao Xiang wrote:
> Since commit 89ffcd1, the status pts of the output link is set to a
> value in the input link time base, not in the output link time base
> when
> EOF is reached. Usually this pst value is larger than the required
> one
> because the output l
Quoting Michael Niedermayer (2021-06-11 17:01:20)
> On Thu, Jun 10, 2021 at 05:49:48PM +0200, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2021-06-01 15:02:27)
> > > On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> > > > Currently existing sws_scale() accepts as input a use
On Tue, Jun 8, 2021 at 1:45 AM Andreas Rheinhardt
wrote:
> This has absolutely nothing to do with full/limited range, but rather
> whether the AVOptionRange contains an interval or a single value.
> (Not that I know why this needs to be set explicitly and not implicitly
> via is_range = value_min
Outrageous!
On Fri, Jun 11, 2021 at 4:49 PM Nicolas George wrote:
> Thilo Borgman (12021-06-10):
> > some of you might have realized that I've removed Valerii Zapodovnikov
> > from our mailing list after [1].
> >
> > I did this in my function as a mailing list admin because I think our
> > guide
On Sat, 5 Jun 2021 22:42:26 +0200
Gustav Grusell wrote:
> Before, seeking in hls streams would always seek to the next keyframe
> after the given timestamp. With this fix, if AVSEEK_FLAG_BACKWARD is
> set, seeking will be to the first keyframe of the segment containing
> the given timestamp. Thi
Hi,
Am 09.06.21 um 12:41 schrieb Nicolas George:
> Thilo Borgman (12021-06-09):
>> $subject seems to be useful depending on the network.
>
> It looks premature. TCP_NODELAY should only ever used when the network
> code already takes care of writing data in a single system call. This is
> not what
Does my last explanation make sense or if not could you point me to
where this reasoning is incorrect?
Kevin LaFlamme
Director of Engineering (Front End)
774.265.0382 (m)
aiera.com
On Jun 8, 2021, 8:52 PM -0400, Kevin LaFlamme , wrote:
> I just realized there’s probably a more straightforward expl
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
> 在 2021年6月11日，22:43，Timo Rothenpieler 写道：
Hi Timo,
>
> ---
> configure | 2 +
> doc/filters.texi| 46 ++
> libavfilter/Makefile| 1 +
> libavfilter/allfilters.c| 1 +
> libavfilter/cuda/vector_helpers.cuh | 14 +-
> l
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
On Thu, Jun 10, 2021 at 05:13:23PM +0200, Anton Khirnov wrote:
> That function pointer is now used only for unscaled conversion.
> ---
> libswscale/aarch64/swscale_unscaled.c | 2 +-
> libswscale/arm/swscale_unscaled.c | 6 +--
> libswscale/ppc/yuv2yuv_altivec.c | 4 +-
> libswscale/sw
On Thu, Jun 10, 2021 at 05:49:48PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2021-06-01 15:02:27)
> > On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> > > Currently existing sws_scale() accepts as input a user-determined slice
> > > of input data and produces an ind
Thilo Borgman (12021-06-10):
> some of you might have realized that I've removed Valerii Zapodovnikov
> from our mailing list after [1].
>
> I did this in my function as a mailing list admin because I think our
> guidelines for the mailing list are mandatory for everyone to be
> welcome here.
> Pl
On 11.06.2021 12:27, stuhlo wrote:
From: stuhlo
This fixes setting of `key_frame` flag in AVFrame when input h264 packets
represents individual fields of interlaced video.
In this case, pairs of two consecutive fields represents a single decoded
picture and have identical `CurrPicIdx`, howeve
---
configure | 2 +
doc/filters.texi| 46 ++
libavfilter/Makefile| 1 +
libavfilter/allfilters.c| 1 +
libavfilter/cuda/vector_helpers.cuh | 14 +-
libavfilter/version.h | 2 +-
libavfilter/vf_format
On Fri, Jun 11, 2021 at 09:34:10AM -0300, James Almer wrote:
> On 6/11/2021 9:03 AM, Michael Niedermayer wrote:
> > On Thu, Jun 10, 2021 at 03:27:37PM -0300, James Almer wrote:
> > > On 6/10/2021 3:18 PM, Michael Niedermayer wrote:
> > > > On Wed, Jun 09, 2021 at 03:07:41PM -0300, James Almer wrote
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
On 6/11/2021 9:03 AM, Michael Niedermayer wrote:
On Thu, Jun 10, 2021 at 03:27:37PM -0300, James Almer wrote:
On 6/10/2021 3:18 PM, Michael Niedermayer wrote:
On Wed, Jun 09, 2021 at 03:07:41PM -0300, James Almer wrote:
It can be useful to library users, and is currently being used by ffmpeg.c
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
On Thu, Jun 10, 2021 at 03:27:37PM -0300, James Almer wrote:
> On 6/10/2021 3:18 PM, Michael Niedermayer wrote:
> > On Wed, Jun 09, 2021 at 03:07:41PM -0300, James Almer wrote:
> > > It can be useful to library users, and is currently being used by ffmpeg.c
> > >
> > > Suggested-by: Hendrik Leppke
From: stuhlo
This fixes setting of `key_frame` flag in AVFrame when input h264 packets
represents individual fields of interlaced video.
In this case, pairs of two consecutive fields represents a single decoded
picture and have identical `CurrPicIdx`, however, only
the first field is entirely i
From: Limin Wang
Signed-off-by: Limin Wang
---
libavformat/dashenc.c | 16 +++-
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index 8a626c1..b7622bc 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -330,
On Wed, 2 Jun 2021 at 08:55, Steven Liu wrote:
>
> LGTM
>
>
> Thanks
> Steven
Hi everyone
Am I supposed to do something for this to get applied or is it just a
matter of time until someone picks it up?
Best regards
/Robert
___
ffmpeg-devel mailing li
67 matches
Mail list logo
