Additionally, somewhat related to this and other recent developments, I propose removing the options "sample-exact controllers" and "anti-aliasing oscillators" from the export dialog. The reason being:
- Anti-aliasing oscillators currently does nothing. However, we already have the implementation for bandlimited oscillators, but I think it's better to leave it as a per-instrument selection, not something that is dependent on an export setting. It's more user-visible and simpler that way. - Sample-exact controllers... I fail to see any situation where, even when sample-exactness is possible, one would NOT want to use sample-exact controllers. If you want your controller to be quantized at the exact same rate as the period size, then... I don't know, use a bitcrushed waveform in the LFO controller? I think any such use case is extremely rare and not worth a specific setting. Instead, I think we just implement sample-exactness for those models that benefit from it - eg. volume knobs, fx mixer faders - and I think if I manage to implement my idea of a structure where values can be fetched from models in buffers/arrays, it'll be entirely feasible to use sample-exactness constantly even in realtime, so there's no reason to turn it off. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
