Mono to Stereo in 2025

[d.healey]

@orange I've been using it since at least 2023

[orange]

@d-healey said in Mono to Stereo in 2025:

@orange I've been using it since at least 2023

I've been using since 2019 ahaha Time goes fast and everything changes :))

[whoopsydoodle]

Unfortunately I still can't get it to show up as m > s.

Ive tried many combinations but the last one that still didn't work is:

Support Mono FX [checked]
Force Stereo [unchecked]

HI_SUPPORT_MONO_TO_STEREO=1
added to Windows and Mac Extra Definitions fields

Forget my comment about compiling outside of Hise, I can't even get it to work leaving that part out and compiling normally.

It's a real pain doing this over and over having to clear out the AU cache every time. Logic really kinda sucks for development.

[d.healey]

@whoopsydoodle said in Mono to Stereo in 2025:

added to Windows and Mac Extra Definitions fields

Just Mac and only for AU not VST3, you don't need it for Windows.

[whoopsydoodle]

@d-healey AAX windows?

[d.healey]

@whoopsydoodle Give me a moment, I'll check what I did there - it's been a while

[orange]

@whoopsydoodle said in Mono to Stereo in 2025:

@d-healey AAX windows?

Yes for Windows AAX, it is the same like macOS.

[orange]

@whoopsydoodle
You might need to clear the AU cache.

[whoopsydoodle]

@orange I've been deleting the com.apple.audiounits.cache in user library. I'm always unsure if I also need to reboot after that.

[d.healey]

On Windows, in Pro-Tools, this is what I see on a stereo track:

And on a mono track I see this:

I have Support Mono FX enabled and Force Stereo Output disabled. I am not using HI_SUPPORT_MONO_TO_STEREO

Is it possible to have stereo out from a mono track in Pro-Tools?

[whoopsydoodle]

I just tried a fresh new project to make sure nothing else was messing things up.

Support Mono FX ON, Force Stereo left alone so it's default off. Added HI_SUPPORT_MONO_TO_STEREO=1 to Extra Definitions OSX. Compiled AU in Hise. No AU Cache to worry about because it's a new plugin.

The plugin only shows in the Logic insert menu on stereo tracks as Pluginame > Stereo

Still no mono > stereo working here.

[d.healey]

@whoopsydoodle It doesn't show up at all on a mono track?

[whoopsydoodle]

@d-healey correct

[d.healey]

@whoopsydoodle I just made a minimal test project with the settings I mentioned and it's working correctly here. Are you definitely exporting as an effect plugin and not an instrument?

Here's my test project for you to try: fxtest.zip

[orange]

@d-healey Which HISE commit are you using?

[d.healey]

@orange A few days ago - dbf11eed4cb2bc1ff458c699812fcf25ea50c52e

[whoopsydoodle]

@d-healey Got sidetracked with other stuff but I'm back to this one now.

Yes, definitely exporting as an FX plugin. I've tried everything in this thread and still unable to get m>s working.

You made a simple FX test plugin? Would you be able to send me that? I can try compiling on my end to see if it shows up properly here.

[d.healey]

@whoopsydoodle said in Mono to Stereo in 2025:

Would you be able to send me that?

Already did - https://forum.hise.audio/post/99631

[whoopsydoodle]

@d-healey Ok got it.

This is very odd. I compile your test project and it works fine both as Stereo and M>S.

I compiled my project with the same settings as your test. Support Mono FX flag and HI_SUPPORT_MONO_TO_STEREO=1 option.

When I do AUVAL I even specifically see this, which to my understanding means it supports 1 in 2 out and 2 in 2 out:

Reported Channel Capabilities (explicit):
      [1, 2]  [2, 2]  

But still the plugin will not show up in the inserts menu for mono tracks.

Is there some other aspect that could be stopping it from being allowed on a mono track? Possibly something with using hardcoded DSP modules?

[d.healey]

@whoopsydoodle said in Mono to Stereo in 2025:

Is there some other aspect that could be stopping it from being allowed on a mono track?

Well I think there must be...

But I don't know what it is. I think you'll need to start with the test project and build it out until it doesn't work. Or try and figure out what is different between your project and the test project - start with project preferences and make sure they are identical.