Sylvain,
 
Ok, good to know.

I need to come up with a good way to pass "options" to fosphor to be
able to configure theses things at runtime.


That would be useful! Given how much I use your tool for real work, I'm willing to contribute; do you look at pull requests on the github mirror? Here are some other things I have often considered plumbing through as options:
1. FFT length. It looks like you have a length 512 FFT kernel in fft.cl already, but I think its unused. A few other FFT sizes might be useful too for adjusting resolution bandwidth. With what you have, several other powers of two should be implementable simply.
2. Waterfall time length. Requires some GL tricks to change the texture size, or internally render at some fixed size and always crop and/or downsample the texture to show the amount of time the user requested.

Thanks for the tips that resolved the issue!

--
Raj Bhattacharjea, PhD
Georgia Tech Research Institute
Information and Communications Laboratory
404.407.6622