Soundtoys 5

Hey all,

I was just wondering if anyone is using the Soundtoys stuff on either platform and if so, how’s it working? I’ve been having some issues getting the settings to recall reliably. Anything slightly edited is definitely a NO GO, but even if I save a User preset per song, oftentimes it loads as “Default.” I was just wondering if anyone else is experiencing as well? I’m going to try to save a GPPluginPreset and see if that works every time.

Thanks!
Mark

Hi Mark, I am using SoundToys Plugins and face no issue so far.

Please take a look in the Plugin Manager at the Soundtoys Plugins:
Locate your plugin, on the right side you see a column Load Type.
Set it to Delayed.

What version do you use: VST or AU?

Hi Paul,

I’m using the AU versions right now. I’ll try setting them to “delayed” which I didn’t do because they initialize fine. I think there are maybe some differences in how each plug in deals with it’s initial state. Omnisphere and the u-he plugins are totally perfect, and even slight adjustments are remembered and seem to come right back, while others like Soundtoys, OPX-Pro, the Eventide stuff, etc all seem to have different levels of returning to the state I left them. I imagine that GP takes a snapshot of each setting, but maybe the plugin itself is telling it to load something that overrides that. Just trying to narrow it down.

Thanks!

As far as I can tell, I have no issue with the sound toys plugins.

What version of Soundtoys are you using?
I just double-checked, no issue with VST and AU - Version.

I am using GigPerformer 1.8.3.5

Hi Mark, which single plugins did you try? I haven’t installed Soundtoys 5 on OSX yet so I can only tell I haven’t got any issues with Soundtoys 5 / GP / Win 7.

BUT I’ve also had problems when recalling presets in OP-X PRO-II so I stopped using OP-X live. Almost every time I load a gig file, OP-X doesn’t recall the saved preset correctly and inits with the Matrix Strings (init patch). I had the same problem in MainStage (since the MainStage 3.2 update or so) 1,5 years ago and also with Studio One… so I didn’t consider GP’s VST implementation to be the problem. It’s really a pitty because OP-X has some nice brass/lead/pad/polysynth sounds.

I agree it’s a no-go not to be sure if your presets will be recalled properly. Maybe I can check that out after Christmas. If some of us can reproduce the issue, we could report that to Soundtoys and/or GP and hopefully they’ll come up with a solution.

I have the full version of Soundtoys 5, and I’m using the AudioUnit version in GP 1.8.4. Everything actually works fine, it’s when I open my GIG file and step through Rackspaces, I find most of the places I use Microshift, Echoboy Jr, etc will be set to the Default patch, instead of what I saved. Most noticeable with Little Plate, that defaults to 3 sec at 100% mix!! I’ll probably just save GPPluginPresets for them all, to be safe. Glad you are not having any quirks with them…thanks for the feedback, I appreciate it!

Wait…are you saying that GP is not restoring what you saved?

Hi Lukas…

Yes, EXACTLY…I waited FOREVER for them to port OPX Pro to mac, and I have the same issue with “Matrix Strings.” I even tried making my own bank of favorites, and changing the bank name to fool it into loading that, but it didn’t work either. I’ve been testing and tweaking my rig for weeks, trying to figure out the most efficient and reliable with best sounding plugins. So about 85% of my synth sounds are U-He plugs now…fine with me. Now I added my Virus into it, and my CPU never hits above 25%, with massive stacks of synth power :slight_smile:

Hi David…

That’s correct…some plugins work very consistently, and always come back to where I saved them, even if I don’t actually save the preset to the plugin. All spectrasonics and U-He plugs behave this way. Others, less so. Soundtoys seems to always load as ‘Default’ unless I saved it with a factory preset. The Eventide plugins load that way as well, unless I save a preset, then it will load that user preset. I just recently noticed this behavior, as the plugin did load, displaying the correct name, however the actual settings of the plugin were reverted.

Is this behavior just happening with Gig Performer or are you seeing this with other hosts like MainStage?

I don’t use MainStage, but I can reinstall and try it, however I do use Ableton Live. I have a few issues with some Arturia plugs, as well, but these happen in both Live and GP, so I know it’s on their end. The Soundtoys and Eventide only behave this way in GigPerformer. If I load them in Ableton, they come up as default, however if I make tweaks and save the session, when I reload it, it comes up where I left it. In GP it comes up as it did when I first instantiated it, though if I’ve internally saved a preset that’s song specific to the plugin itself, sometimes it will load that. I’ve been working off my large GIG file right now before I export all the rackspaces, but I can export a couple and see if it does it importing a Rackspace or only loading a gig file…

I am a Brainspawn Forte user that is transitioning to GP due to Forte development being discontinued. I can tell you that there were issues for OP-X Pro (and Pro II) in Forte, but there were config changes you could make specifically for a given plugin that would fix the behavior issues and enable sonicprojects plugins to work successfully inside the host. It didn’t just initialize to the strings, but actually recalled the appropriate program, tweaks, etc… If there would be any benefit to the developers of GP for me to share the details, I can certainly do that. Just let me know. I’m sure there are some users who would love to use OP-X in their rackspaces.

OP-X PRO II works fine with GP

I had a longer mail conversation with Peter from SonicProjects (at a time I were still using MainStage) and it took a while to figure it out and improve it. It turned out later that the problem was not 100% solved, but didn’t occur most of the case (in some case the correct patches still were not recalled (or saved?) so the Matrix Softstrings default patch were loaded in every instance.

I haven’t explored that with GP in detail yet. Will look at it tonight and see how if it can be reproduced. In the MainStage case it was hard because I have never found a way to make it happen reliably.

Can you provide more detailed? Have you contacted the ProII developer?