Feb 5, 2007 at 8:21pm
I had a performance question. I have some rather complex calculations using a bunch of sin/cos calls in expr objects. I know there are only 128 sin/cos values that I need. Is it faster to create a lookup table and just look up the results instead.
Also, if this is a good idea, do I just create a set of helper functions to create the table, then get rid of them in my patch (or disable them I guess since if they are not being used, they are no going to be using up space.
Feb 5, 2007 at 9:23pm
On Feb 5, 2007, at 1:21 PM, Rick Burnett wrote:
From a historical basis, the relative economy of table lookup vs.
You could write wavetable functions as separate patches – no need to
Personally, I’d love it if some C programmer out there created a
Feb 6, 2007 at 10:27am
On 5-Feb-2007, at 22:23, Steven Miller wrote:
Are you experiencing a performance bottleneck?
If not, I wouldn’t worry much about it. At least as long as you have
If you really only have 128 values and nothing in between, a lookup
> From a historical basis, the relative economy of table lookup vs.
There was a discussion here quite a while ago as to whether modern
At the time, someone (perhaps undersigned) suggested that somebody
>> Also, if this is a good idea, do I just create a set of helper
A common Max technique in this case would be something like loadbang-
Again, if your patch is performing OK, I would advise you not to muck
> You could write wavetable functions as separate patches – no need
I had the impression that any GENxx routines *not* provided by
You might also have an interesting discussion about what constitutes
(*) Sorry Luke, I can never remember the ‘correct’ capitalization.
————– http://www.bek.no/~pcastine/Litter/ ————-
Feb 7, 2007 at 4:53pm
Thanks for the responses. I think the problem I am seeing is just the way I am updating my UI, so I am rethinking how I have implemented it. Even with a table I think it would be slow since I am doing a lot of calculations that I could re-use if I rethink my design.
You must be logged in to reply to this topic.