BrainModular

I have a Hollyhock workspace with 5 racks, two of which require 16 identical base copies of two similar patches, actually the problem patch was a copy of the non problem patch and then modified for specific operations with external MIDI hardware and some slight audio mixing modifications to suit the instruments input to the rack, but really the base functionality of both patches are the same and differences are minimal.

With the problem patch, when I load 16 copies into a rack (only one active at any time, similar to Usine 5 grid mode) the ib becomes very sluggish and does not even respond until I deactivate/activate the patch, and then it is about a 1/2 second to refresh. All MIDI data and audio is acting normally through the patch. On the other hand, the non problem patch loaded 16 times is snappy as can be, with the exception of a bit of lag when switching visibility from one active patch to another, not a big deal for me really. Also the non problem patch is responsive when loaded 16 times into the same workspace as 16x the non responsive one so it is not a cpu issue or such.

Hoping for a nudge in the right direction to help figure this out, I am really hoping to be using this setup to get ready asap for a show coming up way too soon but this lag thing is unbearable..

Cheers!

not easy to help this way

any chance for a polyphonic version of this patches..?

if not , can you use the report page and send us the LogUsine.log ( run a new instance of Usine, run the workspace and recreate the problem, then copy the log file)
you can also join the workspace ( delete vst before if needed)

I seem to have found the solution. Repair id's on original patch before loading multiple copies of the patch. Actually, I did repair id on all patches in workspace, including I/o device patches so perhaps that helped also.
The poly suggestion is interesting, however if I cannot individually save or reload different versions of each "voice" then it does not work in my situation. Perhaps an interesting idea for a future feature?

If I have any further issue with this, I will file a report as suggested. Thanks!

repair IDs does destroy all PM presets, correct?

It didn't in my case, but I only have two very basic preset variations in my root patch. I am curious to know a bit better how this works and what the specific risks to presets would be when using the repair id option.

One last little detail I would like to sort out whether it matters or not is when I load my patches I get the trace message "Warning: The container or popup module doesn't exist!"
I have looked everywhere, but can find no module that points to a non existant popup or container. Could this perhaps be a glitch from importing part of the patch from v5?

About the warning message here a tip:
right click on your patch and open it with a text editor, then use the search engine (generally [CTRL+F] and look for the words container and pop