Error on HISE latest develop build
-
over and over the same thing
Severity Code Description Project File Line Suppression State
Error LNK1181 cannot open input file 'HISE x64 16 Out.lib' HISE_VST H:\HISE-develop\projects\plugin\Builds\VisualStudio2017\LINK 1and i search my hise folder and it doesnt exist. so its not being generated...
-
@mwplugs says go for reg lugin version
Severity Code Description Project File Line Suppression State
Error LNK1181 cannot open input file 'HISE x64.lib' HISE_VST H:\HISE-develop\projects\plugin\Builds\VisualStudio2017\LINK 1 -
@mwplugs cool good waste of a few hours lol ill stick with my 2 year old build that actually compiled until i get this sorted i guess
-
Did you try cleaning the build folder?
-
@d-healey yes :( any other ideas...
i looked and the .lib file its looking for doesnt exist within the hise folder, so the error is right its almost like it isnt creating it or that latest develop build is missing it?
-
@d-healey i read in your develop branch thread how one person had to update im trying that now
-
-
@d-healey VS2017 mine was from 2019 trying now
-
@mwplugs You can use 2019 but you have to retarget the project that Projucer generates
-
@d-healey im gonna try getting it thru as is. i swear i remember having to change the MFC in project settings to Static Library from Standard WIndows Libraries. but it doesnt say to do anything like that anywhere maybe i had to do that to compile vst3 or aax or something to do with IPP dont remember.
-
@mwplugs ugh same errors over and over
Severity Code Description Project File Line Suppression State
Error C2039 'getNumAllocated': is not a member of 'juce::Arrayjuce::var,juce::DummyCriticalSection,0' (compiling source file ....\JuceLibraryCode\include_hi_scripting_01.cpp) HISE_SharedCode h:\hise-develop2\hise-develop\hi_scripting\scripting\engine\javascriptengineexpressions.cpp 136Severity Code Description Project File Line Suppression State
Error C2039 'getNumAllocated': is not a member of 'juce::Arrayjuce::var,juce::DummyCriticalSection,0' (compiling source file ....\JuceLibraryCode\include_hi_scripting_01.cpp) HISE_SharedCode h:\hise-develop2\hise-develop\hi_scripting\scripting\engine\javascriptengineobjects.cpp 85Severity Code Description Project File Line Suppression State
Error LNK1181 cannot open input file 'HISE x64 16 Out.lib' HISE_VST H:\HISE-develop2\HISE-develop\projects\plugin\Builds\VisualStudio2017\LINK 1 -
@mwplugs it is trying to use this file HISE x64 16 Out.lib and hise isnt creating it. so it never finds it...
-
@mwplugs Are you compiling the plugin version or the standalone version?
-
@d-healey plugin multichannel. i need the 16 outs. and the standalone version cant export properly routed multiple out plugins only the multi channel plugin version
-
@mwplugs i would love to just use the standalone version but ive never gotten exported plugins to have more than 1 stereo out regardless of what i do
-
@mwplugs i know thats how it was 3-4 years ago not sure if that changed or if there is a way to make the standalone have multiple outs in the juce settings hmmm
-
@mwplugs Hi, i use only the standalone version to export multichannel instruments, I just implement a Routing Matrix based on combo boxes or if you don't want the user can change the routing you can fix the outputs with a script. You can't monitor the outputs in Hise but in the compiled plugin works fine.
-
make the standalone have multiple outs
Add this preprocessor definition in your project preferences
HISE_NUM_PLUGIN_CHANNELS=16You might also need to do some routing in the script, instructions in this thread - https://forum.hise.audio/topic/2479/build-fail-semantics-reference-to-point-is-ambiguous/35
btw did you try to compile the plugin version directly after compiling the standalone version?
-
@d-healey yeah ive implemented routing and multiple outputs in already compiled plugins i just know before a few years back hise wouldnt actually make the plugins multi out from the standalone only from the plugin version. that was many years ago. but im gonna see if i can get the standalone to compile. as the plugin version of the latest develop build is not working no matter what i try. now i rolled back a few days so we shall see.
-
@mwplugs is there something i have to input in JUCE to make the standalone version 16 out? i know you put that in your hise preferences ive gotten all that to work. but i just cant get any of these develop builds to compile.
