Ok, then define realtime. This kind of stupid test is what make companies add stupid features, just to look better in a test.There is no bad faith. The subject is about real time and if your product doesn't excel in that specific area, I'm not going to hide it, although fruity offline rendering is top notch, so why bother?
I'll probably end up allowing the user to switch the sinc interpolator realtime in FL. Result for the user? None, he will be able to play 2 notes, so will switch it off. Result for us? For the product to look better in a stupid page.
A good test would show quality vs CPU vs ram in a chart. You'd then let the user switch what matters the most to them. But 'realtime' is stupid - it doesn't compare CPU at all. You could have some good interpolators already listed in your 'realtime category', yet they might just eat too much CPU in a complex project, so not be that much realtime.
If you want to promote your tests, just do them right. It's not that hard to check the CPU usage of something. It's not hard to understand that everything is a CPU vs quality vs memory usage tradeoff, and that all 3 parameters matter.


