Apologies, Paul! I've been distracted by sorting and working on something else, so I hadn't made a full updated source available.
I have now, at
http://jcgl.orpheusweb.co.uk/temp/NewWandF.zip
This contains my current source code and a copy of the PolarFooter used for the veusz output.
Note two details. Firstly, it now doesn't list every time a value falls off the range of the histogram plot. Just summarises the count of these if they happen. (None of the stats are affected, just the histogram plot.) Secondly it now lets the user choose how many rotations to plot on the Polar Veusz file. Normally, the user should just say '1.0' and get one full rotation plotted as this avoids multiple turns overlaying and making the pattern hard to see. But plotting many turns lets you see if the pattern is consistent and/or if the rotation rate is fast or slow. (The plot assumes exactly 33.3rec RPM.)
It limits the number of rotations to 5.0 to avoid accidents. But the user should ensure that this value plus the start time don't run you off the end of the input file!
I've been meaning to add other details to the polar plot so it shows the input file name, the rms W&F and tells the user that the red blobs are raw and the blue ones AES weighted, so haven't updated the complied full ROX app yet. Aim to, but want to get on with something else.
Yes, I expect stereo input. I record / capture stereo by default. It also means I can do a frequency measurement on each channel and then average them together. This can slightly improve the accuracy if the noise on the two channels is uncorrelated or antiphase.
Hope this helps.