Post by mindtraveller on Mar 29, 2016 18:32:15 GMT 1
Hi,
after a long time I finally tried to compile SE_SDK3 modules with codeblocks again and this time it worked (on a new computer).
However I recognized that the Gain example, for which I only changed the name, uses more CPU power than the gain3 in SE.
The factor is about 1.5 - 2 times more CPU.
I wondered whether the visual C++ compiler might produce more efficient code than the gnu compiler, or are there some special operations like SSE instructions used for the synthedit native modules? Does anyone have experience with this and might maybe have some tips regarding optimized compiler settings for SE modules, etc.?
I'm particulary concerned about performance, because better performance means more complex synthesis options means weirder sounds :-)
Greetings,
Mindtraveller
after a long time I finally tried to compile SE_SDK3 modules with codeblocks again and this time it worked (on a new computer).
However I recognized that the Gain example, for which I only changed the name, uses more CPU power than the gain3 in SE.
The factor is about 1.5 - 2 times more CPU.
I wondered whether the visual C++ compiler might produce more efficient code than the gnu compiler, or are there some special operations like SSE instructions used for the synthedit native modules? Does anyone have experience with this and might maybe have some tips regarding optimized compiler settings for SE modules, etc.?
I'm particulary concerned about performance, because better performance means more complex synthesis options means weirder sounds :-)
Greetings,
Mindtraveller
