Opened 5 years ago

Closed 5 years ago

#1020 closed defect (invalid)

tools/graph2dot appears to be using different graph parser

Reported by: jamiel Owned by:
Priority: normal Component: ffmpeg
Version: 0.10 Keywords: graph2dot, tools
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: yes

Description

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

Change History (2)

comment:1 Changed 5 years ago by Cigaes

  • Analyzed by developer set
  • Reproduced by developer set
  • Status changed from new to open

graph2dot expects a self-contained graph, while the -vf option expects a graph with an input and an output. You can add the input and the output to the graph you give to graph2dot:

echo "nullsrc [in]; [out] nullsink; ..." | graph2dot

You can use the movie input instead of nullsrc to have the exact properties of the video you are filtering.

comment:2 Changed 5 years ago by saste

  • Resolution set to invalid
  • Status changed from open to closed

Closing the ticket as this doesn't seem a valid issue.

Note: See TracTickets for help on using tickets.