FS#11219 - FFT: add support for input visualization.
Opened by Delyan Kratunov (archivator) - Monday, 26 April 2010, 21:16 GMT
Last edited by Paul Louden (Llorean) - Tuesday, 27 April 2010, 21:04 GMT
|
DetailsInitial support for showing input in the fft plugin. Now, on targets supporting recording, instead of quiting when no track is playing, fft starts monitoring the audio input (using the settings under Recording Settings).
The first patch is just the functional changes, the second patch fixes the indentation of the entire file. I'm not sure if it works at all since I don't have a device that can record. |
In any case, this is arguing semantics and that bit is easiest to change, really.
* Remove a blocking splash from the recording codepath! (fixes input mode slowness)
* Rename "Recording mode" to "Input mode"
* Add a brief overview of the plugin for future reference
Patch 1 is functional changes only, patch 2 fixes the indentation as well.
Maybe "Monitoring mode" is better?
I forgot to mention that this patch needs testing on devices *without recording support* (to check that my #ifdefs haven't broken basic functionality). Unfortunately, there are only 10 of these and it's too late for me to figure out which ones have what.
I can't think of anything else to test, so I leave this patch in your capable hands :)