(If it makes sense) The idea would be to add 2 modes for running JS effects:
- secured mode (as JS effects are running today: with REAPER's internal checks enabled)
- boost mode (all REAPER's internal checks disabled)
As a drawback, with a "bad" JS, the "boost" mode could of course crash REAPER. But that should never be the case for experienced coders and, anyway, you can already crash REAPER today in a "live with it" way (e.g.
the 666th bug).
Of course, this would be up to the user to choose the mode (depending on how much he trust the JS) and not specified in the code!
EDIT: as suggested by shakey.oberon, perharps it could work a bit like the "buggy plugin compatibility mode"
Discussion thread
Remark: after digging into JS, the thing I saw that mostly impact JS performances (CPU) is its array management. This has been explained by schwa:
Quote:
Originally Posted by schwa
JS is compiled. But it will usually be slower than native compiled code because it needs to do things like bounds checking to avoid a bad user JS crashing Reaper.
|
it's that comment that inspired this FR..
Subscribe to this issue
01-22-2010 07:21 AM
