On Sun, Jun 2, 2024 at 12:58 PM Michael Niedermayer
wrote:
>
> On Mon, May 27, 2024 at 01:52:28AM +0200, Michael Niedermayer wrote:
> > Coverity claims these are used uninitilaized in CID1598561 Uninitialized
> > pointer write and CID1598565 Uninitialized pointer write
> >
> > Sponsored-by: Sover
I have looked at these two patches and they look good to me, if
anybody could commit them for me, that would be great.
On Wed, Nov 3, 2021 at 8:10 PM Brad Isbell wrote:
>
> From 25e34ef9f995afffe67e519bb6f03a750aa09ae2 Mon Sep 17 00:00:00 2001
> From: Brad Isbell
> Date: Wed, 3 Nov 2021 20:38:59
Thanks for cleaning that up!
On Thu, Jan 3, 2019 at 9:32 AM James Almer wrote:
>
> On 1/3/2019 1:12 PM, Oliver Collyer wrote:
> > Version created using git format-patch.
>
> Applied, thanks.
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
>
On Fri, Sep 21, 2018 at 3:19 PM Maxim Ershtein wrote:
>
> Hello,
>
> ffmpeg allows capturing a/v from custom DirectShow source filters, and
> provides some methods to pass parameters to these filters, but these
> methods seem insufficient.
>
> So ffmpeg offers to launch a filter configuration dial
As a note, configuring with
... --extra-ldexeflags=-Wl,--image-base,0x1000 ...
results in a link time command of
/Users/rdp/dev/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/bin/x86_64-w64-mingw32-gcc
-Wl,--nxcompat,--dynamicbase -Wl,--high-entropy-va -Wl,--as-needed
Original bigger patch is enough for now. Please merge, thanks!
On Wed, Jan 29, 2020 at 1:40 AM Paul B Mahol wrote:
>
> Please incorporate this change in previous bigger patch. It is ready for
> merge.
>
> On 1/29/20, Roger Pack wrote:
> > Good catch.
> > Or maybe
On Wed, Feb 26, 2020 at 4:36 AM Carl Eugen Hoyos wrote:
>
> Am Mi., 26. Feb. 2020 um 06:57 Uhr schrieb Roger Pack :
> >
> > Original bigger patch is enough for now. Please merge, thanks!
>
> What happened to your git account?
I never made one. Do we still send in privat
I want to add to the closed caption libavcodec/ccaption_dec.c decoder
to be able to handle both 608 "over CEA 708" (which it already does)
and also "raw EIA 608 byte pairs" which it doesn't.
My idea was to introduce a new codec id for the raw 608 pairs.
AV_CODEC_ID_EIA_RAW_608 or the like.
The de
I didn't actually *need* this but thought the functionality was very
nice to have, so here's my contribution.
It allows for forcing "rollup" style closed captions to output one
line at a time (basically, when there is a carriage return, it outputs
a line), so there is never any duplication in the
I needed this in order to be able to parse raw analog TV closed
caption byte pairs (analog line 21 CC's).
0001-closed-caption-decoder-accept-and-decode-a-new-codec.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
On Fri, Apr 17, 2020 at 4:53 PM James Almer wrote:
>
> On 4/17/2020 7:40 PM, Roger Pack wrote:
> > I want to add to the closed caption libavcodec/ccaption_dec.c decoder
> > to be able to handle both 608 "over CEA 708" (which it already does)
> > and also "r
Here's the final piece (to actually use the new codec), where we allow
to read raw CC 608 byte pairs from
analog directshow TV capture devices ("read" in a loose sense of the
term, it requires an intermediate dshow filter to extract the CC raw
bytes from the VBI incoming stream, but anyway it works
On Tue, Apr 28, 2020 at 1:46 AM Hendrik Leppkes wrote:
>
> On Tue, Apr 28, 2020 at 8:19 AM Roger Pack wrote:
> >
> > I didn't actually *need* this but thought the functionality was very
> > nice to have, so here's my contribution.
> >
> > It allows
> > c9153590e5f167e41910d867639eb887164e28d2
> > 0001-closed-caption-decoder-accept-and-decode-a-new-codec.patch
> > From bf29fe5330e83e37cf064b18918185c6b00d9b9f Mon Sep 17 00:00:00 2001
> > From: rogerdpack
> > Date: Tue, 28 Apr 2020 05:15:15 +
> > Subject: [PATCH 1/3] closed caption decod
On Thu, Apr 30, 2020 at 4:30 AM Kieran Kunhya wrote:
>
> On Thu, 30 Apr 2020 at 07:22, Roger Pack wrote:
>
> > > > c9153590e5f167e41910d867639eb887164e28d2
> > 0001-closed-caption-decoder-accept-and-decode-a-new-codec.patch
> > > > From bf29fe5330e83e37cf
On Fri, May 1, 2020 at 12:22 AM Kieran Kunhya wrote:
>
> On Fri, 1 May 2020 at 04:59, Roger Pack wrote:
>
> > On Thu, Apr 30, 2020 at 4:30 AM Kieran Kunhya wrote:
> > >
> > > On Thu, 30 Apr 2020 at 07:22, Roger Pack wrote:
> > >
> > > > >
Bump...
On Wed, Apr 29, 2020 at 11:23 PM Roger Pack wrote:
>
> > > c9153590e5f167e41910d867639eb887164e28d2
> > > 0001-closed-caption-decoder-accept-and-decode-a-new-codec.patch
> > > From bf29fe5330e83e37cf064b18918185c6b00d9b9f Mon Sep 17 00:00:00 2001
> >
Good catch.
Or maybe this?
diff --git a/libavdevice/dshow.c b/libavdevice/dshow.c
index d7f5bd7..96e4374 100644
--- a/libavdevice/dshow.c
+++ b/libavdevice/dshow.c
@@ -453,6 +453,7 @@ next:
if (type->pbFormat)
CoTaskMemFree(type->pbFormat);
CoTaskMemFree(type);
+
On 9/22/16, Roger Pack wrote:
> On 1/4/12, Yuval Adam wrote:
>> From: Yuval Adam
>>
>> The image2 muxer now supports timestamps in output filenames.
>> When used in an output patterm '%t' will be replaced with the frames
>> timestamp in hours, min
On 10/10/16, Roger Pack wrote:
> On 9/22/16, Roger Pack wrote:
>> On 1/4/12, Yuval Adam wrote:
>>> From: Yuval Adam
>>>
>>> The image2 muxer now supports timestamps in output filenames.
>>> When used in an output patterm '%t' will be repla
On 9/5/16, Roger Pack wrote:
> On 9/4/16, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> 2016-08-20 12:09 GMT+02:00 Timo Rothenpieler :
>>> On 8/19/2016 3:28 PM, Roger Pack wrote:
>>>> No complaints, would someone please push it for me? Sorry still
On 10/16/16, Michael Niedermayer wrote:
> On Mon, Oct 10, 2016 at 02:56:24PM -0600, Roger Pack wrote:
>> On 9/22/16, Roger Pack wrote:
>> > On 1/4/12, Yuval Adam wrote:
>> >> From: Yuval Adam
>> >>
>> >> The image2 muxer now supports timest
On 10/25/16, Michael Niedermayer wrote:
> On Mon, Oct 24, 2016 at 03:20:14PM -0600, Roger Pack wrote:
>> On 10/16/16, Michael Niedermayer wrote:
>> > On Mon, Oct 10, 2016 at 02:56:24PM -0600, Roger Pack wrote:
>> >> On 9/22/16, Roger Pack wrote:
>&g
On 10/26/16, Michael Niedermayer wrote:
> On Tue, Oct 25, 2016 at 06:38:12PM -0600, Roger Pack wrote:
>> On 10/25/16, Michael Niedermayer wrote:
>> > On Mon, Oct 24, 2016 at 03:20:14PM -0600, Roger Pack wrote:
>> >> On 10/16/16, Michael Niedermayer wrote:
>>
On 11/1/16, James Almer wrote:
> On 10/25/2016 9:38 PM, Roger Pack wrote:
>> From e8cac5c7de18766ce0f8f286f7dc140b82129df2 Mon Sep 17 00:00:00 2001
>> From: rogerdpack
>> Date: Tue, 25 Oct 2016 18:33:12 -0600
>> Subject: [PATCH 1/2] img2 encoder: allow %t in filen
On 11/1/16, James Almer wrote:
> On 11/1/2016 6:43 PM, James Almer wrote:
>> On 10/25/2016 9:38 PM, Roger Pack wrote:
>>> From e8cac5c7de18766ce0f8f286f7dc140b82129df2 Mon Sep 17 00:00:00 2001
>>> From: rogerdpack
>>> Date: Tue, 25 Oct 2016 18:33:12 -0600
&
On 11/14/16, James Almer wrote:
> On 11/14/2016 8:01 AM, Michael Niedermayer wrote:
>> On Sun, Nov 13, 2016 at 10:32:13PM +0100, Hendrik Leppkes wrote:
>>> ffmpeg | branch: master | Hendrik Leppkes | Sun Nov
>>> 13 22:29:04 2016 +0100| [bd0db4a32d85d027da4d4dc00490c20048090312] |
>>> committer: H
On 11/10/16, Roger Pack wrote:
> On 11/1/16, James Almer wrote:
>> On 11/1/2016 6:43 PM, James Almer wrote:
>>> On 10/25/2016 9:38 PM, Roger Pack wrote:
>>>> From e8cac5c7de18766ce0f8f286f7dc140b82129df2 Mon Sep 17 00:00:00 2001
>>>> From: rogerdpack
On 11/15/16, James Almer wrote:
> On 11/10/2016 4:26 PM, Roger Pack wrote:
>> On 11/1/16, James Almer wrote:
>>> > On 11/1/2016 6:43 PM, James Almer wrote:
>>>> >> On 10/25/2016 9:38 PM, Roger Pack wrote:
>>>>> >>> From e8cac5c7de18
On 11/18/16, Roger Pack wrote:
> On 11/15/16, James Almer wrote:
>> On 11/10/2016 4:26 PM, Roger Pack wrote:
>>> On 11/1/16, James Almer wrote:
>>>> > On 11/1/2016 6:43 PM, James Almer wrote:
>>>>> >> On
On 11/25/16, Roger Pack wrote:
> On 11/18/16, Roger Pack wrote:
>> On 11/15/16, James Almer wrote:
>>> On 11/10/2016 4:26 PM, Roger Pack wrote:
>>>> On 11/1/16, James Almer wrote:
>>>>> > On 11/1/2016 6:43 PM, James Almer wrote:
&
On 12/2/16, James Almer wrote:
> On 12/2/2016 10:06 PM, Roger Pack wrote:
>> On 11/25/16, Roger Pack wrote:
>>> On 11/18/16, Roger Pack wrote:
>>>> On 11/15/16, James Almer wrote:
>>>>> On 11/10/2016 4:26 PM, Roger Pack wrote:
>>>>>
, it does not work, it does not goes beyond the dshow "chit-chat"
>> > between filters/pins.
>> >
>> > After ctrl+c however the right codec stats are displayed...
>> >
>> > Regards,
>> > Máté
>> >
>> >
>> > On Mon, A
n case it's useful to someone in the meantime.
Cheers!
On 5/28/16, Roger Pack wrote:
> On 12/29/15, Hendrik Leppkes wrote:
>> On Wed, Dec 30, 2015 at 12:33 AM, Hendrik Leppkes
>> wrote:
>>> On Wed, Dec 30, 2015 at 12:23 AM, Roger Pack
>>> wrote:
>>&
Windows 10 anniversary edition screwed with how dshow video capture works.
This patch "helps" in some instances, though it still crashes with
rgb24 input (still working on that), at least now it works with yuvp
etc.
Thanks.
-Roger (a dshow maintainer)
0001-dshow-satisfy-alloc-contract-better-prev
Does this require some version check in configure to be added as well?
On 8/16/16, Michael Niedermayer wrote:
> On Mon, Aug 15, 2016 at 12:37:31PM -0400, Stephen Hutchinson wrote:
>> A number of new pix_fmts have been added to AviSynth+:
>> 16-bit packed RGB and RGBA
>> 10-, 12-, 14, and 16-bit Y
On 4/10/16, Michael Niedermayer wrote:
> On Sun, Apr 10, 2016 at 07:29:05PM +0100, Rostislav Pehlivanov wrote:
>> On 10 April 2016 at 17:42, Michael Niedermayer
>> wrote:
>>
>> > On Sun, Apr 10, 2016 at 04:38:35PM +0100, Kieran Kunhya wrote:
>> > > ---
>> > > Changelog | 1 +
>> >
On 8/13/16, Timo Rothenpieler wrote:
> On 8/12/2016 8:12 PM, Dan Haddix wrote:
>> Can you cross compile ffmpeg for Windows using the new bash built in to
>> Win10 anniversary? I'm currently using MinGW but it seems like it might be
>> easier to use the built in bash if possible. However I tried a
No complaints, would someone please push it for me? Sorry still
haven't figured out the key thing yet.
On 8/16/16, Roger Pack wrote:
> Windows 10 anniversary edition screwed with how dshow video capture works.
> This patch "helps" in some instances, though it still crash
On 9/4/16, Carl Eugen Hoyos wrote:
> Hi!
>
> 2016-08-20 12:09 GMT+02:00 Timo Rothenpieler :
>> On 8/19/2016 3:28 PM, Roger Pack wrote:
>>> No complaints, would someone please push it for me? Sorry still
>>> haven't figured out the key thing yet.
>>
&
On 1/4/12, Yuval Adam wrote:
> From: Yuval Adam
>
> The image2 muxer now supports timestamps in output filenames.
> When used in an output patterm '%t' will be replaced with the frames
> timestamp in hours, minutes and seconds (hh:mm:ss).
A somewhat updated (but not yet cleaned up) revision:
ht
On 1/25/16, Hendrik Leppkes wrote:
> On Mon, Jan 25, 2016 at 1:13 PM, Michael Niedermayer
> wrote:
>> On Mon, Jan 25, 2016 at 10:24:36AM +, Carl Eugen Hoyos wrote:
>>> Kieran Kunhya kunhya.com> writes:
>>>
>>> > The internal encoder is superior to libvo-aacenc.
>>>
>>> I thought this was the
On 3/26/16, Lou Logan wrote:
> Signed-off-by: Lou Logan
> ---
> Probably don't need to send this for review, but I know nothing of dshow
> and can't test this trivial change since I don't use Windows.
> ---
> libavdevice/dshow_crossbar.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-
did you have a failure with this? in what environment?
On 5/6/16, Moriyoshi Koizumi wrote:
> From: Moriyoshi koizumi
>
> Signed-off-by: Moriyoshi koizumi
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 1f684d2..fb8d7d3 10
ednesday, December 16, 2015, 8:24:33 PM, you wrote:
>
> DB>> On 12/16/2015 4:29 PM, Roger Pack wrote:
>>>> Still mulling over why this would be needed...hm
>
> DB>> It makes sense that CP_OEMCP is needed for device names, in my mind,
> DB>> after r
On 12/29/15, Hendrik Leppkes wrote:
> On Wed, Dec 30, 2015 at 12:33 AM, Hendrik Leppkes
> wrote:
>> On Wed, Dec 30, 2015 at 12:23 AM, Roger Pack
>> wrote:
>>>> OK I had this great idea to capture the incoming MPEG2 transport
>>>> stream from the dig
which compiler (mingw-w64 I presume?) are you using here?
On 5/6/16, Moriyoshi Koizumi wrote:
> From: Moriyoshi koizumi
>
> wchar_t is not always the same thing as WCHAR.
>
> Signed-off-by: Moriyoshi koizumi
> ---
> libavdevice/dshow.c | 6 +++---
> libavdevice/dshow_capture.h | 10 ++
A handful of devices don't support this, and the rest work fine with it :)
-roger-
From e724d7f169bcae3217455cd88f9c023d275d367a Mon Sep 17 00:00:00 2001
From: rogerdpack
Date: Wed, 15 Jun 2016 02:17:11 -0600
Subject: [PATCH] dshow: don't add two instances of same device to graphs
Signed-off-by:
On 6/15/16, Clément Bœsch wrote:
> On Wed, Jun 15, 2016 at 02:54:09AM -0600, Roger Pack wrote:
>> A handful of devices don't support this, and the rest work fine with it
>> :)
>>
>> -roger-
>
>> From e724d7f169bcae3217455cd88f9c023d275d367a Mon Sep 17 0
On 6/17/16, Roger Pack wrote:
> On 6/15/16, Clément Bœsch wrote:
>> On Wed, Jun 15, 2016 at 02:54:09AM -0600, Roger Pack wrote:
>>> A handful of devices don't support this, and the rest work fine with it
>>> :)
>>>
>>> -roger-
>>
>>&g
On 6/23/16, Gábor Alsecz wrote:
> Dear All,
>
> I am on a Windows machine and have no idea how can i:
> - Grab input sound from attached mic (usb) without dshow device
> OR
> - mix up the following command with dshow to get audio input from attached
> mic.
>
> ffmpeg -loop 1 -i 2K_1.jpg -vcodec li
could you post a copy of the compile failure for reference?
On 6/26/16, Rick Kern wrote:
> decklink_common.cpp includes a .cpp file from the DeckLink API which fails
> to build because there are non-static functions in the included .cpp file.
> This disables the missing-prototypes error so the fi
OK where do we find the "Nvidia CUVID decoder" library, is it this?
https://1f0.de/lav-cuvid/
On 6/10/16, Timo Rothenpieler wrote:
> ---
> Changelog | 2 +
> MAINTAINERS| 1 +
> configure | 34 +++
> libavcodec/Makefile| 5 +
> libavcodec/allcode
OK I was able to reproduce the problem.
Patch looks good, see attached, FWIW.
Thanks!
-roger-
On Sat, Aug 16, 2014 at 4:17 PM, Michael Niedermayer
wrote:
> On Fri, Aug 08, 2014 at 05:08:46PM +0800, hlszl1...@163.com wrote:
> > hi, all
> >
> > I'm using gdigrab feature on windows, and found that
Do you have some instructions on how to get the headers to make this
download work? Any links to some device to exercise the code, like on
amazon [cheaper better LOL].
On Tue, Sep 2, 2014 at 3:26 AM, Deti Fliegl wrote:
> On 30.08.14 01:22, Michael Niedermayer wrote:
>
>> moving code from (like
So you tested this in linux and windows? And it works? What is the
advantage of this over dshow, does it work "better" somehow [I know dshow
is deficient in multiple ways, FWIW]. Or was it just to add linux support?
Cheers!
-roger-
On Mon, Aug 18, 2014 at 12:40 PM, Deti Fliegl wrote:
> Rebased
On Mon, Sep 15, 2014 at 11:19 AM, Amnon Israely wrote:
> It's work already more than 24h
>
> Maybe it's not a big problem but in some scenario may do some problem
>
> Input #0, decklink, from 'DeckLink SDI (3)@3':
> Duration: N/A, start: 0.00, bitrate: 172032 kb/s
> Stream #0:0: Audio:
LGTM
On Mon, Jul 15, 2024 at 12:51 AM patches via ffmpeg-devel
wrote:
>
> The search of the current DirectShow device list has been customized so
> that audio devices are always found even if no video device is connected.
>
> Signed-off-by: Jens Frederich
> ---
> libavdevice/dshow.c | 2 +-
> 1
Hi all, just wondering, if I were to write a libavfilter that
basically "called out" to avisynth and had it process stuff, would
there be any ideological pushback, or would it possibly be accepted?
Cheers!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg
On Wed, Jul 17, 2024 at 1:43 AM patches wrote:
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of Roger Pack
> Sent: Wednesday, July 17, 2024 3:03 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH] avdevice/dshow: Don&#x
On Tue, Jul 2, 2024 at 1:39 PM Michael Niedermayer
wrote:
>
> On Mon, May 27, 2024 at 01:52:26AM +0200, Michael Niedermayer wrote:
> > Fixes: CID1598550 Resource leak
> >
> > Sponsored-by: Sovereign Tech Fund
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavdevice/dshow.c | 2 +-
> > 1 fi
On Thu, Jul 18, 2024 at 6:16 AM Stefan Oltmanns via ffmpeg-devel
wrote:
>
> AviSynth (or better VapourSynth) as filter sounds great, but is it possible?
> The reason why input plugins (like FFmpegSource2) in
> AviSynth/VapourSynth create an index file in a first pass is to allow
> frame-accurate r
On Wed, Nov 19, 2014 at 3:03 PM, Zach Swena
wrote:
> Hi,
>
> Can anyone elaborate on why direct show devices that use crossbar are not
> supported by FFmpeg? Also, what is keeping someone from taking the
> crossbar support found in VLC and porting it to FFmpeg, assuming the said
> port complied
ple analog inputs uses this feature.
>
Apparently it might cost 2K'ish to get this..."pay" implemented. Does
FFmpeg central here have any funds that might be able to be applied here
does anyone know? (we're trying to raise funds from various sources).
Cheers!
-roger-
>
On 2/2/14, Lukasz Marek wrote:
> Signed-off-by: Lukasz Marek
> ---
> libavdevice/avdevice.c | 191 +++
> libavdevice/avdevice.h | 238
> +
> libavdevice/version.h | 2 +-
> libavformat/avformat.h | 12 +++
>
Hello.
My basic question at hand "how to enumerate" dshow devices.
I noticed that the current AVDeviceInfo struct (used by
avdevice_list_devices and I presume by libraries that want to use
libavdevice, to enumerate devices and options) looks the following:
typedef struct AVDeviceInfo {
char *
On 3/11/14, Don Moir wrote:
>
> - Original Message -
> From: "Don Moir"
> To: "FFmpeg development discussions and patches"
> Sent: Monday, March 10, 2014 5:27 PM
> Subject: Re: [FFmpeg-devel] probable dshow bug or strangeness
>
>
>>
&g
Hello. I've noticed there are a few .cpp files in the codebase, but
not many (most seem to be tied to windows).
I have the choice, with the dshow stuff, to write in its "native" cpp
style (much easier/clearer IMO) or to convert it to straight "c
wrapper" style stuff. Is there a large preference
OK I have made modifications to the dshow source so that it adds the
ability to specify capture device by "more unique" name, capture pin
by name, crossbar device support [this is basically any capture source
with multiple inputs--definitely the most requested feature to date]
and ability to use "c
On 1/23/15, Michael Niedermayer wrote:
> On Fri, Jan 23, 2015 at 07:06:39AM -0700, Roger Pack wrote:
>> OK I have made modifications to the dshow source so that it adds the
>> ability to specify capture device by "more unique" name, capture pin
>> by name, c
See attached. Hope I didn't get it reversed or something weird.
-roger-
0001-dshow-show-incremental-values-allowed.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 1/30/15, Don Moir wrote:
>
> - Original Message -
> From: "Roger Pack"
> To: "FFmpeg development discussions and patches"
> Sent: Friday, January 30, 2015 7:09 AM
> Subject: [FFmpeg-devel] PATCH dshow show devices options
>
>
>&g
On 1/30/15, Michael Niedermayer wrote:
> On Fri, Jan 30, 2015 at 08:55:45AM -0700, Roger Pack wrote:
>> On 1/30/15, Don Moir wrote:
>> >
>> > - Original Message -
>> > From: "Roger Pack"
>> > To: "FFmpeg development discussions
On 1/31/15, Roger Pack wrote:
> On 1/30/15, Michael Niedermayer wrote:
>> On Fri, Jan 30, 2015 at 08:55:45AM -0700, Roger Pack wrote:
>>> On 1/30/15, Don Moir wrote:
>>> >
>>> > - Original Message -
>>> > From: "Roger P
On 7/5/12, Michael Niedermayer wrote:
> On Mon, Jun 25, 2012 at 02:21:21PM +0200, Michael Niedermayer wrote:
>> On Tue, Jun 19, 2012 at 07:10:04PM +0200, Reimar Döffinger wrote:
>> > On 19 Jun 2012, at 11:31, Joe Wreschnig
>> > wrote:
>> > > On Windows, the Ctrl+Break key combination usually does
If it looks worth anything, see attached (there's only one file).
Thanks!
0002-log-error-message-when-shutting-down-from-too-many-s.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/f
Hello again.
I was thinking this text:
Received signal %d: terminating.
Today sounds as if the process is "hard exiting" (like SIGKILL or some
odd) when it might be as benign as a ctrl+c that is used as a normal
shutdown process.
Perhaps it could be made to be something like:
Shutting down beca
On 6/24/15, wm4 wrote:
> On Wed, 24 Jun 2015 13:04:27 +0200
> Michael Niedermayer wrote:
>
>> On Wed, Jun 24, 2015 at 04:28:22AM -0600, Roger Pack wrote:
>> > If it looks worth anything, see attached (there's only one file).
>> > Thanks!
>>
>&g
On 6/24/15, Michael Niedermayer wrote:
> On Wed, Jun 24, 2015 at 04:19:38AM -0600, Roger Pack wrote:
>> On 7/5/12, Michael Niedermayer wrote:
>> > On Mon, Jun 25, 2012 at 02:21:21PM +0200, Michael Niedermayer wrote:
>> >> On Tue, Jun 19, 2012 at 07:10:04PM
On 6/24/15, compn wrote:
> On Wed, 24 Jun 2015 04:30:10 -0600
> Roger Pack wrote:
>
>> Received signal %d: terminating.
>>
>> Today sounds as if the process is "hard exiting" (like SIGKILL or some
>> odd) when it might be as benign as a ctrl+c t
On 6/25/15, James Almer wrote:
> On 24/06/15 7:19 AM, Roger Pack wrote:
>> +#ifdef HAVE_SETCONSOLECTRLHANDLER
>> +static BOOL WINAPI CtrlHandler(DWORD fdwCtrlType)
>> +{
>> +av_log(NULL, AV_LOG_DEBUG, "\nReceived windows signal %d\n",
>> fdw
You basically build it normally but build this as a library first:
https://github.com/mjb2000/mfx_dispatch.git
and configure with
--enable-libmfx
(NB that this mfx_dispatch thinger isn't compatible with windows XP so
I don't use it personally):
https://github.com/rdp/ffmpeg-windows-build-helpers/co
On 6/25/15, Michael Niedermayer wrote:
> On Wed, Jun 24, 2015 at 11:48:10PM -0600, Roger Pack wrote:
>> On 6/24/15, Michael Niedermayer wrote:
>> > On Wed, Jun 24, 2015 at 04:19:38AM -0600, Roger Pack wrote:
>> >> On 7/5/12, Michael Niedermayer wrote:
>> >
On 6/30/15, Michael Niedermayer wrote:
> On Mon, Jun 29, 2015 at 11:09:14PM -0600, Roger Pack wrote:
> [...]
>> +Sleep(0);
>
> the funky line ending is here
OK try this one.
thanks!
0001-windows-respond-to-logoff-and-ctrl-break-messages-as.patch
Descri
On 6/30/15, Michael Niedermayer wrote:
> On Tue, Jun 30, 2015 at 01:00:22PM -0600, Roger Pack wrote:
>> On 6/30/15, Michael Niedermayer wrote:
>> > On Mon, Jun 29, 2015 at 11:09:14PM -0600, Roger Pack wrote:
>>
>> > [...]
>>
>> >> +
See attached. Feel free to adjust it, but having more information
helped me a bit today.
Cheers!
-roger-
0001-log-more-information-on-failure-to-init-simple-filte.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
Lacking a better place to debate this, I would like to ask some
questions on a video codec idea...
The goal is basically to create a very fast lossless screen capture
codec (i.e. in the input there will be lots of repeated "colors" of
neighboring pixels, not a lot of dynamic content between frames
On 10/28/15, Matt Oliver wrote:
> On 5 October 2015 at 20:05, Matt Oliver wrote:
>
>> On 5 October 2015 at 19:29, Matt Oliver wrote:
>>
>>> On 30 September 2015 at 02:48, wm4 wrote:
>>>
>>>> On Wed, 23 Sep 2015 12:04:4
On 10/14/15, Nicolas George wrote:
> Le tridi 23 vendémiaire, an CCXXIV, Roger Pack a écrit :
>> For instance, given 3 frames of video ("one after another" from the
>> incoming video stream), "combine them" into one stream like:
>> pixel 1 frame 1, pixel
On 10/14/15, Hendrik Leppkes wrote:
> On Wed, Oct 14, 2015 at 8:08 PM, Roger Pack wrote:
>> Lacking a better place to debate this, I would like to ask some
>> questions on a video codec idea...
>>
>> The goal is basically to create a very fast lossless screen capture
On 12/14/15, Michael Savin wrote:
> Hi, please review this patch for cyrillic devices name support in
> libavdevice/dshow.
> Bug described here: https://trac.ffmpeg.org/ticket/5045
Still mulling over why this would be needed...hm
___
ffmpeg-devel ma
On 8/22/15, Michael Niedermayer wrote:
> On Sat, Aug 22, 2015 at 05:18:04AM +0200, Máté Sebők wrote:
>> >
>> > fails to build with mingw due to missing header
>> > In file included from ffmpeg/libavdevice/dshow.c:33:0:
>> > ffmpeg/libavdevice/bdadefs.h:8:24: fatal error: combaseapi.h: No such
>> >
On 12/17/15, Roger Pack wrote:
> On 8/22/15, Michael Niedermayer wrote:
>> On Sat, Aug 22, 2015 at 05:18:04AM +0200, Máté Sebők wrote:
>>> >
>>> > fails to build with mingw due to missing header
>>> > In file included from ffmpeg/libavdevice/dshow.c:
On 12/11/15, Lou Logan wrote:
> On Wed, 9 Dec 2015 21:24:06 +0100, Hendrik Leppkes wrote:
>
>> libvo-aacenc doesn't see any development anymore.
>> Its an encoder taken from the android sdk a long time ago, but AOSP
>> replaced it with fdk-aac, so libvo-aacenc is EOL.
>>
>> And its quality is horr
> OK I had this great idea to capture the incoming MPEG2 transport
> stream from the digital TV capture device. Kind of like "raw" stream,
> so FFmpeg could have access to, for instance, all the audio stream.
>
> It appears that the type coming out of the tuner is:
> MEDIATYPE_Stream
> with subtyp
On 1/2/16, Marton Balint wrote:
> Hi,
>
> To anybody who is interested, I have pushed my experimental SDL2 branch of
> ffplay to github. (https://github.com/cus/ffplay.git)
>
> SDL2 completely replaced SDL_Overlay with 3D textures, so with SDL2 it is
> possible to:
> - Use textures with odd width/
On 12/10/15, Philip Langdale wrote:
> On 2015-12-09 21:34, wm4 wrote:
>> On Mon, 7 Dec 2015 19:34:20 +0100
>> Timo Rothenpieler wrote:
>>
>>> > I don't remember if this was discussed when avisynth and other headers
>>> > where included, but what's the advantage of directly including the
>>> > hea
On 12/10/15, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> Lite version of one sent to VLC mailing list with only slow but high quality
> mode present.
> To use you need recent netCDF library, SOFA file(s), multichannel audio and
> headphones.
Could you post an example or step by ste
On 11/5/15, wm4 wrote:
> On Thu, 5 Nov 2015 16:23:04 +0800
> Agatha Hu wrote:
>
>> 2) We use AVFrame::opaque field to store a customized ffnvinfo struture
>> to prevent expensive CPU<->GPU transferration. Without it, the workflow
>> will be like CPU AVFrame input-->copy to GPU-->do CUDA resizing-
On 1/8/16, Andrey Turkin wrote:
> In my opinion this proliferation of various filters which do the same thing
> in different way is a configuration headache. There's CPU filters: one for
> scaling/format conversion, one for padding, one for cropping, like 5
> different filters for deinterlacing.
1 - 100 of 134 matches
Mail list logo
