CtrlrX and panels are sometimes lagging/blocked for 10s...

[dobo365]

I guess this will be a difficult one...
I'm busy to convert my panels to 5.6.34
I sent my Pro-800 editor to 2 key users and they reported sometimes a lag (panel blocked for 10s) in the librarian where I'm using list boxes.
Could be the synth, the list box, the editor...
As I don't have the synth and that I have been abroad for one month, I didn't check further.
Now, I'm back and on another PC, I'm using CtrlrX in edit mode to update all my patch mappers. Once in a while, CtrlrX is also blocked for 10s. It can be when clicking a menu or selecting a component or editing a prop...
I will watch it closer.

I'm afraid there is an issue somewhere...
Do you experience the same?
Could be on my own versions only... I don't have all changes you did.

[damiensellier]

Salut Dominique,
Essaie de voir avec la toute dernière version, y a tellement de choses corrigées.

Sinon ca lag comment (ralentis, bloque totalement...)?
Quelle version c'est ?
As standalone or plugin?
PC or mac?

I noticed the autosave in standalone can freeze the gui for a second because it uses saveState() to disk which can be resource demanding. Maybe it's that maybe not, start by disabling the auto save preference.
note that when exporting an instance it will set it to true by default.

I noticed that if you can avoid any global outgoing message delay that's always better (0ms being the best) because it loads the buffer.

Sometimes ctrlrx freezes a lit bit as vst when the daw is doing its project autosave, can't fix that.

On mac there's a shutdown delay when closing the plugin or standalone (not AAX) to help with the saveState process on closing.

10s??? this is very long, I never experienced that but when debugging in debug mode with faulty code. check if your plugin is in release mode.

check for sleep( in the source code and also in your panel lua scripts.

It could also be something related to OpenGL vs native graphics rendering.

check if you have a timer unstopped running on your panel.

Bon weekend!

[dobo365]

Salut! Je vais t'écrire plus longuement perso.

For my key users, it happened with a standalone panel.
I thought it was specific to that panel but I experienced it by myself when editing another panel...
Never had that in 5.3.201...

This is on PC. I don't use sleep().
I will try disabling the Autosave (first get the lag then disable then continue the work and see if gone)

[dobo365]

OK...
I check the Autosave and it is set to 300s.
I have been busy to edit my panels then got the issue. I started a clock and indeed got the next freeze close to 5 min later...
It is indeed blocking CtrlrX for just 1 or 2s but this is not OK.

I will check what I have on my old Ctrlr 5.3.201 but this is on another PC.
I never felt a stop due to Autosave. Did we change something to make it slower?
If I disable it, what are the alternatives?
Is it saving the state of the panel? How can that be triggered via a Lua script?
I guess it is a companion to SaveStateData()

I will also check Autosave on my standalone exports (from 5.3.201 and from 5.6.34)

Thx for the tip!

[damiensellier]

Hi Dominique, je prendrai le temps de te répondre à ton mail dans la semaine quand j'aurai un peu plus de temps ;)

Pour le probleme de freeze ca va dependre de la quantité de données que le pannel a à enregistrer en xml dans e fichier du pannel et peut être aussi ctrlrx.settings.

Le problème vient du fait que cette sauvegarde auto utilise le thread principal du plugin et donc stop toutes les autres activités jusqu'à ce qu'il soit libéré. La solution c'est de faire faire cette tâche en parallèle par un autre thread.

void CtrlrStandaloneWindow::saveStateNow()
{
    _DBG("CtrlrStandaloneWindow::saveStateNow");

    if (ctrlrProcessor != nullptr && appProperties != nullptr)
    {
		appProperties->getUserSettings()->setValue (CTRLR_PROPERTIES_WINDOW_STATE, getWindowStateAsString());

		MemoryBlock data;
		ctrlrProcessor->getStateInformation(data);

		if (data.getSize() > 0)
		{
			ScopedPointer <XmlElement> xml(CtrlrProcessor::getXmlFromBinary(data.getData(), (int)data.getSize()));

			if (xml)
			{
				appProperties->getUserSettings()->setValue (CTRLR_PROPERTIES_FILTER_STATE, xml);
			}
		}
	}
}

Il faudra que je mette ça à jour avec addJob() en listant les threads au préalable avec getThreadPool()

en attendant si c'est ennuyeux tu peux juste retirer le autosave dans les préférences et sauver manuellement.