id	summary	reporter	owner	description	type	status	priority	component	version	resolution	keywords	cc	blockedby	blocking	reproduced	analyzed
1020	tools/graph2dot appears to be using different graph parser	jamiel		"When trying to debug a graph line, I am getting different results from graph2dot than I do from the main ffmpeg source.

Example:

{{{
$ ffmpeg -i INPUT -vf ""[in] split [no-color], fifo, [with-color] overlay [out]; [no-color] fifo, select='gte(t,10)*lte(t,20)' [with-color]"" output

*snip*
Press [q] to stop, [?] for help
frame=  480 fps=  8 q=-1.0 Lsize=    6002kB time=00:00:19.91 bitrate=2468.8kbits/s

$ echo ""[in] split [no-color], fifo, [with-color] overlay [out]; [no-color] fifo, select='gte(t,10)*lte(t,20)' [with-color]"" | ./graph2dot -o graph.tmp

[fifo @ 0x804dad0] 
[fifo @ 0x804e390] 
Input pad ""default"" for the filter ""Parsed_split_0"" of type ""split"" not connected to any source
}}}
"	defect	closed	normal	FFmpeg	0.10	invalid	graph2dot, tools				1	1
