TRAC migration: propagating ticket status from TRAC

file:aNBhJqsDqr5yofdmr6bg7m

Here is a little patch that I put together. For every device it prints a report like this

Device #1 (0 in, 2 out)
 Name                        = Built-in Output
 Host API                    = Core Audio
 Default low input latency   = 0.0100
 Default high input latency  = 0.1000
 Default low output latency  = 0.0100
 Default high output latency = 0.0201

Could this be something acceptable? Or a different display format should be used?

@wspinelli

Thank you. The purpose of this test is to output data that we can combine into a survey of all host APIs. For this reason I think it would be best to have tabular output with one device per line.

For the table format I think either CSV or Textile (assembla) table mark up. Textile tables are just | separated values instead of comma separated (see: http://redcloth.org/hobix.com/textile/quick.html#tables). It's not necessary to vertically align things, although of course that would be nice. My personal vote is for the Textile format, then we can paste the output straight into the Wiki.

I think that you have the correct fields. I would like to see the columns in this order:

1. First column with an X in it if any default latencies are zero, otherwise first column is blank.
2. Device number
3. Host API
4. Name
5. x in
6. x out
7. .. default latencies

I hope that is OK, if you have a better idea, please shout out.

@rbencina

So be Textile tabular format with vertically aligned columns =)
Using a format compatible with the wiki is for sure the best choice