Just updated to …
zyncoder: vangelis (36691b3)
zynthian-ui: vangelis (0e509b5)
zynthian-sys: vangelis (da69c9e)
zynthian-data: vangelis (305b301)
zynthian-webconf: vangelis (d811ea6)
after rebooting, the UI lags horribly.
Somebody else experiencing this issue?
Regards
Add-on info: during startup, the chains are build, but screen seems to be laggy with restoring states…
and fluidsynth shows very big issues in changing and selecting presets (very laggy, ~20s and more).
Are you saying that there is a delay between a user action, e.g. select menu and the corresponding reaction, e.g. menu showing? This is what I would consider lag. Or are you saying that things are taking longer than you expect to complete? Please provide example snapshot and steps to reproduce. I don’t know what the issue is with your descripton. I don’t know what you are doing, what you are seeing and what you are expecting to see. I don’t know if any potential issues that I may observe are similar to what you are experiencing.
[Edit] But, assuming what you are describing is that adding an engine, e.g. fluidsynth takes tens of seconds and results in an error in the log, then it seems to be caused by this commit. which disables echo and breaks control commands.
[Edit] I have reverted this change in vangelis. I will let @jofemodo revisit this. I am not sure why the change was made but it results in the prompt not being detected when recalling preset in fluidsynth or when doing some other things in jalv.gtk.
I experienced a general operations slow down, a huge amount of time in loading snapshots and knobs stop working after selecting a preset in a synth. Can’t use midi learning, too.
Working again as normal…
Well, @riban, it was difficult to find, what was wrong. There was no error in the log’s, just a very slow reaction on changing chains, and fluidsynth presets. Also other lags.
I wanted to investigate further, but it was too late yesterday, hence I just asked into the forum for someone seconding my observations. This is not the smartest style, I know.
Sorry for being unprecise in this, but it must have done something with the update from changing from commit 55628871ef7858cf623dde97803ef3dc0675cc52 to the following ones on Dec, 18th.
I forgot to mention this more precise input you missed.
With the reverted commit it works again, thanks.
Regards