LOGIC: version invalid on built plugins in Plugin Manager

[tomekslesicki]

@d-healey nah, it's not that. In Projucer, the version number is correct. Engine.getVersionNumber gets a correct value, too. It's just that Logic and AUval don't understand it.

[DanH]

@tomekslesicki yes same here. Logic says 'Invalid' under version number on all my recent exports and the Dorian Marko Piano. The projucer projects are fine though.

[d.healey]

@DanH said in LOGIC: version invalid on built plugins in Plugin Manager:

Logic says 'Invalid' under version number

Where do you see this? I'm going to check mine.

[tomekslesicki]

@d-healey in the Plugin Manager. But when you'll run auval like this:

auval -v aufx plugincode companycode

...you'll see version number as 0.0.0. You might have to change the aufx to something else, I'm running this on an FX plugin for a moment but for instruments it's going to have a different class here.

Plugin code is the 4-letter code in HISE, company code too.

[tomekslesicki]

@d-healey you can also run

auval -a

and it will list all installed plugins, giving you both the au type and other info

[Christoph Hart]

@tomekslesicki Hmm, might have been broken with the JUCE 6 update.

I'll take a look next week.

[tomekslesicki]

@Christoph-Hart thanks!

[d.healey]

I'm getting the same result with my AU instrument plugin.

[tomekslesicki]

Just to add to this: the plist included in the .component file seems to have the proper version number (as set in HISE) but Logic doesn’t seem to care.

It’s on unviersal binaries, if it matters, but then I’m not sure if anybody would want to export non-M1 native at this point anyway ;-)

[DanH]

@tomekslesicki It's on non-universal binaries too

[DanH]

@Christoph-Hart did you manage to take a look at this this week?

[tomekslesicki]

@Christoph-Hart it would be great to have this fixed!

[tomekslesicki]

Ok, I have some more intel. I updated XCode to 13.4 and macOS to 12.4 and things are both better and worse. The worse first: when I build the plugin, I get this:

❌  clang: error: unable to execute command: Abort trap: 6



❌  clang: error: linker command failed due to signal (use -v to see invocation)

I can't build the latest develop version of HISE either but I'm just using my backup copy from April 24th.

Now the good part: if I open the autogenerated Jucer file and build it for Native Architecture Of Build Machine, it builds fine AND the plugin version is displayed correctly in auval at last!

...but I guess the Native Architecture Of Build Machine is M1 only and won't work on Intel macs, right? Because my mac is M1 so that would kind of make sense?

@Christoph-Hart @d-healey

[d.healey]

@tomekslesicki Looks very similar to this error I was getting (on my Intel Mac Mini). My solution was to roll back to an earlier version of Xcode.

LLVM Error building on OSX

I'm getting an error I've never come across before on MacOS. It occurs during the linking and I see that all my system memory is being eaten up by the linkin...

Forum (forum.hise.audio)

[Casey Kolb]

Running into this issue as well. Starting to get complaints from Logic users because it has to rescan the plugin every time due to the version being “invalid”

[DanH]

@Casey-Kolb All I could find online so far: https://forum.juce.com/t/au-plugin-version-in-logic-pro-x/46992/4

Would be great to get this fixed :)

[DanH]

@DanH the commit from 30th November 2021 works fine fyi - I just happened to have that still on my machine

[tomekslesicki]

Ok, I have a little breakthrough:

The last XCode that can build plugins or HISE at the moment is 13.2.1

When the AU is built from HISE, the AU version is not written properly and auval can't process it.

When the AU is built from the autogenerated projucer file, everything is fine.

@Christoph-Hart ?

[Christoph Hart]

@tomekslesicki Great news, we're getting close (I can't find anything in the source code so I think it might have something to do with the build tools).

What happens if you run the batch file (Builds/batchCompileOSX) manually? Does the AU version work then or do you need to go into Xcode for compilation? It might be the case that the command line build tools (xcodebuild) is using a different Xcode version, otherwise there shouldn't be too much difference.

You can check this with a terminal command:

Which version of Xcode does xcodebuild use?

I have installed both Xcode 3.2 and Xcode 4.0.2 on the same machine, which uses Hudson for automated CI (continuous integration) builds. When I say that both were installed, what I mean by that is ...

Stack Overflow (stackoverflow.com)

Is it the same version than you're using manually?

[Christoph Hart]

Or are you using a different Projucer binary than the one shipped with HISE?