Hise will not export
-
@Lindon one as far as I know but I had one on here a year ago when I had spoke to you way back. If it is on here its on another drive and I dont know where it would be given that I am on about a 32 terrabyte system. I can look. Would that keep it from exporting as a VST though?
-
@d-healey one as far as I know but I had one on here a year ago when I had spoke to you way back. If it is on here its on another drive and I don't know where it would be given that I am on about a 32 terabyte system. I can look. Would that keep it from exporting as a VST though?
-
@d-healey thoughts?
-
@gryphonsegg In your path to Hise you have first HISE-develop, and then inside that folder you have HISE, it seems you have the Hise code inside the Hise code or something?
I have this path to my Hise code:
try to set your path to "F:\red specter VSTs\HISE-develop
-
@ulrik when you unzip the download you can name it whatever you want, it unzips it into a hise-develop folder, then into another hise-develop folder, I changed the name to test it, it still accepted the folder either way and did not let me export either way.
-
Did you extract the VST3 and ASIO SDKs?
-
@d-healey yes I did
-
-
@ulrik
yes it does -
@gryphonsegg Ok it looks right, and your path to Hise ends with "HISE-develop/HISE-develop"?
-
@ulrik yes sir
-
@gryphonsegg hm..strange
-
@ulrik everything works except the failing on the export, and it fails on vst or standalone or anything I try to export. Just says cant find the file path.
-
@ulrik I even moved the HISE-develop source folder to my c drive and checked it there, same thing, so I moved it back.
-
@d-healey when it says it cannot find the path specified, which path specifically is it referring to?
-
@gryphonsegg I also made sure that all the permissions were not blocked and I even turned off my virus protection
-
@gryphonsegg said in Hise will not export:
@d-healey when it says it cannot find the path specified, which path specifically is it referring to?
Can't remember but I think it's the Visual Studio path.
Open the .jucer file that was generated by the export, this will be in the binaries folder. When it opens in Projucer go to File >> Open in IDE, and make sure it opens VS2017, try exporting it directly from VS2017. If it works then it probably means the error is due to having both versions installed and the automated system is picking the wrong one.
-
@d-healey I cant find the binaries folder
-
@gryphonsegg Inside your project's folder.
-
@d-healey my projects folder only has pl,ugin and standalone in it and no binaries folder in the ones inside. I need afile path if possible
