When DEBUG_BIN_TO_DOT_FILE() is used with DEBUG_GRAPH_SHOW_CAPS_DETAILS, the caps are put in the DOT file by simply taking the to_string() of the caps and replacing ',' with '\n'. This is a problem because commas aren't only present between caps field name but also inside values such as { 1234, 4321 }.

When the caps have not been negotiated and you are trying to figure out why by looking at the caps in the DOT file you will see this terribly difficult to read block of text:

    audio/x-raw-float
      rate=(int)[ 1
      2147483647 ]
    channels=(int)[ 1
      2147483647 ]
  endianness=(int) { 1234
         4321 }
width=(int)64; audio/x-raw-float
    rate=(int)[ 1
      2147483647 ]
    channels=(int)[ 1
      2147483647 ]
  endianness=(int) { 1234
        4321 }
    width=(int)32;
    
    
You will also notice that none of the lines start at the same place because the text is centred.

My patch changes the font to monospace (so we can make things line up like in the terminal), and then outputs the caps in the same style as gst-inspect-0.10 does. The same caps above will now appear like this in the DOT file:

audio/x-raw-float
             rate: [ 1, 2147483647 ]
         channels: [ 1, 2147483647 ]
       endianness: { 1234, 4321 }
            width: 64
audio/x-raw-float
             rate: [ 1, 2147483647 ]
         channels: [ 1, 2147483647 ]
       endianness: { 1234, 4321 }
            width: 32


Other information: