The Source Code Has a Different Commit Hash... and Other Errors
-
Hi guys, first of all, many thanks for accepting me here. I am a total newbie in HISE. I have to mention that I don't know any code. But tired of Maize, I took it step by step, especially helped by the tutorials of Mr. Healey (many many thanks for what he's doing!), and I succeeded in creating and exporting a VST3 plugin (sampler), not something complicated, but fully working. Then, noticing that my installs are a mess, I deleted everything, and I followed the tutorial for building HISE in Windows, everything step by step and carefully.
Next, I made another test plugin, and then while exporting, I noticed the following alerts and errors (?). The exported plugin seems to work perfectly. But I don't understand these errors. Can you please tell me what I am missing? I repeat, I am totally new to HISE, but I am eager to learn because I love its intuitive interface - it's like you start doing something and you advance by inertia. Thank you.
-
@Faniber There are no errors there, only warnings. The message about the commit hash means that the version of HISE you are using (the exe) is built with a different version of the source code to the one on your system. To get rid of that message you need to recompile HISE.
-
@d-healey Hey David, thank you for your fast response :)
If recompiling HISE means reinstalling the source code, I did that. I also updated HISE, because I have this message "New build available: 4.1.0. Press OK to download file to the selected location". But I update, and this message doesn't disappear. Maybe I am not updating properly? -
@Faniber said in The Source Code Has a Different Commit Hash... and Other Errors:
If recompiling HISE means reinstalling the source code,
No exactly. It means building HISE from the source code, rather than using the prebuilt version.
Check out my free bootcamp course that covers this in detail
-
@d-healey hmmm, I just found this...
-
@d-healey sorry, this is correct
-
@Faniber That just means you have the latest changes from whichever branch is active (use
git branchto check). But you still need to build HISE using that source code. -
@d-healey
-
@Faniber Looks good
-
@d-healey ok, many thanks sir! I am following the tutorial from here again https://audiodevschool.com/courses/hise-bootcamp/lessons/building-hise-on-windows/. You're doing a great job. I will subscribe to Patreon soon because I want to learn more.
