Diagnostics module

[Mike]

If you follow my tweets (http://twitter.com/#%21/MikeVersteeg) you know I have started work on the Diagnostics module as I need it to show some graphs to write the audio mixer. While at it I figured I'd add graphs for the individual CPU core usage. Problem I am running into is that displaying graphs for 8 cores, let alone 16 or 32, is taking up a lot of space (see below). Any suggestions for a better presentation?

http://forum.vidblaster.com/attachment.php?attachmentid=332&stc=1&d=1319712034

[zenvideo]

If you follow my tweets (http://twitter.com/#%21/MikeVersteeg) you know I have started work on the Diagnostics module as I need it to show some graphs to write the audio mixer. While at it I figured I'd add graphs for the individual CPU core usage. Problem I am running into is that displaying graphs for 8 cores, let alone 16 or 32, is taking up a lot of space (see below). Any suggestions for a better presentation?


It's difficult to see how you could make it much smaller and still see as much information. The only thing I can think of it to overlay the traces for multiple cores and render them in different colours. Maybe in sets of three, to stop it getting too complicated, and to keep the colour separation clear (eg 1=red, 2=green, 3=blue), but that alone would cut down on the space required (eg. by a factor of three). You would possibly lose the colour separation where they all overlapped, but that might not matter because it would be obvious that they were all at the same level (eg idle), and you would still see the parts where they were at different levels, and which core was it which level. If you stuck with the RGB primary colours and added them together at each point in the trace, then you would still get an unambiguous display as each colour mix would give a clearly identifyable colour. (eg if 1 & 2 were at the same level, in my RGB example, the trace would be yellow. All three at the same level would produce white.).

[Tony]

have them see more cores by adding an advance button or only show active cores

[weconverse]

Sorry no. And I don't see any major problem with it's size, it is intended for debugging purposes anyway.

Are you considering that VidBlaster marks important events on the time scale, eg. selecting a module or starting a streamer?

[Mike]

Interesting idea, but that would take up even more space?

Mmm... I could make a timeline you can move and then sync that with the log?

[weconverse]

Oh, I didn't see the Diagnostic as a module, rather a free floating window like the CPU usage thing. As a matter of fact, that is how I think it should be implemented.