New Automation problem

[Pianoscope]

Raised as a ticket but wondered if anybody could help

I am using the grid to automate preset changes and bypass function in patches containing vst and au plugins.
​The standard bypass function works intermitantly, so as a workaround I create a preset patch, assign buttons to trigger saved preset states, one of which is set with the plugin bypassed, and automate them in the grid. This however is unreliable, sometimes the grid does not successfully change the preset, seemingly ignoring the automation.
​
​( I have also uncovered another bug, preset managers have to be created individually for different patches, copying and pasting leads to very unpredictable behaviour.)
​
​I have noticed that vst plugs have to be chosen with care, some plugs create huge amounts of data which can lead to big file sizes that can crash the program. I have chosen plugins that can be saved via presets that don't create large file sizes, and also sometimes deactivate "saved in preset" in the plugin, assign faders to its parameters, and save the fader settings in the preset manager. Thus I can save vst plugins with a very small patch file size.

The vst large file size when saved in preset is reason I can't use the workspace preset, Usine ballons to an enormous file size and fails to save.
​I am happy to work around this with the automate patches solution.
​
​Automating the patches and racks in the grid allows me to have my whole set as one workspace,and seamlessly morph between sections, avoiding loading workspaces mid set, keeping the music flowing. The alternate worspace does not work, I get glitching and dropouts.

I used the single workspace idea in a gig suporting Juan Atkins in London last night. Everything worked apart from the grid, which missed key patch changes, even though the automation was clearly visible.
​
​i am going to try with a lighter vst patch, and place an extra automation trigger point to see if it helps.
​
​is there a limit to how much automation the grid can handle?
​
​My workspace is quite deep, 8 channels of audio and many plugins, for a seamless 45 minute set. Next gig is 2 weeks away so racing against time to find a workaround. I like having the whole set as one workspace. This way I only have to calibrate to the PA once.
​if I have 8 pieces on 8 separate workspaces I have to set each gate and compressor on my 8 input channels 8 times, a total of 64 gates! There is never enough sound check time....

Any ideas?

Leon

[nay-seven]

yes, we try to answer your ticket of course.
About Plug_ins , yes some are really heavy and all are different and written with different programs so you have to experiment to find the faulty one.
about automation, no specific limits, the best way is to try to reproduce this with a minimal workspace to isolate clearly the issue
don't forget to specify the Usine and OS version you use

[Pianoscope]

thanks nay, just realised I always post "issues", just want to say in general how much I enjoy using this software,and how inspiring it is.
Thanks to Oliver and the rest of the team for all the hard work! it's appreciated over here.

[nay-seven]

Thanks a lot Pianoscope for your kind words, always appreciated !