On 12/27/2020 04:26 PM, Paul B Mahol wrote:
On Sun, Dec 27, 2020 at 7:56 PM pdr0 wrote:
pdr0 wrote
I don't know if it's the full explanation...
The way it should work is ppsrc should disable everything else , given if
input src ,and ppsrc have the exact same timecodes
In theory, you
On Sun, Dec 27, 2020 at 7:56 PM pdr0 wrote:
> pdr0 wrote
> > I don't know if it's the full explanation...
> >
> > The way it should work is ppsrc should disable everything else , given if
> > input src ,and ppsrc have the exact same timecodes
> >
> >
> > In theory, you should get same as -vf
Hello,
In the v360 filter the alpha_mask option can be used to make unmapped
pixels transparent.
What's the simplest method for filling all transparent pixels with a color?
Let's assume the size of the video isn't known in advance.
This command line is working as expected:
ffmpeg -i input.mp4
Not sure about other OS's - For Windows, you don't need to escape commas
inside the text field; but the paths for fonts needs to be escaped
These work ok in windows
one comma
ffmpeg -f lavfi -r 24 -i color=c=green:s=640x480 -vf
drawtext="fontfile='C\:\\Windows\\Fonts\\Arial.ttf':text='Room
On Sun, Dec 27, 2020 at 7:53 PM Mark Filipak (ffmpeg)
wrote:
> On 12/27/2020 01:23 PM, Paul B Mahol wrote:
> > On Sun, Dec 27, 2020 at 6:45 PM Mark Filipak (ffmpeg) <
> markfili...@bog.us>
> > wrote:
> >
> >> On 12/27/2020 06:19 AM, Paul B Mahol wrote:
> >>> On Sun, Dec 27, 2020 at 5:00 AM Mark
I am attempting to overlay the text, “Room Temp Water, No Heat Mat” onto some
video.
If I use that exact string, the comma renders as a white box. According to the
drawtext documentation, I should escape the comma, but depending on the context
I may have to escape the escape character before
pdr0 wrote
> I don't know if it's the full explanation...
>
> The way it should work is ppsrc should disable everything else , given if
> input src ,and ppsrc have the exact same timecodes
>
>
> In theory, you should get same as -vf decimate on preprocessed.mkv
>
> ffmpeg -i preprocessed.mkv
On 12/27/2020 01:23 PM, Paul B Mahol wrote:
On Sun, Dec 27, 2020 at 6:45 PM Mark Filipak (ffmpeg)
wrote:
On 12/27/2020 06:19 AM, Paul B Mahol wrote:
On Sun, Dec 27, 2020 at 5:00 AM Mark Filipak (ffmpeg) <
markfili...@bog.us>
wrote:
Decimation with ppsrc=1 malfunctions.
Paul fixed this
I don't know if it's the full explanation...
The way it should work is ppsrc should disable everything else , given if
input src ,and ppsrc have the exact same timecodes
In theory, you should get same as -vf decimate on preprocessed.mkv
ffmpeg -i preprocessed.mkv -vf decimate -c:v libx264 -crf
On Sun, Dec 27, 2020 at 7:33 PM pdr0 wrote:
> One issue is scene change is still active. When you crop to a region of
> interest, a small change is effectively a larger % change. eg. The delta
> between 1020 and 1021 is large when head is going up. If you disable scene
> change, you get set
One issue is scene change is still active. When you crop to a region of
interest, a small change is effectively a larger % change. eg. The delta
between 1020 and 1021 is large when head is going up. If you disable scene
change, you get set intervals, it's no longer adaptive by scene change.
On 12/27/2020 07:30 AM, Carl Eugen Hoyos wrote:
Am 27.12.2020 um 12:19 schrieb Paul B Mahol :
Do you know exact telecine pattern used in your samples?
I don’t think the sample is telecined...
It must have been. Now, bear with me.
1, The original video was p24:
[A/a][B/b][C/c][D/d]
2, Later,
On Sun, Dec 27, 2020 at 6:45 PM Mark Filipak (ffmpeg)
wrote:
> On 12/27/2020 06:19 AM, Paul B Mahol wrote:
> > On Sun, Dec 27, 2020 at 5:00 AM Mark Filipak (ffmpeg) <
> markfili...@bog.us>
> > wrote:
> >
> >> Decimation with ppsrc=1 malfunctions.
>
> >> Paul fixed this somewhat, but it's still
On 12/27/2020 06:19 AM, Paul B Mahol wrote:
On Sun, Dec 27, 2020 at 5:00 AM Mark Filipak (ffmpeg)
wrote:
Decimation with ppsrc=1 malfunctions.
Paul fixed this somewhat, but it's still in trouble.
Since I eliminated threading and decimation as the cause, I suspect that
frames numbers are
> Am 27.12.2020 um 12:19 schrieb Paul B Mahol :
>
> Do you know exact telecine pattern used in your samples?
I don’t think the sample is telecined, or at least whatever was done with it
can’t be undone (even the description confirms this), so this part of the
discussion seems moot.
My
On Sun, Dec 27, 2020 at 5:00 AM Mark Filipak (ffmpeg)
wrote:
> Decimation with ppsrc=1 malfunctions.
>
> Paul fixed this somewhat, but it's still in trouble.
> Since I eliminated threading and decimation as the cause, I suspect that
> frames numbers are being
> bollixed.
>
> The report package
16 matches
Mail list logo
