Mono versions of FX Plugins?

[Dan Korneff]

@christoph-hart AU in Reaper shows up as 2in/2out plug, but will load on mono track. It'll also load on a mono channel in GarageBand.
Seems like Logic and PT are the only hosts picky about channels.

[orange]

@dustbro I don't know Studio One and Ableton Live has mono support; but did you tried on one of them too?

[Dan Korneff]

@orange I don't have access to those.

[d.healey]

@dustbro
Free trials
https://www.presonus.com/products/studio-one/get-studio-one
https://www.ableton.com/en/trial/

[Dan Korneff]

just tested studio one. It loads on mono and stereo tracks.

[Dan Korneff]

@Christoph-Hart could this be our issue?
https://forum.juce.com/t/adding-mono-to-stereo-hides-mono-to-mono-in-protools/30266/2

Also:

JUCE now generates the AAX plug-in bus layout configuration id independent from
the position as it appears in the Projucer’s legacy “Channel layout
configuration” field.
Possible Issues
ProTools projects generated with a < 4.3.0 JUCE versions of your plug-in, may
load the incorrect bus configuration when upgrading your plug-in to >= 4.3.0
versions of JUCE.
Workaround
Implement AudioProcessor’s getAAXPluginIDForMainBusConfig callback to manually
override which AAX plug-in id is associated to a specific bus layout of your
plug-in. This workaround is only necessary if you have released your plug-in
built with a version previous to JUCE 4.3.0.
Rationale
The new multi-bus API offers more features, flexibility and accuracy in
specifying bus layouts which cannot be expressed by the Projucer’s legacy
“Channel layout configuration” field. The native plug-in format backends use
the new multi-bus callback APIs to negotiate channel layouts with the host -
including the AAX plug-in ids assigned to specific bus layouts. With the
callback API, there is no notion of an order in which the channel
configurations appear - as was the case with the legacy “Channel layout
configuration” field - and therefore cannot be used to generate the AAX plug-in
id. To remain backward compatible to pre JUCE 4.0.0 plug-ins, JUCE does
transparently convert the legacy “Channel layout configuration” field to the
new callback based multi-bus API, but this does not take the order into account
in which the channel configurations appear in the legacy “Channel layout
configuration” field.

[Dan Korneff]

@Christoph-Hart giving this a friendly bump. Any luck on mono compatibility?

[Dan Korneff]

@Christoph-Hart Any chance you can take a peek at this before your radio silence?

[Dan Korneff]

Taking a look under the hood to try and understand what the Mono FX option is doing.
What's the idea behind having this if + else statement being the same here?

And what does line 98 and 99 do here?

[Dan Korneff]

I created a 1 channel version of the HISE plugin... the exported AAX shows up as a mono plug in Protools!

[Christoph Hart]

Great news. Does it work in Logic (or whatever DAW was also not working correctly)?

[orange]

@dustbro Great news. and great idea, congrats!! I hope this is the solution. If you want, you can send the mono plugins that you've compiled and we can test it on different systems too. I can test on both PC/MAC - Pro Tools / Logic Pro X 10.2 / Ableton ...etc

[Dan Korneff]

@Christoph-Hart I actually have some strange news... While using the standalone version, I'm able to create mono compatible AAX plugins by changing the routing in the master container to 1 channel, then back to 2. Gonna do some more testing to see exactly what's causing this. I haven't tested in Logic yet. just pt

@orange Can you try this with your rig and let me know if it works?

[orange]

@dustbro How did you compile 1 channel version of Hise? Only from JUCE interface or did you modify any code?

[Dan Korneff]

@orange
In the projucer

[orange]

@dustbro Ok, so after compiling it, in HISE, you made the routing of the master container 1 to 1, that's it right?

[Dan Korneff]

@orange yes

[Dan Korneff]

@orange but I was also able to do it with the standalone version just by changing the routing and then changing it back. No need to tweak with projuicer

[orange]

@Christoph-Hart I think the only reason for this mono plugin problem is; there is a misunderstanding for that.
Stereo plugins shouldn't be at the same time mono compatible. HISE trying to make a stereo plugin mono compatible. Maybe that's why it is hard to do it.

For mono plugins, HISE should create a different mono channel plugin, that uses only one channel (1 in - 1 out) like @dustbro had manually compiled HISE.

All of the fx plugin companies are making separted mono VST2, AU, AAX plugins with stereo versions. In only VST3, an fx plugin is able to compatible with mono tracks at the same time, but in VST2, AU and AAX mono version should be compiled individually.

So maybe HISE can compile a stereo plugin with only one channel and create a seperate plugin with stereo version. Just simulating like @dustbro manually did. So all of the versions will be double (mono & stereo) is it possible?

[lalalandsynth]

@orange said in Mono versions of FX Plugins?:

maybe HISE can compile a stereo plugin with only one channel and create a seperate plugin with stereo version. Just simulating like @dustbro manually did. So all of the versions will be double (mono & stereo) is it possible?

Has this been resolved , I am assuming I will have to make mono versions of my fx plugins for compatibility ?