Hise will not export
-
@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. :(
-
@gryphonsegg so when exporting the hise standalone from projucer my exporter should be VS 2022 yes?
-
@gryphonsegg Yes, it should match the version you have installed.
-
@d-healey and if it says nothing about IPP in projucer in the extra processor definitions do I stll need to add it in?
-
@gryphonsegg If I remember correctly with the latest version of IPP you have to select OneAPI from a drop down menu.
-
-
@d-healey yeah I did that. what about in the other section I stated when using VS 2022 where you actually need to type in USE_IPP=1 ?
-
@gryphonsegg I don't think that's necessary any more. But either way you haven't hit any IPP related problems so I wouldn't worry about it for now.
-
@d-healey I'm really bummed because I want to really sue HISE. I have been using flowstone 64 alpha and experimented with max 8 a little but too hard to compile from, and Romplur just makes ample based instruments. I really need to figure out what is happening here.
-
I'm really bummed because I want to really sue HISE.
Well you are using HISE. You just have to compile your projects manually until you figure out what's going on with the configuration.
-
@gryphonsegg I recompiled and built it all making sure 2022 VS was my eport etc and re opened it and tired again after putting in the new file path and NOPE. same fail. what could be doing it?
-
-
delete all the HISE folders you have.
-
re-download the HISE-develop branch
-
unzip it and rename the folder to HISE
-
rebuild HISE
-- tell us how far you get...
-
-
@Lindon rebuilding now
