Develop branch build status
-
@yall Did you clean the build folder before compiling again? What error are you seeing?
-
@d-healey yes I did.
some errors like this one./Users/mine/Desktop/HISE-develop/hi_components/floating_layout/SnexFloatingTiles.h:70:32: No member named 'ui' in namespace 'snex'; did you mean 'scriptnode::analyse::ui'?
/Users/mine/Desktop/HISE-develop/hi_components/floating_layout/SnexFloatingTiles.h:70:42: No member named 'WorkbenchData' in namespace 'scriptnode::analyse::ui'
/Users/mine/Desktop/HISE-develop/hi_components/floating_layout/SnexFloatingTiles.h:133:18: Unknown type name 'Ptr'
/Users/mine/Desktop/HISE-develop/hi_components/floating_layout/SnexFloatingTiles.h:105:40: Expected class name
-
@yall Looks like it's all snex related. Have you tried the new_layout branch?
-
@d-healey no but I will try. but is it functional to release plugins?
-
@yall I haven't tried compiling any plugins with it yet so I don't know.
The latest commit has a bug where UI tables cause HISE to crash, so you should use a few commits earlier. Probably this one https://github.com/christophhart/HISE/tree/a3eb5dfa2d1ce5051564a1c2ed4774dfb6970574
-
@d-healey I will try them all. forcefully there is one who will have pity on me
-
@d-healey the 2 verisons that you recommended to me do not compile. same error
-
@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?
-
@d-healey I download them directly. I've always done like that. I try with xcode 12.5.1 now
-
@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.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
-
@Matt_SF so far it has downloaded the correct versions. I will try again anytime
-
@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 versionnow 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) -
@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.
-
@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 versionnow 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...
-
@Lindon
can you tell me what AUVAL is? I don't know at all please -
Dan Korneff - Producer / Mixer / Audio Nerd
-
-
-
@yall said in Develop branch build status:
@Lindon
can you tell me what AUVAL is? I don't know at all pleasecheck 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...
