what build of hise and IPP are people using to have working convolution....as ive stated mines broken.
-
@d-healey lol. im gonna try to compile without IPP first this second. i just knew i needed it for this project so not using it wasnt even an option. if i remembered i had to change things in project properties. IPP single threaded static or multi?...and code generation...runtime do we use /MT or a different option.
but im gonna start now compiling without IPP with my latest known working script node version from a few months ago..where i used convolution and everything successfully..
i saw the devloper thread i tried that...didnt work either
one second ill coile without IPP
-
ok @d-healey without IPP the distortion and digitized sound does not occur. so what do i do moving forward.
i have 2020 initial release (installed currently)
2019 initial release and 2018 update 2
my project setting are set to single thread static in VS2017
-
I'd uninstall IPP completely and install it again, whichever version you like to start with, if that doesn't work uninstall again and try a different version, keep going until you find one that works or you've tried them all.
-
ive already done that lol. why do you think i have so many different versions haha. the question i was asking people is what version are they using? like you what version is working for you?
-
@d-healey said in what build of hise and IPP are people using to have working convolution....as ive stated mines broken.:
I'm not sure how to check the version of IPP I'm using but it's one from around May 2019.
-
ok ill download the may 20th one and try after uninstalling
-
@d-healey 2019 update 4 (may 20) and current developer branch still produce the same issue wit IPP enabled. trying another version
-
in console it does say
Master Chain:! RELEASE_RESOURCES_CALLED
Master Chain:! RELEASE_RESOURCES_CALLED -
@d-healey also you can see what one you are using because it is in your add remove programs list on PC it says exactly what one it is
-
im 99 percent sure its a setting or something.....
IPP is enabled in projucer.. save and open
so when installing IPP what boxes do you check
i64 single or
i64 single and multior all i32 and i64.
what should you project settings be in VS2017 when compiling hise. single thread static..multithread static...single dll multi dll...
in MFC "use of standard libraries" or something different
in code generation /MT or something different
i have tried every version of IPP now it has to do with some settings
-
-
@mwplugs said in what build of hise and IPP are people using to have working convolution....as ive stated mines broken.:
@d-healey also you can see what one you are using because it is in your add remove programs list on PC it says exactly what one it is
Yeah but that means firing up my Windows machine :p I only do that when I need to compile a project.
Have you changed HISE version since you last had it working successfully?
-
yeah i went all the way back to 2018 update 2 which is the oldest and it still did the same thing so like i said above i think it has to do with setting when compiling in VS2017
-
so i need to know asap..
what version of hise i should be using
what IPP i should be using for vs2017 on pc
i have the proper sdk setups
are there any special settings to change in vs2017..or hise to make IPP work
i really need to get this done and it seems like such a silly thing...
-
what version of hise i should be using
The most recent one you can get to build
what IPP i should be using for vs2017 on pc
ustk said I remember it was risky to go above IPP 2019 v4 with Hiseare there any special settings to change in vs2017..or hise to make IPP work
None that I recall
-
from what branch is best to get it from
-
@mwplugs i always assumed the scriptnode versions with the red x meant they didnt compile
-
alright i may have found a clue @d-healey
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets \v141\ImportBefore\Intel.Libs.IPP.v141.targets(90,43): error MSB4086: A numeric comparison was attempted on "$(IPPMajor Version)" that evaluates to "" instead of a number, in condition "'$(IPPSingleThreaded)'=='0' AND ('$(UseIntelIPP)' == 'Sequential' OR '$(UseIntelIPP)' == 'Sequential_Dynamic' OR ('$(UseIntelIPP)' == 'true' AND '%(ClCompile.OpenMPSupport) ' != 'true')) AND $(IPPMajorVersion) > 7". [D:\!PLUGINS!\Sting\Binaries\Builds\VisualStudio2017\The Sting_SharedCode.vc xproj] -
look @Christoph-Hart i have tried every version of IPP now that is available for download...they all produce a crackling digitized noise with EVERY SINGLE IR i have used from every source via the net..home made etc. EVERY ONE. its broken..and not even just a little. like completely unusable. im not sure why hise breaks every month but i literally just used convolution with IPP in late jan and it worked perfect. now no matter what combination of hise version and IPP version i use basically my plugin ive been working on for 3 years is basically useless.
i just want ONE version of HISE that doesnt break. i had done nothing at all and its just broke..even with just a convolution as the only element of a compiled plugin. whenever IPP is enabled its broken.
-
@mwplugs You said you tried combinations of every Hise version with every IPP version... How Hise could be broken then? I'm sure if you tried all these combinations, at a moment you must have compiled the same working combination that you worked with before right?
Also when you have a working version, you should make a backup before compiling a new one...
Personally, it's working here and I'm sure it's working for many people so the problem has great chances not to be Hise...
I'm on mac though, but I don't know if it makes any difference here...
I'm using Hise from January 20 (I stopped updating since Christoph is on V3), and IPP 2019-4 (versions above are known to cause issues with Hise, at least it happened once for me so I got back to v4...)What is your CPU saying when an IR is crackling?
