LMMS • Forums

Sounds generic, right? I've been using LMMS on my current computer for almost a year now, and just now I've started to get random CPU spikes When I have an instance of ZasFX loaded. The spikes cause clipping during playback, which is annoying , but not computer threatening. Anyhows. Does anyone have any ideas on how to fix this? My specs
LMMS 1.1.3
Asus X555,
Intel i3-5010U
12 gigs of RAM
Windows 10 (64 bit,) Version 1511.
Also, I'm not sure if this is connected, but i also just installed flux
I'd appreciate your help. Thanks!

mrlmmsguy wrote:I've started to get random CPU spikes When I have an instance of ZasFX loaded. The spikes cause clipping during playback, which is annoying , but not computer threatening.

I went through a similar problem to this, a few years ago, with ZasFX on Lmms 0.4.13 64 bit on Win 7 64 bit.

At first I think thought you had a cruddy computer or something causing the problem, that's interesting. Maybe it's time to clean your computer? Both hardware and software. Idk really, turn it on and off again, see if that helps.

That last parts a joke.

[quote="mrlmmsguy"] The spikes cause clipping during playback, which is annoying , /quote]

So a coups of days has past.. What is the status?
What i think it looks like, is that you have invoked auto-save, but that should have no connection to zasfx, even though zasfx is indeed the instrument that write the largest amount of data in a save-event..
So check if you have auto-save invoked (Settings | performance-

If this is not the case: What zasfx preset did this start with?

musikbear wrote:

mrlmmsguy wrote: The spikes cause clipping during playback, which is annoying , /quote]

So a coups of days has past.. What is the status?
What i think it looks like, is that you have invoked auto-save, but that should have no connection to zasfx, even though zasfx is indeed the instrument that write the largest amount of data in a save-event..
So check if you have auto-save invoked (Settings | performance-

If this is not the case: What zasfx preset did this start with?

Well, the status is, there's still a problem. I"m still getting CPU spikes. It does not seem to be limited to a single ZasFX preset. I haven't tested them all yet, but the problem appears in multiple files. And no, I do not have autosave enabled. Despite running a full virus scan, cleaning my temp files and registry (except for OS backup .dll's) I still have the problem.
Can I run a backtrace? Is that even a good idea?

mrlmmsguy wrote: Well, the status is, there's still a problem.

Hmm.. and you also see this if you open old projects?

Then theres this 'flux' stuff..
In a nutshell WHY?!
..But i cant see any reason that an issue with flux, only should result in spikes with zasfx.

Backtrace, well if you have a resent point, but somethings almost always missed

But an issue like this one need to be broken down.
So the first thing your should do is to create a new project, and add native zasfx from Instrument-plugins NOT My-presets!
What then?
Are the spikes present only during playback, or also in idle?

So I loaded a init instance of ZasFX in a new project and experienced no issues..... Hrmmmmmmm.
Spikes are only occuring during playback

mrlmmsguy wrote:So I loaded a init instance of ZasFX in a new project and experienced no issues

oK
So this is now what you need to do:
Open a problem project
Save each and every preset NOT only zasfx!!! -to a new folder : 'problems'
close lmms
open the init project with NO spikes

Import ONE preset from the 'problems' folder
Play -Are there any spikes?
new import

This should let you find the preset that has the issue

Had a new file. Imported "problem presets" saved in a new folder... No playback disruption, and I had four instances of ZASFX running. GGRRRRRR. I'm really getting stumped about this. If this provides any clues. my keyboard response time playing a game on Steam also slowed down at the same time as the ZasFx spikes... Upgraded the runtime priority, didn't fix anything either.

Update: Once I disabled f.lux, the spikes went away. Odd. very odd. Perhaps I should file a bug report....