It makes me think something really big is coming......?
The other thread will be closed at its 4th birthday at the 13.02.2016, so lets start the second epoch here.
It is time to wait!
Like the name " !Epoch " best by the way.
!Epoch, for the next 4 years
already closed the other thread. It threw a wittle tantwum. -
- KVRAF
- 2681 posts since 25 Aug, 2003 from Bournemouth, UK
Honestly, a new thread isn't a bad idea. The previous one is obviously quite long, so I intended to shortly start an 'official' one.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
-
- KVRAF
- 2681 posts since 25 Aug, 2003 from Bournemouth, UK
Indeed. I hope jowen doesn't mind, but I will close this thread at that point just to keep things all in one place.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
-
- KVRAF
- 35295 posts since 14 Sep, 2002 from In teh net
'Epic' - which is what it becamejowen wrote: Like the name " !Epoch " best by the way.
-
- Beware the Quoth
- 33174 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
As long as it doesnt become Epochryphyal. 
my other modular synth is a bugbrand
-
- KVRAF
- 35295 posts since 14 Sep, 2002 from In teh net
Although it could be Eponymous, which would be somewhat amusing.
-
- KVRian
- 853 posts since 3 Nov, 2006 from Poland
We're doing THAT again?!
-
- KVRAF
- 1629 posts since 11 Dec, 2005 from Malmö, Sweden
-
- KVRAF
- 2681 posts since 25 Aug, 2003 from Bournemouth, UK
I've been doing some profiling tests, just to ensure that everything still ticks along nicely. On my test machine, a five year-old MacBook, and using the most heavyweight macro I've built - an ADSR envelope sourced from about 150 individual modules - I'm pleased that total CPU usage of this macro is only about 0.4%: pretty trivial in the grand scheme of things.
The most heavyweight built-in modules, the sequencers, tend to take a similar amount. Instances of both the poly and mono step sequencers, for example, have been seen to use about 0.2% each.
The other weighty module, the lua script, which is in itself fairly lightweight, depends largely on what the script is actually doing. There are plenty of lua optimisation tips around, using locals instead of globals, etc, and you can tweak the performance a little more by setting the required size of the memory pool available to each script. As a precaution, if the script appears to take too long - perhaps an accidental infinite loop - it will be forcibly stopped, to ensure that the graph keeps flowing. In this case, the forcible termination will appear in the console, informing you to fix your script! Lua scripts will also be forcibly terminated if they fail twice consecutively.
So, all looking good CPU-usage wise, and I've still several performance tweaks to implement post release.
The most heavyweight built-in modules, the sequencers, tend to take a similar amount. Instances of both the poly and mono step sequencers, for example, have been seen to use about 0.2% each.
The other weighty module, the lua script, which is in itself fairly lightweight, depends largely on what the script is actually doing. There are plenty of lua optimisation tips around, using locals instead of globals, etc, and you can tweak the performance a little more by setting the required size of the memory pool available to each script. As a precaution, if the script appears to take too long - perhaps an accidental infinite loop - it will be forcibly stopped, to ensure that the graph keeps flowing. In this case, the forcible termination will appear in the console, informing you to fix your script! Lua scripts will also be forcibly terminated if they fail twice consecutively.
So, all looking good CPU-usage wise, and I've still several performance tweaks to implement post release.
Architect, the modular MIDI toolkit, beta now available for macOS, Windows, and Linux.
