Hise will not export
-
@d-healey had to restart the computer for some reason. compiling now. is this how I am going to have to do all projects or are we just testing something?
-
Use the correct directory in the HisePath setting. I can see the mismatch from your screenshots.
-
@Christoph-Hart what should it be set to? I am confused.
-
@gryphonsegg Click the browse button and select your HISE source code path. The path you showed us you had set ends in
/HISE, but we can see in your screenshot of the SDKs that the path should end inHISE-develop/HISE-develop -
@d-healey I fixed that. it was a temporary change in folder name to see if that worked but did not so I changed it back. still doesn't work, by the way VS successfully build the project. I don't know where to find it because when I go to look for it there is no VST but just the same, it said successful. Now what?
-
@gryphonsegg it still says it cannot find the path when compiling in HISE
-
@gryphonsegg If you're compiling a VST2 it will have a .dll extension. If you're compiling a VST3 it will have a .vst3 extension. It might have automatically copied the VST3 to the VST3 location on your computer:
C:\Program Files\Common Files\VST3Did you set the HISE path by clicking the browse button and choosing it or did you enter it manually? If you copy and paste that path into explorer does it open the HISE source folder?
-
I cannot find the .dll of it or the vst3. I looked everywhere and definitely in the vst3 directory. secondly, I browsed for the folder location from the HISE file path prompt. and yes copying and pasting it into the explorer opens the source folder. That is the source folder yes?
-
@gryphonsegg Show a screenshot of the folder with that path please
-
@d-healey I found the .,dll. It was a debug build.
-
@gryphonsegg Ah you must have built a debug version.
Yep that's the HISE source path. If that is set correctly in project preferences then I don't know why HISE is complaining.
-
@d-healey me either. I really want this to work.
-
@gryphonsegg when I compiled HISE I did it with the PPI or IPP, whichever it is, and for 2022. was that correct? would that have any ill effects?
-
@gryphonsegg If it was causing a problem you'd get an error that mentioned IPP.
-
@d-healey no errors . only it saying it cannot find the file every time. Can we fix this?
-
@gryphonsegg I know you guys are way smarter than I am apparently LOL
-
@gryphonsegg said in Hise will not export:
@d-healey no errors . only it saying it cannot find the file every time. Can we fix this?
I have no idea, if the path is definitely correct and you only have one copy of the source code on your system then it should work.
-
@d-healey so is that it? nothing else can be done?
-
@gryphonsegg There is nothing I can do without access to your machine. At least at the moment I have no suggestions of things you can try.
-
@d-healey wonderful. Well, I guess HISE is not for me after all. :(
