Experimental support for Unity native audio plugins on the develop branch


#21

Both @mtytel and I have posted on the Unity forum about this in the past. Our concerns seemed to have fallen on deaf ears. I’ve taken a big step back from Unity as a result. I have to say however, that I haven’t looked into this area in quite some time, but if @ed95 also reports issues with automation on custom GUIs then it looks like the problem is still there. Might be nice if ROLI reached out to them. It would be to Unity’s advantage. Heck, why not turn the screw a little and release a UE4 plugin that does allows automation. Apropos, their audio API has got a lot better in recent releases. I imagine supporting JUCE plugins there may be not be that tricky.


#22

@ed95 Really nice new feature :slight_smile: Did I miss something or the unity plugin generated via Juce produces an empty shell? I just tried and the VST and AU builds are OK with the compiled code visible inside the plugin via ‘show package content’. But the unity generated plugin does not contain any compiled code… Does anyone also have this issue? Or I did something wrong?


#23

On macOS it should build a .bundle package which contains the executable in Contents/MacOS - do you not have this?


#24

@ed95 It builds the .bundle package: it contains the C# script, the Contents/ folder with Resources/ inside but no MacOS/ folder and consequently no executable inside. This is strange because the same XCode project builds AU and VST which contains the MacOS/ folder and executable inside (and they work fine in ableton). By the way, I just tried to build the “Hello world” plugin starter code from the ProJucer.


#25

Are you using the latest JUCE from the develop branch? You’ll need to rebuild the Projucer and make sure that the JUCE modules that the project is using are up to date. It sounds like your building against an older juce_audio_plugin_client module that doesn’t contain the Unity/juce_Unity_Wrapper.cpp file.


#26

You are wright, I think I was building against an older version of the modules… Now it works, thank you! Will verify this next time :wink: By the way, I had an error when I compiled the projucer plugin starter project (see the picture). I commented the line to make it work, maybe it’s normal because it’s the develop branch but I inform you just in case…


#27

Are you sure your JUCE modules are all the same version? This looks like an error from a mismatch…


#28

Yes, all JUCE modules are those of the develop branch.


#29

And the project that you’re trying to build is definitely using these modules? If you open the project in the Projucer and then navigate to the modules pane you can see where each module is located.


#30

Yes, I changed the modules path in the pane and they are all the same: the path of the develop branch.


#31

That’s odd. What version of macOS and Xcode are you using?


#32

MacOS: 10.12.6
XCode: 8.2.1 (maybe I have to update Xcode?)