Release 1.2.0 Beta 3

[apohl79]

GENERAL

• Improved automation support
  • Bidirectional parameter syncing between AG plugin and DAW as well as AG plugin and AG server.
  • Support for recording automation runs via plugin UI as well as the generic editor.
  • Enables rendering of parameter movements in the generic editor and the remote UI.
  • This should resolve Automation on 1.1.1 and Live 11 #485.

PLUGIN

• Added "Keep Plugin UI Open" option
  • Allow the user to choose if the plugin UI should be opened automatically.
• Fixed settings menu Fix plugin settings menu #511.
• Minor UI fixes

SERVER

• Hide cached plugins with a disabled format
• Fixed default I/O layout for plugin chains

---

This discussion was created from the release Release 1.2.0 Beta 3.

[MrPisquan]

Hi,
first of all, thank you for your incredible work. This literally changed my life.
I just installed the beta 3 but the plugin is not connecting to the server.
AudioGridderServer_2021-05-05_11-49-11.log
Thank you for being there!

[MrPisquan]

[apohl79]

hmm working normally in cubase 10. here is how it is supposed to work:

1. assign the param you want to automate to a slot in AG.
2. hit the automation "W" button of the channel
3. play and change the parameter - alternatively, edit the automation curve manually.
4. hit the automation "R" button of the channel

[MrPisquan]

Hi Andreas,
mmmh. This time I did everything right.

1. the preset list is showing but when I select one preset nothing happens (several presets and plugin tested)
2. I assigned the slot, hit the Write automation button, changed the parameter but the DAW detects no automation.
3. I tried then to automate it from the daw, but the automation doesn't affect the plugin.
   Thank you for your support!
   Federico

[apohl79]

Would you be able to record a little screen video showing how you do this?

[MrPisquan]

Yes with pleasure, here it is:

https://wetransfer.com/downloads/1bd550127264aed8f5c0c9c39cffc80920210506194756/8bb9a3f090511cb191942c24d6bae91920210506194756/aa10c7

Thank you so much!

Federico

[MrPisquan]

Today I've dug more in the matter. Depending on the plugin the behaviour of AG is different, You will see in the video above some examples.
:-)
F.

[fojerhar]

Woow

A damn happy user here. Now working flawlessy in my hack with protools 21.3.1. Everything. Open close, as many instances I want (I could use only one in a session), plugin copy also works. old session opens up.
So, thank you for the amazing job, changes life, no stem mixdowns, no cpu peaks, all 32 cores have things to do :)))
Even the acustica modula works trough this troug two juce engines, funny
Big claps (my GF also happy, because I'm happy)
Looking again for the ppal button.
Thankyou
Viktor

[apohl79]

my GF also happy, because I'm happy

:-D

[CaBuffalo]

Hi, Victor and Federico, Thanks for the feedback. We are glad to see new Beta 3 solves the problem. Enjoy your mixing and please help us by spreading the words. Cheers.

…

On Wed, May 5, 2021 at 7:39 AM Andreas Pohl ***@***.***> wrote: Ok cool, you might have had loaded the prev version of the plugin. I should probably make the user feedback on connection problems a bit more readable (heard that before.. ;-)). There is always that question of the two servers instead of one, and I can't manage to automate parameters within Cubase 11.0.2, win10, but that annoying problem is sorted out. So are you saying automation is still broken for you? Or do I misread this? Thank you again for the incredible support: a bunch of minutes and you were here to help! sure, after pushing a release I keep an eye open for immediate problems :-) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#537 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARMAR6EEFUTVBSBF5T4XK7TTMFKDBANCNFSM44ELW3TA> .

-- Kevin Ma Supported by Gmail.

[AaronNiduk]

Hello) Sorry for my bad english
You saved me and my Xeon 2689 by using AudioGridder as a bridge for my plugins.
I am very grateful to you and will soon receive a scholarship and donate to you!))

I will have a request (I think many have it too)
Unfortunately, when you switch to the daw, the plugin is minimized.
Would like a * detached * function for the plugin
Please add the dock function of the plugin window.
I sent you a video.
Thanks!)))

20210505_201059.MP4

[apohl79]

I see, try moving the ag plugin DAW window (assuming local mode enabled). This should bring the plugin UI back to the front.

The way AG works is a bit limiting for running the server and DAW on the same desktop, as the plugin window belongs to the server process while the ag plugin window belongs to the DAW process.

One thing I will try though is forcing and keeping the plugin windows owned by the server to the front of the desktop. Right now this happens only when the position changes.

[fojerhar]

Hi amazing team

An issue with the 1.2.0.b3
Computer: AMD hack with catalina, pro tools 21.3.1

At sample rates 44.1 and 48K everything works like a dream, fast, reliable, and AG takes out all the processing power from PT

The same converted session to 96K with the same plugins do not takes out the cpu needs from PT

And I have cpu peaks and playback stops also
Here are the traces logs
AudioGridder 44-96K.zip
First I opened the 96K session, then the 44.1K session

Thank you
Viktor

[jin2]

I like the direction you guys are taking. Bravo for the continuous development.

However I'm getting a lot of crashing with both beta 2 and 3. I'm loading old projects that used 1.1 and after installs of the betas i eventually get into a cycle of crashing (the server goes into continual reboot)

going back to 1.1 resolves this.

Is there anything I can do to prevent this?

[apohl79]

Please provide bug report(s) for crashes. https://audiogridder.com/bug-reports/

Thanks!

[jin2]

AG Log.zip

Hi,
So installed beta 3 yesterday and used it for a few hours with no issues at all.

I open up the same session in Logic x today and I get a crash as soon as I press play.

I then emptied the AG log folders and re-ran the scenario above, the attached logs are from the most recent incident.

What was different this time was having to press allow incoming connections for AG, i dont recall having to do that at installation.

Hope it helps.

Thanks

[ignaceland]

Hello AudioGridder team, thanks for making this very useful and well developed software.

Just wanted to report that I am having the following problem in 1.2.0 beta3 with every plugin in Harrison Mixbus.
It doesn't happen with version 1.1.1. I think it has to do with the multichannel support on the new version, though as far as I can see everything looks fine on the pin connections.

The 1.2.0 beta3 loads the same plugins fine here in REAPER 6.
Kind regards

[apohl79]

Could you provide the plugin/server logs for the failed runs? https://audiogridder.com/bug-report-diagnostics-locations/

[ignaceland]

Sure thing
AudioGridderServer_2021-05-10_12-42-59.log
AudioGridderPlugin_2021-05-10_12-43-47.log

[Dirxman]

Hello,

maybe related to other I/O related problems....
The VST3 version of Audiogridder 1.2.0 beta3 comes up in an Amisonics 3rd Order Channel in Cubase Pro11, and even in Cubase Elements11 (although it a non valid Channel config in Elements, shouldn't even be possible there).

Cheers,
Dirk

[apohl79]

An amisonics 3rd order cubase channel uses 16 (mono) channels. As AG can do 16 in/out, why should it not be there?

[Dirxman]

Hi,

I forgot to mention that I use the Instrument Plugin.
I presume there is something wrong, as I did not want to use 3rd Order Ambisonics.
It opens as 3rd Order Ambisonics in an Application that is not supposed to allow this (Cubase Elements).

If I open the Instrument, Cubase (Pro and Elements) asks for output Channel config, it is set to stereo.
In both apps the result is an Instrument Track with 3rd Order Ambisonics configuration.
No Server involved at this point.

Cheers,
Dirk

[apohl79]

understood, ok thx, I will have a look at this

[djschultz123]

I'm stuck using 1.1 because I can't get any audio output from AG with the 1.2 betas in Studio One. Not sure what changed (nothing did on my end). The 1,2 beta FX plugin works great. But the instrument one, not so much. I can see that the synths are triggered, but no sound is produced out the other side.

Win10 latest release build
Studio One latest release build

[fojerhar]

Hi
Have found a bug in your really nice and amazing 1.2.0.b3 release.
Catalina, Protools
If I automate a master bypass for AG plugin, and I stop the playback where the automation is off then server and plugin collapses. If I let run trough the on off section it is fine, only if I stop the playback there
AudioGridder.zip
thank you for the amazing work!

[bluesbop]

Thank you guys for all your work on this, it's made an unbelievable difference in my workflow.

I'm finding that AU plugs are much less stable in beta3 compared to 1.1.1. I can't even open a single Acustica plug without the server going into a crash loop, but can load a bunch of VST versions without problem, even the ZL ones. Fabfilter AUs would crash the server twice and then settle down and work fine, and I also couldn't open Gullfoss AU...but VST versions of those plugs did not crash the server.

Anyone else noticing this?