Mono versions of FX Plugins?

[Tod Slaughter]

Can you not send the left channel to both outputs using a routing matrix?

[resonant]

@tod-slaughter
No it doesn't work. Because the plugin has stereo input and output.

When you want to instert a (HISE made) plugin on a mono track, your plugin won't be in the list. There are only mono compatible plugins on the list for mono tracks. (Pro Tools, Logic Pro X...etc)

That means user can't put effects on your vocal takes, instrument records...etc directly. This is a very sad thing for an fx plugin.

[Tod Slaughter]

Ok fair enough

[Dan Korneff]

Is the new "Support Mono FX" feature supposed to work yet? I've tried and plugins are still only available as Stereo with this option selected.

[Christoph Hart]

Yes, but it only works for FX plugins, instruments always will be stereo. Which host did you test?

[Dan Korneff]

Yeah, I just exported with the delay effect in the master container. Tested on ProTools 12 and 2018.
I tried exporting on HISE standalone and HISE plugin.

[Christoph Hart]

Ah, I didn't check our old friend ProTools. Can you test it in another DAW, not that there's something generally wrong with it - I checked in Cubase and the JUCE plugin host - Ableton has no concept of mono channels AFAIK.

[Dan Korneff]

@christoph-hart protools and logic don't recognize the export on mono tracks. Cubase works fine

[Christoph Hart]

That is the exact reason why I bothered adding this because now I have to check this on every host for a really edge case use case of this framework.

[Dan Korneff]

@christoph-hart anything I can do to help?

[Christoph Hart]

If you have any other host sitting around on your hard drive, you can check it there so that I can verify and debug each host.

[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?