[FFmpeg-trac] #1922(undetermined:closed): Broken or incomplete parser for filters

FFmpeg trac at avcodec.org
Fri Nov 16 17:41:34 CET 2012

#1922: Broken or incomplete parser for filters
             Reporter:  burek        |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:  invalid
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0

Comment (by Cigaes):

 Replying to [comment:3 burek]:
 > @Cigaes: I'm not sure why any of those 2 need escaping?

 You missed something: the second example is not a single filter, it is two
 filters, one printing the "8-(" smiley, the other printint the "8-)"

 > Making the parser aware of this is as simple as implementing one of
 several well known algorithms (for which there is also a sample code
 available for most popular programming languages):
 > I believe this won't be as complex as it looks like, because people have
 solved this kind of a problem a long time ago and it would be wise to not
 reinvent the wheel.

 It is not as simple as you make it: filters expect a flat string, and
 parse it themselves. More and more use the options system, but some use a
 custom parser.

 Changing the way it works constitutes a big API change, and can not be
 disregarded as "as simple as" anything.

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1922#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list