Develop branch build status

[d.healey]

@yall There is possibly some configuration issue with your system because both develop and new_layout work for me and others. Are you using git to manage source code versions and branches?

[yall]

@d-healey I download them directly. I've always done like that. I try with xcode 12.5.1 now

[d.healey]

@yall Does that work for you? We had a discussion in a thread recently because clicking the download as zip was always downloading the master branch no matter which one you selected.

[Matt_SF]

@d-healey @yall it's solved. Now you can DL the choosen branch correctly.

[yall]

@Matt_SF so far it has downloaded the correct versions. I will try again anytime

[yall]

@d-healey I come back to you regarding the compilation of hise 5 hours later;)
I managed to compile hise with my following config.
xcode 12.5.1
development target 14.

I also put in projucer, in the mac os part, on native architecture of build machine. (they were on 64 bits)
.
big on 15.5.2 last develop version

now do you think the audio units will work in Logi pro?
because so far I still have not had an answer on this subject (logic belongs to apple so rosetta will not work)

[d.healey]

@yall said in Develop branch build status:

logic belongs to apple so rosetta will not work

According to Apple it should work

If you're using an Audio Unit plug-in that wasn't built for Apple silicon, Logic Pro or Final Cut Pro recognizes the plug-in only when Rosetta has been installed.

If you're having issues with this you should make a new thread so we can keep track of the problem.

[Lindon]

@yall said in Develop branch build status:

@d-healey I come back to you regarding the compilation of hise 5 hours later;)
I managed to compile hise with my following config.
xcode 12.5.1
development target 14.

I also put in projucer, in the mac os part, on native architecture of build machine. (they were on 64 bits)
.
big on 15.5.2 last develop version

now do you think the audio units will work in Logi pro?
because so far I still have not had an answer on this subject (logic belongs to apple so rosetta will not work)

try running auval for a start...

[yall]

@Lindon
can you tell me what AUVAL is? I don't know at all please

[Dan Korneff]

@yall https://auval.ca/

[d.healey]

@yall https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/AudioUnitDevelopmentFundamentals/AudioUnitDevelopmentFundamentals.html

[Lindon]

@dustbro said in Develop branch build status:

@yall https://auval.ca/

LOL...

[Lindon]

@yall said in Develop branch build status:

@Lindon
can you tell me what AUVAL is? I don't know at all please

check Daves URL above, you need the section called:

Audio Unit Validation and Testing in the menu(on the left) item Audio Unit Development Fundamentals

its not that clear(typical Apple) what you do but compile your AU plug-in and put it in the folder:

Completer/Library...etc.. folder

open a terminal window and type this:

auval -h

to get a list of all the command options.

The commands you want to use are:

auval -a

(to list and get your AU's recognised type , plugin code and company code

then auval -v (with those details from above)

it will run a series of tests (the ones LOGIC uses) to validate the plugin - if this succeeds then LOGIC will at least not reject your plug-in on validation grounds...

[A Former User]

@LinuxVst @d-healey Coming back to your earlier remarks about compiling HISE on Big Sur... I have now tried Xcode 12.4, 12.5, 12.51 and 13 without any success yet. I've set the macOS deployment target to 10.14 as suggested, but I always hit similar issues.

Has anybody been successfully building HISE and compiling plugins on macOS Big Sur yet???

[Dan Korneff]

@UrsBollhalder I had to downgrade to Xcode 12.0 to make it work. I haven't tried 12.2 yet, which would allow the export of native M1 plugs.
My be my project for this week since people really want native M1 plugs.

[A Former User]

@dustbro True! Maybe I'll try 12.2 quickly... ALthough quickly doesn't exist when it comes to downloading and unpacking XCode!!!

[d.healey]

@UrsBollhalder Let me know how you get on, I need to do some compiling on MacOS soon.

[A Former User]

@d-healey Well, so far no luck... 12.2 didn't resolve the issue... I'll keep you posted.

[d.healey]

Success with Xcode 13 - will probably work with 12x too.

I just had to disable un-needed architectures.

[A Former User]

@d-healey said in Develop branch build status:

Success with Xcode 13 - will probably work with 12x too.

I just had to disable un-needed architectures.

I'll try that right now... I've been at it for 2 days now... losing my shit... unable to get a working compile on Big Sur!

I get a bunch of these now... I believe to know that these are vst sdk-related but I don't know where to fix it! I think the sdk-path is not set correctly... but where!??!!