Replies: 5 comments 6 replies
-
Thank You Andreas!!! |
Beta Was this translation helpful? Give feedback.
-
Ohh, nice, lets try!) |
Beta Was this translation helpful? Give feedback.
-
I had to revert to v6 on my Win10 computer in Studio One Pro 5.latest, With v7, the plugin window anchored in one place and also the Audiogridder plugin and the synth plugin it loaded were also locked into relative position to one another. Very weird. Worse, I couldn't use a menu in the softsynth loaded into Audiogridder because the menu kept automatically closing as I tried to use it. I'll try again with the next version. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the update. Also, when loading a plugin, the plugin window appears. If I 'x' it out, it just reappears a few seconds later. I have to click on the plugin name in the AG window to 'un-highlight' it, and then the plugin window stays closed. Don't know if this is intentional, but I'm just noting it because it is different behavior from v6. I'm also not able to reposition a loaded plugin window without it returning to the original position. For instance, I can move a plugin window to a 2nd monitor, but it returns to the 1st monitor almost instantly. |
Beta Was this translation helpful? Give feedback.
-
I realize I'm not exactly the main target audience, this being a beta version. but my somewhat obsolete system (Mojave 10.14.6 and Ableton 11.0.11) only runs into issues with the main FX instance, with the same old constant CPU spikes of over 1000% from just loading AG. both MIDI and Instrument instances didn't cause spiking. hope this is useful |
Beta Was this translation helpful? Give feedback.
-
GENERAL
In the following cases we will prefer unix domain sockets over TCP for performance improvements:
Plugin windows are properly positioned by aligning to the DAW window size rather than the rendered editor space. This resolves issues with AG zoom enabled, if DAW plugin windows are larger than the AG editor itself and scaling on Windows.
The plugin will perform connectivity checks before showing a server entry. Also, remote servers in local mode will not be shown anymore.
PLUGIN
SERVER
In addition to isolating a plugin chain in a separate process, each loaded remote plugin will be isolated in its own sandbox process.
Multiple servers can be run on one computer using different IDs. Each server will have a dedicated config going forward. This allows for running x86 and arm servers on the same macOS instance using different plugin folders etc.
This discussion was created from the release Release 1.2.0 Beta 7.
Beta Was this translation helpful? Give feedback.
All reactions