The Source Code Has a Different Commit Hash than the HISE Build
-
@Jay-Lippman I guess you have another version of Hise on windows.
To fix it, have the same commit on both machines
I'm not sure if there will be any problem to export your VST, I guess it depends how big differences it is between the 2 builds. -
@ulrik I'm confused. I only have one machine, and it's a Windows machine.
-
@Jay-Lippman What?
That sounds strange, is it a snippet or project from another commit of Hise? -
@Jay-Lippman Build HISE using the source code you have, then try exporting your project
-
@d-healey Hey David! I've been binging your videos lately on YouTube lol. I'm unsure what exactly that means. Are you saying I need to re-build HISE using the source code that downloaded when I ran the Export Wizard?
-
@Jay-Lippman Yes, then both will match
-
@d-healey Okay. Do you have any videos on how to do that? I followed your Compiling HISE on Windows video for the original install. Not really sure which parts to skip for the rebuild, if any.
Sorry, complete newbie here.
-
@Jay-Lippman Same process as you already used for building HISE, the only additional thing extra might be you need to clean the build folder, but I think I showed that in the video. In visual studio it's in the Build menu > Clean solution - or something like that
-
This post is deleted! -
@d-healey Okay. I ended up clicking on "Check for new version" while I was waiting for a reply (I'm a compulsive button-pusher). Doing that and running the install seemed to fix the issue. I think. We shall see if the plugin actually ends up where it's supposed to be. Thanks for all your help!
