Whats latest perfect working HISE version, and AAX and m1 compile instructions and implementation
-
i get lost sometimes knowing what version of hise im supposed to be pulling from to compile my standalone and plugin versions of hise..
i had been using an older scriptnode or a developer version that has been working good for me for a year or so...but what is the latest full functional build of hise first off that i should be working with as of now...i think mine is from about 18 months ago lol.
secondly im getting an m1 mac tommorow and i want to compile plugins in m1 native and AAX for pc and mac. so...
-
what are the instructions to compile hise and plugins from hise in m1 native. and is the plugin and folder locations the same as before
-
what is the process of getting AAX im not sure if i need some sort of develop avid membership etc. i did a bunch of things before and im able to compile AAX although ive never been able to test what is being compiled as i never use pro tools...so what is that whole process
-
also i noticed some people having issues with older hise based stuff in newer versions of logic. will that be fixed or changed in a newer hise compile or my m1 rig?
thanks in advance :)
-
-
@mwplugs Usually you want the version that's most recently been updated. You can see this by viewing the Branches page on the github repo. Sometimes the most recently updated branch will have a bug and won't build, but this is usually resolved quickly.
what are the instructions to compile hise and plugins from hise in m1 native. and is the plugin and folder locations the same as before
You can compile natively for M1 or Intel on both an M1 or an Intel Mac. Just do it the way you always have done, nothing really changes - but you will need to be using the latest version of HISE.
what is the process of getting AAX im not sure if i need some sort of develop avid membership etc. i did a bunch of things before and im able to compile AAX although ive never been able to test what is being compiled as i never use pro tools...so what is that whole process
You need to sign up as a developer with AVID to get access to their SDK. More than that, I have no idea.
also i noticed some people having issues with older hise based stuff in newer versions of logic. will that be fixed or changed in a newer hise compile or my m1 rig
Plugins built with the latest version of HISE and correctly signed and notarized should have no issues.
-
@d-healey i am registered as a developer and got the sdk and did the little compile thing i had to do within it to get it to work. will those plugins work? i should check huh lol
and...i have no idea how to get things signed and notarized..never heard of it haha hmmm..i guess what is that process
lastly so you are saying i dont need to get an m1 mac at all to even compile m1 native, i just need the latest version of hise but which branch?
i know there is the scriptnod, developer and then the main one i only ever saw a super old commit can you link me to the github branch and version possibly?
-
@d-healey it seems the latest one here
https://github.com/christophhart/HISE/tree/develop
is from 11 hours agothe masters last commit was nov
https://github.com/christophhart/HISE/tree/masterit also has a red X and i always assumed that means something is wrong
so should i grab the latest master or developer branch? i always get confused by this haha
-
will those plugins work?
No idea. I've never made an AAX plugin.
.i have no idea how to get things signed and notarized.
Here's the guide to signing and notarizing - prepare for fun :D Before you can do this you'll need to sign up for an Apple Developer account (and pay the fee) and set up the signing certificate they give you (Google is your friend here).
lastly so you are saying i dont need to get an m1 mac at all to even compile m1 native, i just need the latest version of hise but which branch?
Correct. XCode will build universal binaries that are native to both M1 and Intel, I think you need to be using Xcode 12 or newer for this (but I might be wrong).
it seems the latest one here https://github.com/christophhart/HISE/tree/develop
is from 11 hours agoThis is the one to use.
-
@d-healey thanks man. i about to subscribe to your patreon the hise exporter plus being able to just run things by you is worth it x10 :)
-
@mwplugs Thank you!
hise exporter
Don't use this until you can do it yourself using the standard tools. It's very much in an alpha stage and not being actively developed at the moment. It's designed as a tool for batch exporting multiple projects (although that's one of the features that doesn't work yet :p ) it's not meant to be a replacement for knowing how to export/sign/notarize manually.
-
@d-healey ugh lmao. it seems there is hise templates for whitebox and whitebox can sign and notarize if im not mistaken. we shall see.
-
@mwplugs said in Whats latest perfect working HISE version, and AAX and m1 compile instructions and implementation:
@d-healey ugh lmao. it seems there is hise templates for whitebox and whitebox can sign and notarize if im not mistaken. we shall see.
it cannot.
-
@Lindon boo :(
-
@mwplugs Actually you can get the public SDK for AAX just creating a Dev account (I think you already did that) but in order to make the AAX Plugins to work in a Release version of Protools you need to be part of a Partner Program and have an iLok to sign the Plugins before distribution, without signing the plugins will work only in Pro Tools Dev version but to get a license of Pro Tools Dev you need the iLok and a Partner Program.
-
@d-healey So I really don't need to do anything else for Native M1 support but simply export as normal with the newest HISE? Maybe because I'm on Xcode 10 it won't work?
-
@Casey-Kolb yes there are some minimum
OS and Xcode requirements but otherwise the M1 export works out of the box. -
@Christoph-Hart Awesome! Thank you. I was afraid I'd need to start shipping two versions of the Mac plugins, one for M1 and one for Intel.
Does anything need to be selected in Projucer before exporting?
-
Does anything need to be selected in Projucer before exporting?
No - assuming your using the standard export from HISE and not doing anything custom it should just work.
