On 1/29/19, Carl Eugen Hoyos wrote:
> 2019-01-28 19:40 GMT+01:00, Paul B Mahol :
>> On 1/28/19, Carl Eugen Hoyos wrote:
>>> 2019-01-28 16:17 GMT+01:00, Paul B Mahol :
On 1/28/19, Carl Eugen Hoyos wrote:
> 2019-01-28 15:20 GMT+01:00, Paul B Mahol :
>> On 1/28/19, Carl Eugen Hoyos wr
Hello,
A little history: Many years back I started using a modified version of
an unaccepted Decklink output patch, updated it to work for me, and
reposted a newer patch. Of course, the patch was not accepted for many
valid reasons like formatting and working only on Linux but it continued
to
Hello,
Il 21/10/2018 22:43, Giulio Benetti ha scritto:
Currently LIBDRM is appended to Libs: in libavutil.pc. This causes
every program linking with avutil to link with -ldrm in both shared and
static linking cases. In shared linking case it makes no sense, since
-ldrm is a dependency of libavut
On Tue, 29 Jan 2019, Deron wrote:
Hello,
A little history: Many years back I started using a modified version of
an unaccepted Decklink output patch, updated it to work for me, and
reposted a newer patch. Of course, the patch was not accepted for many
valid reasons like formatting and work
2019-01-29 10:10 GMT+01:00, Paul B Mahol :
> On 1/29/19, Carl Eugen Hoyos wrote:
>> 2019-01-28 19:40 GMT+01:00, Paul B Mahol :
>>> On 1/28/19, Carl Eugen Hoyos wrote:
2019-01-28 16:17 GMT+01:00, Paul B Mahol :
> On 1/28/19, Carl Eugen Hoyos wrote:
>> 2019-01-28 15:20 GMT+01:00, Paul
On 1/29/19, Carl Eugen Hoyos wrote:
> 2019-01-29 10:10 GMT+01:00, Paul B Mahol :
>> On 1/29/19, Carl Eugen Hoyos wrote:
>>> 2019-01-28 19:40 GMT+01:00, Paul B Mahol :
On 1/28/19, Carl Eugen Hoyos wrote:
> 2019-01-28 16:17 GMT+01:00, Paul B Mahol :
>> On 1/28/19, Carl Eugen Hoyos wr
2019-01-29 22:36 GMT+01:00, Paul B Mahol :
> On 1/29/19, Carl Eugen Hoyos wrote:
>> 2019-01-29 10:10 GMT+01:00, Paul B Mahol :
>>> On 1/29/19, Carl Eugen Hoyos wrote:
2019-01-28 19:40 GMT+01:00, Paul B Mahol :
> On 1/28/19, Carl Eugen Hoyos wrote:
>> 2019-01-28 16:17 GMT+01:00, Paul
Hi!
Attached patch fixes decoding NO_DATA amr-wb frames.
Please comment, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2019-01-27 22:38 GMT+01:00, Carl Eugen Hoyos :
> Attached patch was requested in ticket #7220 iiuc.
Ping.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This is from an old thread here:
https://ffmpeg.org/pipermail/ffmpeg-devel/2009-December/062437.html
The problem at hand manifests itself as "freeze-frame" of the last frame in
a stream being displayed in OBS, until that source is de-activated and
re-activated.
It seems that:
mp_media_next_pac
> It is not Blackmagic who does not want you to distribute FFmpeg
> with their (proprietary) library, it is us who do not allow distribution
> of FFmpeg binaries that link against Blackmagic libraries.
When you say proprietary library, do you mean the Desktop Video driver? I
believe this quali
11 matches
Mail list logo