AG Instrument does not activate all channels

[Dieguitarro]

Hello everyone. I had already presented this problem in the beta 15 version, apparently in this new version the problem persists.

It turns out that having one or more AG instruments inside a project does not automatically activate all channels, there is a section called "all channels" that is active by default, the problem is that the additional channels do not appear there, they appear outside of that section , so the option "all channels" cannot fulfill this function, therefore you must activate all channels manually every time you open the project

I would appreciate any solution on this.

thank you so much

[Dieguitarro]

PSD: The virtual instrument used is SUPERIOR DRUMMER 3 in the DAW cubase 12

[apohl79]

The way that menu works is:

• it presents all available buses
• a bus can have 1-many channels
• if a bus has more than 1 channel, it shows a submenu for that bus with an "All channels" item and the individual channels
• "all channels" in the submenu applies only to that bus
• at the top of the "instruments outputs" menu you have an item called "enable all channels", which applies to all buses, use this to activate all available outputs across all buses

[Dieguitarro]

Hello, thanks for the prompt response.

I understand what you are saying, I have implemented it, but AG does not save the assigned option, therefore you have to manually activate the channels every time you open projects in the DAW with similar configurations.

[apohl79]

you mean every time you add a new instance of AG, you have to go into the menu and activate all channels, right?

[Dieguitarro]

Good day.

No, every time I open an existing project with AG instrument instances I have to activate the channels manually or do the procedure you mention in the first comment, that is, AG does not save the option to "activate all channels"

[Dieguitarro]

*AG does not save the option to "enable all channels"

[Dieguitarro]

Hi, I'm sorry I didn't make myself understood.

To give a clearer and simpler example. what is happening is like using kontakt with a virtual instrument that needs multiple channels. The problem is having to activate the kontakt channels every time the daw project is opened because kontakt doesn't save the settings in the daw project. having to do that every time the daw project is opened

[Kjudkins]

How bitter sweet, I found AG seemed to be a must more efficient host for some vsti only to discover this fatal flaw on accident.

Just to reiterate the problem: you add an instrument and it only plays the left signal of the first stereo pair.

You remedy this by enabling all every single time, but the issue is, everything you load that project up you have to go in each single instance and re-enable the outputs by hand. The same problem occurs with SINE player, Kontakt, Spitfire player and really anything I tried. Saving the state would be one way to fix the issue, the other would be to make all outputs enabled by default.

So close yet so far!! AG is still an interesting piece of software, would love to eventually drop VEPRO entirely.

[emack999]

@Dieguitarro I use Gig Perfomer.

However, I just checked in Cubase 12 and the project saves the channels correctly there as well(using the same steps as I listed in my last post).

[emack999]

@Dieguitarro I also tested this in Cubase12 using Superior Drummer 3, as you did, My channel settings were saved and reloaded properly.

[Dieguitarro]

So I don't understand what's happening.

In my case it's as if the default plugin only enabled "all channels" found on the two stereo systems.

Is there a configuration that I am overlooking?

[Dieguitarro]

Does Cubase also activate the plugin channels? or how do you do it?

[emack999]

@Dieguitarro I don't know what is happening for you.
My procedure was this:

• Open Cubase > Create New project
• Add Track > Instrument > AudioGridderInst

• open AG > Load Superior Drummer 3 VST >16xStereo
• In AG, Instrument Options > Enable All Channels
• Save Project > Close Cubase
• Open Cubase > load project I just saved

[emack999]

Does Cubase also activate the plugin channels? or how do you do it?

No Cubase does not activate the plugin channels automatically.

[Dieguitarro]

@emack999 try doing the same in AG vst3. in the list of plugins it appears with 3 vertical lines III

[Dieguitarro]

@apohl79 @emack999 I already found the problem.

AG VST3 plugin does not save settings.

VST2 if it saves it

@apohl79 Could you check that?

We could work with VST2 instances but the DAWs in the future will not support it and that is a big problem

[Dieguitarro]

@apohl79 The differences between the VST3 and VST2 instances of AG instrument is that when loading the VST2 plugin, by default the 64 non-active channels appear, but they do appear, in VST3 this does not happen, when loading the VST3 instance by default 1 stereo channel appears and If we activate the channels in Cubase, they appear within the plugin to activate.

For this reason I think that in the VT3 instance the default stereo channel will always appear even if it is saved with active channels.

[emack999]

when loading the VST3 instance by default 1 stereo channel appears and If we activate the channels in Cubase, they appear within the plugin to activate.

I can confirm this behavior with the VST3 version. When the VST3 AG plugin is loaded, only 1 Main stereo channel is visible in AG. If you enable more channels in the DAW, then those channels appear in AG to be enabled. In the VST2 version, all 64 channels are visible in AG before doing anything in the DAW.

As a side note, I cannot change the bus layout of the AGridderInst VST3 in Gig Performer---it hangs the host.

[Kjudkins]

So is there a vsti version of AG? Or just vsti3? I'm away from my machine but if I can atleast get stereo outs by default in reaper I'd be back in business

…

On Mon, Nov 6, 2023, 2:51 PM Ed M. ***@***.***> wrote: when loading the VST3 instance by default 1 stereo channel appears and If we activate the channels in Cubase, they appear within the plugin to activate. I can confirm this behavior with the VST3 version. — Reply to this email directly, view it on GitHub <#1191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDUNYZG3EVAFWWEJ47JHMCDYDE5UJAVCNFSM6AAAAAAWJVNDPOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TIOJRGUZDK> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mabian69]

Do you need to only change from line 595, right? The line 96 inside the constructor can be left as it is...?

Thanks!

[mabian69]

Answering myself... I changed as mentioned, it works beautifully :)

[StephanRoemer]

What tools are needed to compile this on macOS?

[mabian69]

I managed to build it both VST2 and VST3 on Linux, including the change for channels (VST2 didn't need it anyway).
I needed to clone the git repo, both the main and dependencies, get the vst2sdk around, and follow the instructions here:

https://github.com/apohl79/audiogridder/blob/master/DEVELOP.md

Some libs were missing, and the make failed, but I found this and it helped a lot:

https://linuxmusicians.com/viewtopic.php?t=27103

On MacOS I don't really know, should be similar.

[StephanRoemer]

Thanks for the heads up! Will check out :)