Replying to everybody at once:
To Ronald, regarding "rewrite EVERYTHING!!!" versus "added as extensions of
the current API":
My gut feeling is that starting from scratch would prove less efforts in
total. The current code is already quite convoluted, even adding a single
type requires adding cod
I like the idea of JSON syntax.
To avoid escaping problems simply read the arguments out of a file instead of
off the command line.
Suggestion
-vf '@/path/to/filter-syntax' to read filter syntax from a file
-vf '-' to read filter syntax from STDIN
___
On 12/4/15, Nicolas George wrote:
> Hi.
>
> This is a rather long explanation on ideas I have to replace the options
> system with something better. I will not work on it before I have made
> significant progress on de-recursiving lavfi, but I can still think of it
> and mature its design while wa
On 05.12.2015 00:54, James Darnley wrote:
On 2015-12-04 15:33, Nicolas George wrote:
Why do we need a new options system?
Most importantly: escaping hell
OMG yes! I have seen several times the amount of backslashes Windows
users are forced to use to provide a path to some of the filters.
On Fri, 4 Dec 2015 15:33:39 +0100
Nicolas George wrote:
> Hi.
>
> This is a rather long explanation on ideas I have to replace the
> options system with something better. I will not work on it before I
great, i'd suggest asking for comments also on libav-user and
ffmpeg-user list. there maybe s
On 2015-12-04 15:33, Nicolas George wrote:
> Why do we need a new options system?
>
> Most importantly: escaping hell
OMG yes! I have seen several times the amount of backslashes Windows
users are forced to use to provide a path to some of the filters.
You raise a lot of good points that need
On Fri, Dec 04, 2015 at 03:33:39PM +0100, Nicolas George wrote:
[...]
> Extra features
>
> This system allows a few new interesting features. Some of them just
> thanks to no longer worrying about sizeof(AVOption).
>
> Special syntaxes
>
> Any component can define its own syn
Hi
On Fri, Dec 04, 2015 at 11:22:17AM -0500, Ganesh Ajjanagadde wrote:
[...]
> > Conclusion
> >
> > This has been a very lengthy exposition. Actually, I believe
> > implementation would not be that long. Well, longer than text, of course,
> > but not as gigantic as the explanation suggests.
Le quartidi 14 frimaire, an CCXXIV, Ganesh Ajjanagadde a écrit :
> > And while we are at it, we should change them to accept strings as
> > pointer+length or pointer+end instead of zero-terminated C strings.
> Are you referring here to something like djb's netstrings:
> http://cr.yp.to/
Am 04.12.15 um 15:33 schrieb Nicolas George:
> [...]
> Personal note: if you skimmed through the whole thing and did not find it
> completely uninteresting, I would appreciate even short quick feedback,
> even "looks interesting, will read more carefully later".
I've no idea of the internals behin
Hi Nicolas,
On Fri, Dec 4, 2015 at 9:33 AM, Nicolas George wrote:
> Personal note: if you skimmed through the whole thing and did not find it
> completely uninteresting, I would appreciate even short quick feedback,
> even "looks interesting, will read more carefully later".
I feel for you :).
On Fri, Dec 4, 2015 at 9:33 AM, Nicolas George wrote:
> Hi.
[...]
>
> Substring parsers
>
> Parsers need to be able to operate on a substring, and stop when they
> reach the delimiters for the surrounding syntax. This is, in fact,
> rather easy to achieve.
>
> Think h
Hi.
This is a rather long explanation on ideas I have to replace the options
system with something better. I will not work on it before I have made
significant progress on de-recursiving lavfi, but I can still think of it
and mature its design while walking in the street or waiting for the subway.
13 matches
Mail list logo
