volvement.
For that reason, I believe that if this plan goes forward, it should
include all past involvement, but possibly with the condition that the
involvement continues presently.
On the other hand, I believe this whole plan is a bad idea.
Regards,
--
Nicol
successor.
Small companies and small Libre Software projects are too vulnerable to
a takeover by a small number of greedy people who care about what they
can gain from it more than the well-being of the company/project.
Regards,
--
Nicolas George
_
Vittorio Giovara (12025-01-30):
> No, what we're seeing is a few representatives of the community
Nobody appointed them.
Nobody appointed you.
I am more representative of the community than anybody who has been
bullying Michael to leave.
___
ffmpeg-dev
plex.
This is precisely why Michael should be in charge.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ
or
whether some of them have more nefarious purposes, like some kind of
supply-chain attack.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link ab
a few people who do not behave in
the best interest of the project and would rather bully the leader into
resigning is the only way to work in peace, then that is what we should
do.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.or
bove, which is that people are leaving the
> project precisely because it is *not* democratically run.
This too is false, we established no such thing.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/m
Marth64 (12025-01-29):
> * The community wants
Please do not accept uncritically what a greedy minority limply
supported by a silent majority wants to pass as the will of the
community.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing l
very
bad outcomes.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
pened the first time.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Rémi Denis-Courmont (12025-01-24):
> For the record, those are just suggestions for future reference, not personal
> attacks.
Rule of thumb: messages that needs to clarify they are not personal
attacks are personal attacks.
--
Nicolas
Nicolas George (12025-01-22):
> That limitation of side data is very annoying. We should get rid of it,
> especially since it is not that hard.
>
> The issue is that side data has to be flat because its refcounting is
> built on top of AVBufferRef when AVBufferRef if only good for
ings API.)
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
people who do not take it with grace are precisely the
people who have been bullying you, and have as such lost their moral
rights to be listened to. Focus on the people you enjoyed hacking
together with who respect your leadership.
Regards,
--
Nicolas George
___
every other week and instead make use of the framework we came
> up with, or if needed, change it and improve it.
I have not said that “everything” is fucked. Only one thing is fucked:
democracy in a project as small but appetizing as FFmpeg. And the
improvement is obvious: reaffirm Micha
tern on things that need to be lightweight (no dynamic
allocations) but extensible.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above,
and fix bugs and add features in any part of
the code base.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-re
not surprised.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
people who want
to work in command-line is taken into consideration at all and not just
ignored or treated with scorn, as was so often the case in similar
discussions.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ff
an the maintainer?
Having two systems in parallel in practice does not allow anybody to use
only the one they like: in practice it forces everybody to use both.
That is terrible.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg
o me that goals requires quite a lot of work with all-in-one
online tools, whereas it is automatically achieved with mail.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-d
t; - What other options would the community consider and any relevant pros/cons?
Can any of the solution you would favor be used without a
javascript-enabled web browser?
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
av fork failed in part because it tried to be the upstream (and
pretend it was alone). I would say it amounts to about half the reason
it failed, the other half being the personality of its de-facto leaders.
Regards,
--
Nicolas George
___
ffmpeg-devel
modern workflow
I have still to be shown a “modern” workflow where “modern” is not
synonym mostly with clicking randomly on things in a web browser.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.or
Technical Committee.
Leadership is about policy more than it is about technical matters. The
CS was voted upon based on the latter.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listin
ick them out, not try to please them.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subj
ing about it.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
we should let "perfect be the
> enemy of good" and outright reject a proposed implementation that has
> been reported to work in many use cases.
Thank you for writing the obvious.
> It's a good starting point and can be improved over
m immediately and
might hypothetically make more work for them?
This “it does not belong in ffmpeg” attitude in the GA is killing the
project. It needs to stop. We need somebody in charge who understands
what ffmpeg really is.
--
Nicolas George
___
moved or disabled.
You were asking for proof that corporate-style mindset harms the
project, you have one right here: “we do not want this new feature
because it could mean bad PR” is one of the leitmotivs that have pushed
the project towards stagnation since the GA has had influence.
--
icolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
or packets and frames, accessing the side data directly is allowed, and
the utility functions to query return the data directly, without new
allocation. This API should have the same behavior, both for consistency
and convenience.
Regards,
--
Nicolas George
___
de we want for
the long run.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
, revoked their access.
First, we need to close the loophole. Afterwards we can explain why we
did it and discusser better ways. But please, first close the loophole
for good.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@f
as just a bad idea, for that very reason among others, let us
drop it.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffm
Same goes for patch #2 in this series.
1: For the same reason, I have always refrained from explaining how to
legally ship GPL ffmpeg with a proprietary binary.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://
function. I suppose the issue was a negative return value? If so,
please use >= 1 instead of == 1.
> arg += len;
> if (parse_channel_name(&arg, &in_ch_id, &named)){
> av_log(ctx, AV_LOG_ERROR,
Regards,
--
Nicolas George
___
Fix “Could not update timestamps for skipped samples” warning
and associated misfeature.
Signed-off-by: Nicolas George
---
libavfilter/src_movie.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/src_movie.c b/libavfilter/src_movie.c
index d2aa572d12..a1b3d026a6 100644
--- a
ew ideas and
instead getting on to managing releases and fuzzing the code.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
by Google or James you must
use an address at a less monopolistic operator for your CC seat.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above,
r
proposal”.
> This is not sound argumentation; this is outright libel against my person.
“You keep using that word. I do not think it means what you think it
means.”
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmp
those effects. I am afraid that I do not
> have
> an answer to your absurd 20-typos hypothetical.
I am just applying the rule that you defend. I see you have no argument
in favor of democracy since the only thing you found to answer was t
ould have as much
power over the direction of the project as somebody who knows multiple
subsystems inside-out and maintains them?
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
James Almer (12025-01-02):
> The string type is a remnant of the old channel layout API implementation.
Looks ok.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
tenance by the
most experienced developers.
Michael did an excellent job as a leader for years, and it only turns
sour when a small faction get greedy and tries to oust him to take over.
I look forward to him again being able to act as a leader without
obstruction from them.
Regards,
-
and irrelevance. And in our case, it is worsened
because some people have borrowed their definition from Erdoğan, “like a
tram, you ride it until you arrive at your destination, then you step
off”.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing l
eory” is the kind of accusation anybody can throw
around when they do not have factual objections beyond a few
misremembered details about who helped with the daily merges.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.o
than libav.
At some point, I do not exactly know when, libav died and its members
started coming back in the ffmpeg project.
I strongly suggest to read the list of names in the 2011 mail I have
quoted earlier and compare it to the list of people who criticize
Michael
Anton Khirnov (12024-12-24):
> So boiling down your verbal vomit, I get
> * you are delusional
This kind of is unacceptable. Especially from somebody who recently
volunteered to judge over other people's civility.
--
Nicolas George
___
f
Could you all stop ganging against Michael? It is reminiscent of the
bullying he was subjected to in the months leading to the fork that
convinced him to “resign” as project leader even though he was doing an
excellent job of if.
Thank you very much.
--
Nicolas George
End of text from me on this.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Kieran Kunhya via ffmpeg-devel (12024-12-13):
> Where is the second sample rate stored in wav?
Nowhere, obviously. I am surprised somebody who has been in the project
for more than 12 years still does not know how it works.
--
Nicolas Geo
ing.
The answer is yes.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
e/swr-async-firstpts | 34 +--
> 13 files changed, 560 insertions(+), 560 deletions(-)
Ok of course.
Thanks.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, vis
-
> 1 file changed, 23 insertions(+), 1 deletion(-)
Sorry for the delay. The logic looks sound, and I am assuming you have
checked that it now gives periodical output when the frequency is a
divisor of the sample frequency, so ok.
Regards,
--
Nicolas George
Jean-Baptiste Kempf (12024-11-26):
> Once again you attack people directly on threads.
« your kind of » ≠ « you », please do not abuse code of conduct rules to
silence discourse that you want to silence. It is part of the kind of
governance that is harming the project.
--
“I dont see why” isnt
xploit it for profit is the worst
possible person to manage or contribute to manage a Libre Software
project.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, v
Jean-Baptiste Kempf (12024-11-26):
Replying to this would be a waste of time.
It took me time to realize the harm your kind of governance did to
FFmpeg, but now it is quite obvious.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel
as Open Source might explain why the
result is such a mess.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.or
e a right to know who is accusing them and who the witnesses
are except in exceptional circumstances. I think the CC should grand the
same right to their accused.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org
said on the
criticised mail, but I fully agree with you that this intervention of a
CC member is entirely inappropriate and abusive.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmp
ot important.
LGTM.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Marton Balint (12024-11-10):
> The filter currently use inaccurate frequencies, this is inpreparation for
uses
> fixing that.
... by using numbers that will map to the equivalent value in the future
code.
LGTM otherwise.
Sorry for the delay.
Regards,
--
Nicolas
Marton Balint (12024-11-15):
> Will apply the series soon.
Sorry, this was the series I was thinking of when replying:
I have had a busy week, I will be able to look at it this week-end.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing l
Marton Balint (12024-11-15):
> Ping for this, will apply soon.
I have had a busy week, I will be able to look at it this week-end.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listi
and server distributions are not the only kind there is.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
James Almer (12024-11-07):
> Linux x86_32 is pretty much obsolete and deprecated.
Source?
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above,
s that we move
to such a tool mostly come from people who would have contributed
anyway. People who want their code in, shifting the burden of
maintenance to the project, but do not want to invest time into learning
different tools, even when they are superior.
Regards,
--
Nicolas
:
5.1. Add dphi_rem to phi_rem.
5.2. If phi_rem >= 0, subtract dphi_den to it and increment phi.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscr
tests/ref/fate/swr-async-firstpts | 2 +-
> 4 files changed, 94 insertions(+), 90 deletions(-)
Urgh, this is abominable.
NAK!
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmp
test filter
from 10^-9 to 10^-19 is a very minor enhancement that could easily
shelved until benchmark can be obtained.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubsc
James Almer (12024-11-05):
> Asking for benchmarks on old CPUs that are running deprecated or obsolete
> OSes is not reasonable.
I did not ask that they be running deprecated or obsolete OSes, so…
Also there are recent ARM32 CPUs.
--
Nicolas
Anton Khirnov (12024-11-05):
> 32bit CPUs are effectively obsolete and heading to extinction
The idea that FFmpeg is only for new hardware and should not support
“obsolete” hardware is unreasonable.
--
Nicolas George
___
ffmpeg-devel mailing l
Anton Khirnov (12024-11-05):
> That is an unreasonable demand IMO.
Care to elaborate why requesting benchmarks for changes on a filter that
was designed for speed on the architectures it would be most impacted on
seems to you unreasonable?
--
Nicolas Geo
an emulation or compatibility mode, and preferably a low-end
one.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpe
ction (so AVBufferRef → 🗑️).
Eventually, these AVWhateverLibraryInstance take charge of all global
mutable state: log callback, threads manager, overridden memory
allocation functions, etc.
I have had all this designed for quite some time.
Regards,
--
Nicol
shared
FFmpeg on the system. So I wonder one would utter such an obvious
falsehood.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffm
everal megaoctets with a custom build?
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
with what
ff_filter_process_command() does, i.e. change the value of options on
the fly.
Note: commands are not a part I am familiar with, I had to check and it
took me less than 30 seconds. You could have done the same.
--
Nicolas George.
___
ffmpeg-devel mailing li
Anton Khirnov (12024-10-15):
> headers, but that first requires to eliminate its use.
Not an excuse to remove the feature it was used for at the same time,
especially without warning about it.
--
Nicolas George
___
ffmpeg-devel mailing list
ffm
ommand callback, once as the flag. Having
the same information twice in the source code is a recipe for bugs:
unavoidably somebody will update one and not the other.
The correct way of doing this would be to add a function in libavfilter.
--
Nicolas
Alexander Strasser via ffmpeg-devel (12024-10-14):
> Learning question: How can we see this is a private field?
I suppose “revert everything and start again properly designing things
without loss of feature” will not be appreciated?
Regards,
--
Nicolas Geo
Anton Khirnov (12024-10-13):
> > I was experimenting with mencoder
> why oh oh god why?
Among other things, because on that other project there are no people
who think they can tell their fellow developers what they should or
should not be working on.
--
Nicol
anged.
This is making the code worse. Please stop and do better.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
e memcpy()
to fetch/return it.
- Have an instance of the struct in the buffersrc/sink and make it
available for that use.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/f
op the series altogether.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Anton Khirnov (12024-09-23):
> ---
> fftools/ffplay.c | 20 +---
> 1 file changed, 17 insertions(+), 3 deletions(-)
What an enhancement!
--
“I dont see why” isn't an argument.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
this flag is set, av_buffersink_get_frame_flags() fills the non-data
> + * fields of the supplied frame without causing any filtergraph activity.
> + *
> + * @note While frame data will be NULL, certain other allocated fields may be
> + * filled (e.g. ch_layout, hw_frames_ctx), so the
Anton Khirnov (12024-09-23):
> I fail to see
…
> how that is a problem, since you need an allocated AVFrame
> to use the buffersink API anyway.
Not at the same point in code.
> Not to mention that even if one allocates a dedicated AVFrame for the
> parameters, the cost is trivial
Anton Khirnov (12024-09-23):
> That is all av_buffersink_get_*() except type and frame_rate, for which
> AVFrame does not currently have fields.
NAK: an API that requires an allocated AVFrame to retrieve the
parameters is significantly worst than the existing.
--
Nicolas
is the proper fix,
but it is highly unlikely any other change is.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-deve
now the technicals of
this instance, but the first version of this patch looks like it could
be the proper fix fix. The second version is not a fix at all, no need
to know the technicals to know it.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing li
s. Add asserts where there are none.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.or
ike is…
concerning.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
on. It is not something
one can resign from, and even less something one can be expelled from.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link abo
necessary, but it is possible a small bit in
the common framework is missing to fully work with the simplified
interface.
Regards,
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-
me.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
ave to think about when you design an
API.
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with s
idget(opt);
} else {
???
}
What do you put in the else clause when you already handled all types
you know how to handle?
--
Nicolas George
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman
f you are using a 2026 FFmpeg with an application
from 2024, all the types introduced in FFmpeg between 2024 and 2026 will
be and cannot have a specific GUI, unless they are trivial enumerations.
This is why you need powerful text manipulation even with GUIs.
--
Nicol
1 - 100 of 1170 matches
Mail list logo
