Best way to optimize a primary sequencer?
Im currently at a very early stage of development of a new idea for a sequencer.
Attached to this post is a brief ensemble of a single structure that im developing.
It works as i expect it. However, im gonna need lots and lots of the same structure.
And when i replicate the macro multiple times the cpu usage can go to up to 30% Which is really undesirable.
My question is. which of the primary modules that im employing would be the most cpu demanding? Can you think of a simple way to optimize the thing?
Also, if i was to do this in core... would that give me a noticeable difference?
And if i was to do it... what would be a good starting point? i've never used core before so the thought of jumping into it for this sequencer is daunting, but would do so if it is going to pay in big cpu savings.
Thank you in advance.
You guys are awesome. This community has been very helpful.
I really appreciate all of you fine folks who take time to reply. For now im the annoying guy who has questions all the time, but please know that i really appreciate all of your help.
- All Categories
- 21 Welcome
- 2.1K Hangout
- 85 NI News
- 1.4K Tech Talks
- 2.3K Native Access
- 13.4K Komplete
- 1.3K Komplete General
- 2.8K Komplete Kontrol
- 3.8K Kontakt
- 3.5K Reaktor
- 327 Battery 4
- 596 Guitar Rig & FX
- 317 Massive X & Synths
- 706 Other Software & Hardware
- 4K Maschine
- 4.9K Traktor
- 4.6K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators