From the original SynthMaker forum (2004–2014), with its members’ names and dates.
datsound ·
hi, the synth i am working on gets 28% CPU on SM1 and 41% on SM2.
also here is a pic of the task manager showing a phantom 70% of one core being used and 10 of another, when sm only shows 10% on one core. the 70% reading only occure while SM1 was open. the performance tab had 70% but the processes tab read 90% idle.
Mo ·
You'll need to post more info, a schematic and how to replicate it would help. I see no difference in the cpu use with the example synth and others.
datsound ·
It's an FM synth, it must be denormals somewhere that are being handled differently in the new engine. i will try to find what it is but it may take a while as there are lots of modules, will say when i find what is causing it.
aliasant ·
Just started testing SM2.0 and Redraws is using a lot more cpu. A LOT.
So if you have moving guis / redraws in your schematic that might be the problem. I think I saw another thread about redraws being hungry in SM 2.0 and Flowstone as well ....
infuzion ·
aliasant wrote: Just started testing SM2.0 and Redraws is using a lot more cpu. A LOT.
So if you have moving guis / redraws in your schematic that might be the problem. I think I saw another thread about redraws being hungry in SM 2.0 and Flowstone as well ....
A few test OSMs would be great. If others see the same exact issue, then please open a bug so it can be fixed in SM2.0.1
sunsynth ·
Redraws is using a lot more cpu. A LOT.
I can confirm this behavior 2...
Only one big slider with slider 'region only' redraw plus a 1 Grid blinking led eats up mucho CPU than v1.17 while dragging/moving 🙁
trogluddite ·
Same here - tested Soopa Loopa in SM2 with all automated knobs running - getting about 40-50% more GUI CPU use. exe and vst exports have the same behaviour, though not quite as extreme (maybe 20-30% more CPU - so maybe the SM editor interface is eating some extra)
aliasant ·
Found a clu but I cant give a schematic.... but
I think it has to do with window sizes. One example is the Bode Plot someone just shared.
I dragged it into my already busy schematic and emediatly the sound started stuttering. I went into the Bode Module and lowered the window size to 256 and checked cpu usage with Process Explorer and it emediatly dropped to a low level... I then Raised it step by step and I could see the cpu usage climb in exponential but very small steps but over 1024 it started getting worse and when I got past 4096 the stuttering came back. I then had a cpu usage of about 11% Took it back down to 4096 and cpu emediatly dropped to half that. About 5.5% and no stutter.
Weird though that I hadnt even connected that Bode Plot and I have nothing Poly in my schematic since its an effect. Sounds like a loop somewere but to be honest I think I had this in SM 1.1.7 too but not as bad. My guess is that if you create a new empty schematic and drop a Bode Plot into that one nothing will happen. Its one of those "the more the happier" scheemes 🙂
datsound ·
I've just found a program that can graph the performance of a task like synthmaker.exe, http://www.fallenstar.net/autoit/graphxexplorer.jpg
it's abit basic as it isnt real time, i hope someone knows a better program for monitoring sm.exe? it would be better to change the graph size and the polling rate, am working on it.
to run it, download the 2 au3 files in attachments, and also this program http://www.autoitscript.com/autoit3/downloads.shtml
when you run graphx.au3 a window appears with a task list, you have to close it and then a timer will appear in the tray menu.
Thanks to Weaponx http://www.autoitscript.com/forum/topic ... r-process/
XoechZ ·
I have noticed the same. Plugins made with 2.0 use more CPU power and have a bigger file size. Bad update so far... :-(
infuzion ·
XoechZ wrote: I have noticed the same. Plugins made with 2.0 use more CPU power and have a bigger file size. F_____ bad update so far... :-(
I also wish 2.0 was tested out better, you don't need to cuss to emphasize your point please.
datsound ·
XoechZ wrote: Fucking bad update so far... :-(
i dont think that saying that will encourage the SM team to fix the new version faster.
Dozius ·
aliasant wrote: Weird though that I hadnt even connected that Bode Plot and I have nothing Poly in my schematic since its an effect. Sounds like a loop somewere but to be honest I think I had this in SM 1.1.7 too but not as bad. My guess is that if you create a new empty schematic and drop a Bode Plot into that one nothing will happen. Its one of those "the more the happier" scheemes 🙂
The bode plot is set to 'auto-draw' by default, so it's continually redrawing the plots even with nothing hooked up. I didn't bother trying to make the auto-draw very sophisticated since it's just an analysis tool you drop in for a few minutes and then take out.
You can switch it off and use the manual trigger input instead. That way it won't consume CPU unless something triggers the redraw.
XoechZ ·
I´m sorry.
aliasant ·
Dozius wrote: aliasant wrote: Weird though that I hadnt even connected that Bode Plot and I have nothing Poly in my schematic since its an effect. Sounds like a loop somewere but to be honest I think I had this in SM 1.1.7 too but not as bad. My guess is that if you create a new empty schematic and drop a Bode Plot into that one nothing will happen. Its one of those "the more the happier" scheemes 🙂
The bode plot is set to 'auto-draw' by default, so it's continually redrawing the plots even with nothing hooked up. I didn't bother trying to make the auto-draw very sophisticated since it's just an analysis tool you drop in for a few minutes and then take out.
You can switch it off and use the manual trigger input instead. That way it won't consume CPU unless something triggers the redraw.
Lol Right Thanx. Remember that now but the cpu usage is still way out there and it is related to the size iof the window Im sure. I have had similar problems with other parts that use eg. Mono to Graph or Mono to Float.
datsound ·
i hope that they have seen it and that they will update in the next couple of weeks with cpu levels on the individual modules. i thought that graph program i found was brillant 😍 but erm. perhaps not.
infuzion ·
datsound wrote: i hope that they have seen it and that they will update in the next couple of weeks with cpu levels on the individual modules. i thought that graph program i found was brillant 😍 but erm. perhaps not.
Best bet is to send the OSMs to "[email removed]"
infuzion ·
I emailed support about this a few days ago, still nothing... anyone else?
Mo ·
Yeah, seems to be related to the issue reported here too: http://www.dsprobotics.com/support/view ... ?f=2&t=147 Not much response so far. Hope it means they're hard working to fix it..?
MichaelBenjamin ·
the redrawing is indeed much more excessive with cpu, when exported its a bit less but still more than 1.1.7
electrogear ·
I realise this is a bit of a useless post for the devs but CPU seems a lot lot higher in general, even simple schematics with a few sine waves/envelopes and a tick 100 are giving me >10% CPU... can't believe it...
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker