Mono versions of FX Plugins?

[dustbro]

@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.

[dustbro]

@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.

[dustbro]

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

[dustbro]

@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/

[dustbro]

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

[dustbro]

@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.

[dustbro]

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

[dustbro]

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

[dustbro]

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?

[dustbro]

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

[dustbro]

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

[dustbro]

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