I am trying to create a video by stitching multiple HLS segments (.ts
files) together based on a start time and end time. Basically, create a
video of a particular timeline in the HLS stream.
My setup has a camera pointing to a monitor that displays the system clock
(The camera control and the
I ask this because I think it can only be answered by looking at the source code. I'm not competent
to do that.
Is 'mi_mode=dup' or 'mi_mode=blend' or 'mi_mode=mci' the default?
On 01/26/2021 09:49 PM, pdr0 wrote:
Jim DeLaHunt-2 wrote
Perhaps the character between 'mci' and 'mc_mode' should
On 01/26/2021 09:49 PM, pdr0 wrote:
Jim DeLaHunt-2 wrote
Perhaps the character between 'mci' and 'mc_mode' should be ':' instead
of '='?
That works for me
-vf
minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10
Each one is a separate option and argument
Hongyi Zhao wrote
> I noticed there are -cgop/+cgop and -g options used by ffmpeg. But I
> really can't figure out the usage of them. Any hints will be highly
> appreciated.
-g is the maximum gop length (the maximum keyframe interval) . Some
codecs/settings have adaptive GOP and I frame
Jim DeLaHunt-2 wrote
> Perhaps the character between 'mci' and 'mc_mode' should be ':' instead
> of '='?
That works for me
-vf
minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10
Each one is a separate option and argument
On 01/26/2021 08:39 PM, Jim DeLaHunt wrote:
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that 'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out
On 01/26/2021 08:31 PM, Jim DeLaHunt wrote:
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that 'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that
'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out what
they would be.
ffmpeg -i SOURCE -map
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that
'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out what
they would be.
ffmpeg -i SOURCE -map
I noticed there are -cgop/+cgop and -g options used by ffmpeg. But I
really can't figure out the usage of them. Any hints will be highly
appreciated.
Regards
--
Assoc. Prof. Hongyi Zhao
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552
on 2021-01-26 at 19:49:34
Report written to "ffmpeg-20210126-194934.log"
Log level: 32
Command line:
ffmpeg -i "source=24FPS.mkv" -map 0 -filter_complex "split[1][2], [1]telecine=pattern=55,
select=not(eq(mod(n\\,5)\\,2))[3],
[2]minterpolate=fps=6/1001:mi_mode=mci=mc_
I ask 4 questions toward the end of this message. But first is my
beautification of the documentation.
minterpolate ...Convert the video to specified frame rate using motion
interpolation.
minterpolate=fps=60:mi_mode=Ø:scd=fdiff:scd_threshold=10 ...Defaults (Ø means
no default).
On 1/26/2021 1:03 PM, Reindl Harald wrote:
Am 26.01.21 um 22:00 schrieb MADOVSKY:
On 1/26/2021 12:50 PM, Reindl Harald wrote:
you still will be a security risk running on two legs tomorrow
for now the security risk is your disrespectful behavior on this
mailing list, insulting and
Am 26.01.21 um 22:00 schrieb MADOVSKY:
On 1/26/2021 12:50 PM, Reindl Harald wrote:
you still will be a security risk running on two legs tomorrow
for now the security risk is your disrespectful behavior on this mailing
list, insulting and harassing, bullying every one
not everyone, only
On 1/26/2021 12:50 PM, Reindl Harald wrote:
Am 26.01.21 um 21:47 schrieb MADOVSKY:
On 1/26/2021 12:29 PM, Reindl Harald wrote:
Am 26.01.21 um 21:27 schrieb MADOVSKY:
On 1/26/2021 12:21 PM, Reindl Harald wrote:
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb
Am 26.01.21 um 21:47 schrieb MADOVSKY:
On 1/26/2021 12:29 PM, Reindl Harald wrote:
Am 26.01.21 um 21:27 schrieb MADOVSKY:
On 1/26/2021 12:21 PM, Reindl Harald wrote:
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
On 1/26/2021 12:29 PM, Reindl Harald wrote:
Am 26.01.21 um 21:27 schrieb MADOVSKY:
On 1/26/2021 12:21 PM, Reindl Harald wrote:
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1;
Am 26.01.21 um 21:27 schrieb MADOVSKY:
On 1/26/2021 12:21 PM, Reindl Harald wrote:
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
Thunderbird/52.9.1
still
On 1/26/2021 12:21 PM, Reindl Harald wrote:
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
Thunderbird/52.9.1
still on WinXP - breaking news: we have 2021 now
Am 26.01.21 um 21:17 schrieb MADOVSKY:
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
Thunderbird/52.9.1
still on WinXP - breaking news: we have 2021 now
what's the purpose of your harassment? I
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
Thunderbird/52.9.1
still on WinXP - breaking news: we have 2021 now
what's the purpose of your harassment? I love XP and it's not your
F problem.
Hello all,
I'm going to ask everyone to take a break from this thread. It is no longer
about ffmpeg.
Thank you.
-m
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above,
Am 26.01.21 um 21:07 schrieb MADOVSKY:
You know what Mr Harald?
GFY
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
Thunderbird/52.9.1
still on WinXP - breaking news: we have 2021 now
___
ffmpeg-user mailing list
You know what Mr Harald?
GFY
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Am 26.01.21 um 20:56 schrieb MADOVSKY:
On 1/26/2021 11:52 AM, Reindl Harald wrote:
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
On 1/26/2021 11:52 AM, Reindl Harald wrote:
Am 26.01.21 um 20:48 schrieb MADOVSKY:
Am 26.01.21 um 20:28 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:25 AM Reindl Harald
wrote:
Am 26.01.21 um 20:23 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald
wrote:
On 1/26/2021 11:03 AM, Nicolas George wrote:
Carl Zwanzig (12021-01-26):
What is "invalid" there? linux does point releases, so does freebsd,
firefox, python, bind, glib, clang, etc. Find me a major opensource project,
other than ffmpeg, that tells people to use their development branch.
Am 26.01.21 um 20:48 schrieb MADOVSKY:
Am 26.01.21 um 20:28 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:25 AM Reindl Harald
wrote:
Am 26.01.21 um 20:23 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald
wrote:
Am 26.01.21 um 19:43 schrieb Chris Angelico:
Am 26.01.21 um 20:47 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 8:44 PM Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
On Tuesday, 26 January 2021, 19:10:38 GMT, Chris Angelico <
ros...@gmail.com> wrote:
Do you realise how toxic you make the FFMPEG community look?
To
Am 26.01.21 um 20:28 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:25 AM Reindl Harald
wrote:
Am 26.01.21 um 20:23 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald
wrote:
Am 26.01.21 um 19:43 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 5:36 AM Reindl
On Tue, Jan 26, 2021 at 8:44 PM Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> On Tuesday, 26 January 2021, 19:10:38 GMT, Chris Angelico <
> ros...@gmail.com> wrote:
>
> > Do you realise how toxic you make the FFMPEG community look?
>
> To answer your last point first, either
Am 26.01.21 um 20:33 schrieb Phil Rhodes via ffmpeg-user:
As regards the issue of release versions, the way I usually do it is to download a
statically-built executable. As a windows person I'd invariably do this anyway; I have
built ffmpeg on windows but it's a real hurt in the hiney. There
On Tuesday, 26 January 2021, 19:10:38 GMT, Chris Angelico
wrote:
> Do you realise how toxic you make the FFMPEG community look?
To answer your last point first, either they don't know how toxic it looks, or
they don't care. It's been like this for so long that if it's an elaborate
trolling
Am 26.01.21 um 20:28 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:25 AM Reindl Harald wrote:
Am 26.01.21 um 20:23 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald wrote:
Am 26.01.21 um 19:43 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 5:36 AM Reindl
On Wed, Jan 27, 2021 at 6:25 AM Reindl Harald wrote:
>
>
>
> Am 26.01.21 um 20:23 schrieb Chris Angelico:
> > On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald
> > wrote:
> >>
> >>
> >>
> >> Am 26.01.21 um 19:43 schrieb Chris Angelico:
> >>> On Wed, Jan 27, 2021 at 5:36 AM Reindl Harald
> >>>
Am 26.01.21 um 20:23 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald wrote:
Am 26.01.21 um 19:43 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 5:36 AM Reindl Harald wrote:
the unknown ones breaking workloads you didn't think of in your tests is
the problem and
On Wed, Jan 27, 2021 at 6:18 AM Reindl Harald wrote:
>
>
>
> Am 26.01.21 um 19:43 schrieb Chris Angelico:
> > On Wed, Jan 27, 2021 at 5:36 AM Reindl Harald
> > wrote:
> >> the unknown ones breaking workloads you didn't think of in your tests is
> >> the problem and hence only idiots running
Am 26.01.21 um 19:43 schrieb Chris Angelico:
On Wed, Jan 27, 2021 at 5:36 AM Reindl Harald wrote:
the unknown ones breaking workloads you didn't think of in your tests is
the problem and hence only idiots running git-snapshots in production
Lovely. You just called me an idiot to my face.
On Wed, Jan 27, 2021 at 5:36 AM Reindl Harald wrote:
> the unknown ones breaking workloads you didn't think of in your tests is
> the problem and hence only idiots running git-snapshots in production
Lovely. You just called me an idiot to my face.
For the record, not FFMPEG, but I have
Am 26.01.21 um 20:03 schrieb Nicolas George:
Carl Zwanzig (12021-01-26):
What is "invalid" there? linux does point releases, so does freebsd,
firefox, python, bind, glib, clang, etc. Find me a major opensource project,
other than ffmpeg, that tells people to use their development branch.
Carl Zwanzig (12021-01-26):
> What is "invalid" there? linux does point releases, so does freebsd,
> firefox, python, bind, glib, clang, etc. Find me a major opensource project,
> other than ffmpeg, that tells people to use their development branch.
Debian. The number of things based on Sid, or
On 1/26/2021 10:23 AM, Paul B Mahol wrote:
On Tue, Jan 26, 2021 at 7:12 PM Carl Zwanzig wrote:
Have to agree, pretty much _every_other_ opensource project* manages
x.y or x.y.z releases and _doesn't_ support (whatever that even means)
their git head or development branches.
That is invalid
Am Di., 26. Jan. 2021 um 19:09 Uhr schrieb Armin Hasitzka :
>
> > Nearly one year passed between 4.2 and 4.3.
> >
> > We recommend that all users download current
> > FFmpeg git head as we lack the manpower to
> > support other versions.
>
> Fair enough, thanks for that insight :) Out of curiosity
Am 26.01.21 um 19:33 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 19:29 Uhr schrieb Reindl Harald
:
Am 26.01.21 um 19:23 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 19:04 Uhr schrieb Reindl Harald
:
nobody on this planet can assure that a random
git-snapshot is error free and
Am 26.01.21 um 19:29 schrieb Reindl Harald:
Am 26.01.21 um 19:23 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 19:04 Uhr schrieb Reindl Harald
:
nobody on this planet can assure that a random
git-snapshot is error free and everyone who
pretends that is either stupid or lying
This is
Am Di., 26. Jan. 2021 um 19:29 Uhr schrieb Reindl Harald
:
>
>
>
> Am 26.01.21 um 19:23 schrieb Carl Eugen Hoyos:
> > Am Di., 26. Jan. 2021 um 19:04 Uhr schrieb Reindl Harald
> > :
> >
> >> nobody on this planet can assure that a random
> >> git-snapshot is error free and everyone who
> >>
Am 26.01.21 um 19:23 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 19:04 Uhr schrieb Reindl Harald
:
nobody on this planet can assure that a random
git-snapshot is error free and everyone who
pretends that is either stupid or lying
This is an important point, thank you for making it!
Am 26.01.21 um 19:23 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 7:12 PM Carl Zwanzig wrote:
On 1/26/2021 10:03 AM, Reindl Harald wrote:
Am 26.01.21 um 18:59 schrieb Paul B Mahol:
This is invalid
I'm starting to think that when Paul says "invalid" he means "I don't
agree
with you".
Am 26.01.21 um 19:22 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 7:13 PM Reindl Harald
wrote:
Am 26.01.21 um 19:09 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 7:04 PM Reindl Harald
wrote:
Am 26.01.21 um 18:59 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
Am Di., 26. Jan. 2021 um 19:04 Uhr schrieb Reindl Harald
:
> nobody on this planet can assure that a random
> git-snapshot is error free and everyone who
> pretends that is either stupid or lying
This is an important point, thank you for making it!
Of course, every random git-snapshots has many,
On Tue, Jan 26, 2021 at 7:12 PM Carl Zwanzig wrote:
> On 1/26/2021 10:03 AM, Reindl Harald wrote:
> > Am 26.01.21 um 18:59 schrieb Paul B Mahol:
> >> This is invalid
>
> I'm starting to think that when Paul says "invalid" he means "I don't
> agree
> with you".
>
> > it is *not* invalid
> >
> >
> For release versions, one just make sure that FATE report is not yellow.
Alright, that sounds simple enough; CI testing for the win \o/
Much appreciated + thanks for your hard work <3
Armin
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On Tue, Jan 26, 2021 at 7:13 PM Reindl Harald
wrote:
>
>
> Am 26.01.21 um 19:09 schrieb Paul B Mahol:
> > On Tue, Jan 26, 2021 at 7:04 PM Reindl Harald
> > wrote:
> >
> >>
> >>
> >> Am 26.01.21 um 18:59 schrieb Paul B Mahol:
> >>> On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
> >>> wrote:
>
Am 26.01.21 um 19:09 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 7:04 PM Reindl Harald
wrote:
Am 26.01.21 um 18:59 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
wrote:
Am 26.01.21 um 18:09 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb
On 1/26/2021 10:03 AM, Reindl Harald wrote:
Am 26.01.21 um 18:59 schrieb Paul B Mahol:
This is invalid
I'm starting to think that when Paul says "invalid" he means "I don't agree
with you".
it is *not* invalid
nobody on this planet can assure that a random git-snapshot is error free
and
On Tue, Jan 26, 2021 at 7:09 PM Armin Hasitzka wrote:
> > Nearly one year passed between 4.2 and 4.3.
> >
> > We recommend that all users download current
> > FFmpeg git head as we lack the manpower to
> > support other versions.
>
> Fair enough, thanks for that insight :) Out of curiosity --
On Tue, Jan 26, 2021 at 7:04 PM Reindl Harald
wrote:
>
>
> Am 26.01.21 um 18:59 schrieb Paul B Mahol:
> > On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
> > wrote:
> >
> >>
> >>
> >> Am 26.01.21 um 18:09 schrieb Carl Eugen Hoyos:
> >>> Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb Armin Hasitzka <
> Nearly one year passed between 4.2 and 4.3.
>
> We recommend that all users download current
> FFmpeg git head as we lack the manpower to
> support other versions.
Fair enough, thanks for that insight :) Out of curiosity -- are there
any special (stability) checks you run for releasing versions
Am 26.01.21 um 18:59 schrieb Paul B Mahol:
On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
wrote:
Am 26.01.21 um 18:09 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb Armin Hasitzka <
ar...@grabyo.com>:
Given that FFmpeg has been released on an almost
monthly basis
On Tue, Jan 26, 2021 at 6:50 PM Reindl Harald
wrote:
>
>
> Am 26.01.21 um 18:09 schrieb Carl Eugen Hoyos:
> > Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb Armin Hasitzka <
> ar...@grabyo.com>:
> >
> >> Given that FFmpeg has been released on an almost
> >> monthly basis before that
> >
> > Nearly
Am 26.01.21 um 18:09 schrieb Carl Eugen Hoyos:
Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb Armin Hasitzka :
Given that FFmpeg has been released on an almost
monthly basis before that
Nearly one year passed between 4.2 and 4.3.
you heard about point releases?
We recommend that all users
Am Di., 26. Jan. 2021 um 10:33 Uhr schrieb Armin Hasitzka :
> Given that FFmpeg has been released on an almost
> monthly basis before that
Nearly one year passed between 4.2 and 4.3.
We recommend that all users download current
FFmpeg git head as we lack the manpower to
support other versions.
Am Di., 26. Jan. 2021 um 16:51 Uhr schrieb Thomas Seilund via
ffmpeg-user :
> Input #0, h264, from 'pipe:':
>Duration: N/A, bitrate: N/A
> Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720, 25
> fps, 25 tbr, 1200k tbn, 50 tbc
> Guessed Channel Layout for Input Stream #1.0 :
Dear All
Video gradually falls behind!
I live stream from a Raspberry Pi with this command:
raspivid -vf -hf -t 0 -v -n -fps 25 -w 1280 -h 720 -b 200 --inline
-o - | \
ffmpeg -fflags nobuffer \
-thread_queue_size 4096 -i - \
-thread_queue_size 4096 -f pulse -i
> Am 26.01.2021 um 11:25 schrieb Stefan Riediger :
>
> It worked perfectly with version 4.2.3. Unfortunately I didn't get it to
> work with 4.3.1.
Please test current FFmpeg git head and please test with ffmpeg (the
application), not ffplay.
Carl Eugen
"Mark Filipak (ffmpeg)" writes:
> On 01/25/2021 03:58 PM, Leo Butler via ffmpeg-user wrote:
>> "Sergey \"GrayFace\" Rozhenko via ffmpeg-user"
>> writes:
>>
>>> Hello.
>>>
>>> I've met a childish person with nickname "cehoyos" that made it his
>>> goal to block a bug report I've filed.
>>
Hi guys,
I understand that the last official release of FFmpeg was 4.3.1 in
July last year. Given that FFmpeg has been released on an almost
monthly basis before that, I wonder whether there are any plans around
a version 4.4.0 or really any official version that would support
On Tue, 26 Jan 2021, 03:14 owen s, wrote:
> I am running this command
>
> ffmpeg-git -y \
> -vaapi_device /dev/dri/renderD128 \
> -framerate 60 -i ./image.jpg \
> -stream_loop -1 -i ./audio.mp3 \
> -map 0:v \
> -c:v h264_vaapi \
> -vf
>
>
Am 26.01.2021 um 01:09 schrieb owen s:
I am running this command
ffmpeg-git -y \
-vaapi_device /dev/dri/renderD128 \
-framerate 60 -i ./image.jpg \
-stream_loop -1 -i ./audio.mp3 \
-map 0:v \
-c:v h264_vaapi \
-vf
I think it's the encoding speed that's causing the problem.
Typically, encoding faster than real time would be a good problem to have
but in this situation, when I stream this fast, it fills up the streaming
platform buffer
after some point the streaming platform gets too far behind and cuts the
70 matches
Mail list logo
