Repository navigation
FluidEQ uses a lot of memory #73
Answered
by
StartSWest
StartSWest
asked this question in
Q&A
|
Task Manager shows FluidEQ using several hundred megabytes. Where it goes. Raised in issue #53. The answer is below, marked so it shows first. |
Answered by
StartSWest
Nov 14, 2026
Replies: 1 comment
|
The sound itself is processed by the engine inside Windows' audio service, which is small. Most of what Task Manager shows is FluidEQ's window: the graph, the analyser and Scenes. Processes in the actions menu shows what each part of FluidEQ is doing. Using less is being looked at in issue #53; add your numbers there. |
0 replies
Answer selected by
StartSWest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The sound itself is processed by the engine inside Windows' audio service, which is small. Most of what Task Manager shows is FluidEQ's window: the graph, the analyser and Scenes. Processes in the actions menu shows what each part of FluidEQ is doing. Using less is being looked at in issue #53; add your numbers there.