I just got the new 2024, iPad Pro 11 M2 and it’s a beast!
Has anyone recently attempted to compile HISE or found a way to get their plug-ins working on iOS?
I just got the new 2024, iPad Pro 11 M2 and it’s a beast!
Has anyone recently attempted to compile HISE or found a way to get their plug-ins working on iOS?
@virtuscapeaudio @pgaudioworks HERE are my notes from @d-healey 's Scripting 101 video (the video link is in the header of notes). Maybe they can be helpful to you even though they are in my own language.
This link is marked "Editor" so if anyone want's to contribute for other first timers then please feel free. (Then again there's always the HISE Docs lol)
@pgaudioworks I literally had zero knowledge of any programming language but tons of experience with Kontakt since v4. If you are a great student, then all you need to do (what I did) is sign up to @d-healey patreon (top tier), binge watch his youtube channel and take literal notes, and just dive straight to the deep end by creating a project. Highly recommend at least starting your project with the Rhapsody template as the infrastructure is all there (preset browser, basic GUI, etc) to get a feel.
My debut instrument was made with mostly bult-in components (including the reverb freeze mode!!) but the community here and ChatGPT helped with HISE scripting.
https://www.youtube.com/shorts/PLRcWuEkvIU
For context, it took me about 5 months from the first youtube vid I watched to releasing the instrument. (I already had samples recorded and tried to build in UVI Falcon first).
Honestly if it wasn't for @d-healey and @DanH (and of course the forum) I couldn't have done it.
but...
JUST GO FOR IT...It's worth it in the end.
@MrControl I built my debut instrument with the Rhapsody template....Shoutout to @d-healey !!!!
@DanH Yes indeed @Christoph-Hart What an amazing thing the whole HISE ecosystem is. Kudos to you and congrats!
@BWSounds Same here...you ever find out what was up? I just updated the standalone and compiled and immediately opened and now I don't see the presets. All the necessary settings are checked and have worked in previous exports.
@d-healey Solved. I had to revert to a previous commit from Sep 25th and rebuild HISE and Exports now work inside HISE
@DanH SMART!!! thank you!
@DanH Good advice! Yup I'm trying to update Rhodecase88 which is my debut release haha. tbh I just assumed the latest was best..still a noob. I may just try to go back and find the branch I was using before. I will PM you the project to see if maybe you can export it? REALLY appreciate it.
@virtuscapeaudio Is it an Xcode issue if other projects work fine when exporting other projects?
@d-healey This project is built on a Rhapsody template and perhaps updating to the latest develop branch caused something to go awry? idk
Yes def the AutogeneratedPoroject.jucer
Yes that happened to me as well so I made sure only arm64 is selected and I chose Save and open in IDE, Build and get the same error.
@DanH I'm not using faust...I'm on M1. I just exported a different project successfully from within HISE without any modifications. The build that fails doesn't get past the Global Header issue. What exactly is the Global Header? Perhaps there's something within the Project Settings of this particular .xml that I'm missing? How trivial is it to rebuild this project? I would hate to go down that road if its something as simple as fixing a setting the project_settings.xml or something (I'm really guessing, here)
@DanH Ive tried to change to x86_64 then build, and arm64 then build, and still no global header is included automatically. Also I don't see the VST and AU targets in Xcode, only Standalone
@d-healey All was working well with Xcode until I updated to latest develop branch of HISE so I wonder if something doesn't match with the actual project or something. Tested other projects and it works fine.
@d-healey XCode 13.1 on MacOS 12.2.1
@DanH Really having trouble with this...I exported another test project just fine so it seems architecture settings are ok. I deleted the entire build folder and tried again but same issue.
Interesting thing is when I open in Xcode, I no londer see VST and AU targets, only Standalone.
any ideas?
@d-healey Just cleaned it. Failed again with this error:
/Users/cadencemusicent/HISE/hi_dsp_library/../hi_tools/../JUCE/modules/juce_core/system/juce_TargetPlatform.h:56:3: "No global header file was included!"
#error "No global header file was included!"
^
** BUILD FAILED **
The following build commands failed:
CompileC /Users/cadencemusicent/Music/Top\ Secret/_VirtuScapeAudio/Rhapsody_Rhodecase_88_v1/Binaries/Builds/MacOSX/build/Rhodecase88.build/Release/Rhodecase88\ -\ Shared\ Code.build/Objects-normal/x86_64/factory.o /Users/cadencemusicent/Music/Top\ Secret/_VirtuScapeAudio/Rhapsody_Rhodecase_88_v1/AdditionalSourceCode/nodes/factory.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'Rhodecase88 - Shared Code' from project 'Rhodecase88')
(1 failure)
Same error on Standalone and VST/AU Export
Any ideas?
/Users/cadencemusicent/HISE/hi_dsp_library/../hi_tools/../JUCE/modules/juce_core/system/juce_TargetPlatform.h:56:3: "No global header file was included!"
#error "No global header file was included!"
^
** BUILD FAILED **
The following build commands failed:
CompileC /Users/cadencemusicent/Music/Top\ Secret/_VirtuScapeAudio/Rhapsody_Rhodecase_88_v1/Binaries/Builds/MacOSX/build/Rhodecase88.build/Release/Rhodecase88\ -\ Shared\ Code.build/Objects-normal/x86_64/factory.o /Users/cadencemusicent/Music/Top\ Secret/_VirtuScapeAudio/Rhapsody_Rhodecase_88_v1/AdditionalSourceCode/nodes/factory.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'Rhodecase88 - Shared Code' from project 'Rhodecase88')
(1 failure)