From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
MyCo wrote:
infuzion wrote: I was reminded when I tried to run this OSM. A large OSM (900k), so I expect it to be slow to open, but it became very slow to go inside the module, about 5 seconds, 2-3 seconds to open the menu... almost impossible to peek around since it was lagging so much. I gave up & closed it before it would crash.
Well this has nothing to do with SM itself, in this case it's because the wave player is buggy. There is a wave with more than 200.000 samples, and the player window draws 20.212 points and lines on the screen !!! The best way to draw a wave is to reduce the points that have to be drawn to less than the view width in pixel.
And there is another bug in the wave drawing part, the connection between "wavearray" and "get Length" is wrong (samplerate is connected to array length).
aliasant ·
I "fixed" the waveplayer so you can test if you havnt done this already.
infuzion ·
aliasant wrote: I "fixed" the waveplayer so you can test if you havnt done this already.
Oh I see; you used the Resample Float Array in the DrawWave. Good call, thanks aliasant! Why isn't this in the WavePlayer already?
BTW, I hope the released version doesn't have all your Int & Float primitives that are left laying around. 😉
I think you can bypass the Int to Float Array if you change the Loader output connector type from Int Array to String. Though I used Text as a lag-causing workaround myself, I prefer to workaround that workaround.
aliasant ·
No idea why it isnt in there already. Not my waveplayer 🙂
There are probably a lot more stuff that can be made smarter in that one but I only changed the things that Myco pointed out.
malc ·
I'll get that updated in the next release.
Thanks for the update aliasant 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker