Quote:
Originally Posted by Justin
I saw an odd issue testing on armv7l linux: when the UI isn't visible the CPU use doubled. I'm baffled by this. Is there anything in the ReEQ code that detects when the @gfx code runs and changes the processing depending on whether it has run recently? If so can you point me in the right direction to see why the slowdown happens?
|
That is odd. There shouldn't be any dependencies between inner DSP code and the UI code. There's shared state of course for the filters and modes but nothing that would give the effect you're seeing as far as a know.
You could try replace the @sample section with some idle work that isn't related to the rest of the code to see if still happens.