On Mon, Jan 30, 2023 at 12:23 AM Michael Koch
wrote:
> Am 29.01.2023 um 23:36 schrieb Paul B Mahol:
> > On 1/29/23, Michael Koch wrote:
> >> Am 29.01.2023 um 23:07 schrieb Paul B Mahol:
> >>> On 1/29/23, Michael Koch wrote:
> Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
> > On
On 1/29/2023 10:03 PM, 김기돈 [메타버스엔터테인먼트] wrote:
Q1) Since I'm just using the libav libraries that are included in FFmpeg,
do I still need to distribute the source code of FFmpeg?
(all of the libav* libraries? lbavcodec, libavformat, libavfilter, etc)
The license and livense FAQ should explain
Hi,
I have two questions while I am following the license compliance checklist.
In the checklist, number 3, it says
*"Distribute the source code of FFmpeg, no matter if you modified it or
not."*
Q1) Since I'm just using the libav libraries that are included in FFmpeg,
do I still need to
Hi Vincent
Thank you so much for reporting the details of your journey. There seems to
be something with the TS muxer that makes it hard to split a media into
rigorously same-length segments.
I remember that in the first tests I made before answering your first email
in this thread, I tried to
Am 29.01.2023 um 23:36 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 23:07 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
On 1/29/23,
On 1/29/23, Michael Koch wrote:
> Am 29.01.2023 um 23:07 schrieb Paul B Mahol:
>> On 1/29/23, Michael Koch wrote:
>>> Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
> Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
>> On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 23:07 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Hello,
if I understood the documentation correctly, the
On 1/29/23, Michael Koch wrote:
> Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
>> On 1/29/23, Michael Koch wrote:
>>> Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
> Hello,
>
> if I understood the documentation correctly, the normalize filter maps
Am 29.01.2023 um 22:05 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Hello,
if I understood the documentation correctly, the normalize filter maps
the darkest input pixel to blackpt and the brightest input
On 1/29/23, Michael Koch wrote:
> Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
>> On 1/29/23, Michael Koch wrote:
>>> Hello,
>>>
>>> if I understood the documentation correctly, the normalize filter maps
>>> the darkest input pixel to blackpt and the brightest input pixel to
>>> whitept:
>>>
Am 29.01.2023 um 19:32 schrieb Paul B Mahol:
On 1/29/23, Michael Koch wrote:
Hello,
if I understood the documentation correctly, the normalize filter maps
the darkest input pixel to blackpt and the brightest input pixel to
whitept:
darkest pixel --> blackpt
brightest pixel --> whitept
On 1/29/23, Michael Koch wrote:
> Hello,
>
> if I understood the documentation correctly, the normalize filter maps
> the darkest input pixel to blackpt and the brightest input pixel to
> whitept:
> darkest pixel --> blackpt
> brightest pixel --> whitept
>
> However I need a slightly different
Hello,
if I understood the documentation correctly, the normalize filter maps
the darkest input pixel to blackpt and the brightest input pixel to whitept:
darkest pixel --> blackpt
brightest pixel --> whitept
However I need a slightly different mapping:
A black input pixel shall remain black,
13 matches
Mail list logo
