Mac OS export Questions
-
@d-healey I have another M1 Mac laptop. I'll give that a try and see if it makes any difference. What I mean was it seems as though there is a rather small user base for HISE. I'm coming from Unity development where there are literally millions of devs on all platforms all over the globe using the software so I guess I've been spoiled with all that support. I now see that there is like 1000 people on this forum. Is that an accurate amount of actual users?
-
@d-healey using a VM is not exactly the best way to test for Mac support considering all the differences in hardware and OS versions. Like if I'm going to buy a new piece of software and I look at the system requirements and all it says is ... we tested it on a Mac VM... I'm going to pass on that software. I'd want to see what Mac hardware is supported and what OS version is supported. Does it support Intel and Apple Silicon or does it only support one or the other? Are there memory requirements? You see my point here?
-
@ElectroBlue of course there is a smaller user base. Compare the market for video games against the market for audio plugins, it‘s maybe 1:10000, which is why you also don‘t see a unity engine like framework from a big company.
Hise definitely has regular macOS users but they have never encountered your issues (myself included) so you can‘t expect them to give you the solution. Ask something like „What is xcpretty and what Xcode version do I need“ and you‘ll get an answer in about an hour.
-
@Christoph-Hart Got it. I understand. AND I have good news to share....
I tried HISE out on my M1 Macbook Pro and after a little bit of tweaking it... and as you mentioned ... installing xcpretty... I was able to export a working standalone Mac app! Finally! So I think the issue may have something to do with Intel Macs or possibly something on that particular iMac I was using... who knows?! lol -
@Christoph-Hart I still had issues with exporting the plugins.... got this error:
Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
error: Cycle inside NEON-8X - VST3; building could produce unreliable results.But I think this has to do with the version of Xcode I'm using on my laptop. I keep you posted.
-
@ElectroBlue Xcode 15 Beta 6 got rid of that error and finishes compiling the VSTi and AUi plugins without any errors but I don't know where it put them? I can't seem to find them?
-
@ElectroBlue look in your MacOS plugin folders
HISE Development for hire.
www.channelrobot.com -
Intel macs are definitely supported and I‘ve been using one for years with HISE but since a year or so I‘ve switched all my mac systems to ARM so it might be possible that a few glitches have creeped in.
-
@Lindon They are not there. they never got generated
-
Now this error on build for the plugins: xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
-
Ok, so I deleted Xcode 15 Beta 6 and installed Xcode from the Mac App store. I then exported my Virtual Instrument in HISE as an AUi and VSTi an d it went through a lengthly compile and finished with a Succeeded message but once again... the compiles plugins are nowhere to be found? They are not in my Mac's plugin directory and they are not in my HISE project folder's Binaries directory? Where did they go? Where are they usually generated?
-
I found them!!!!! I was looking for them under the main computer's Library/Audio/Plugins directory ... they aren't there! They were in my user account's Library/Audio/Plugins directory! Not sure why they didn't show up when I searched for them by their name? So strange, but whatever... I found them!! Yay :)
-
@ElectroBlue they didn't show up in my search results because that Library directory is hidden for the user account by default in Ventura 13.5
I only found them because I looked inside my HISE project folder inside the Binaries/Builds/MacOSX/build/Release .... there are alias to them in this location.I was looking inside the Binaries/Builds/iOS directory ... my mistake! ugh lol
-
I have now tested the plugins inside Logic Pro X, Cubase 12, Bitwig Studio 5 and GarageBand....they work perfectly in all these DAWS! This is so cool! :):smiling_face_with_sunglasses:
-
I spoke too soon! Ugh!! I tried testing the standalone Mac app and the AUi and VSTi on my Intel iMac and nothing worked! I have another older Intel Macbook Pro I can also test on just to be sure that this is an Intel issue and not something specific to my iMac.
-
@ElectroBlue Did you compile a universal binary or an arm one?
-
@d-healey Oh good question... how do I find out? I just exported from the HISE menu defaults.
-
-
@d-healey thanks! It looks like it's a Universal Binary: joeyadmin@iDance-iMac ~ % file /Volumes/T7\ Shield/Virtual\ Instrument\ Creation/_Replay11/_Virtual\ Instruments/NEON-8X.app/Contents/MacOS/NEON-8X
/Volumes/T7 Shield/Virtual Instrument Creation/_Replay11/_Virtual Instruments/NEON-8X.app/Contents/MacOS/NEON-8X: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64]
/Volumes/T7 Shield/Virtual Instrument Creation/_Replay11/_Virtual Instruments/NEON-8X.app/Contents/MacOS/NEON-8X (for architecture x86_64): Mach-O 64-bit executable x86_64
/Volumes/T7 Shield/Virtual Instrument Creation/_Replay11/_Virtual Instruments/NEON-8X.app/Contents/MacOS/NEON-8X (for architecture arm64): Mach-O 64-bit executable arm64Also, if I select the app and choose "Get Info" it says the Kind: Application (Universal)
-
@ElectroBlue And I just checked both plugins as well... they are both Universal Binaries
