Export Issues (Tried It All)

[trillbilly]

Hello,

My name is Aaron. I am new here to HISE & Development. I swear I have tried everything under the sun on the forum to get my VSTi to correctly export.

I receive the following error (which seems fairly common so Im unsure why I cant figure this out!)

Re-saving file: E:\HISE VST Builder\VST Instruments\Jalisco - Acoustic Guitar\Binaries\AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (MacOSX)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin Jalisco - Acoustic Guitar ...
The system cannot find the path specified.
Press any key to continue . . .

1. I have my HISE Path in 'Preferences' set to the Parent Folder of 'hi-core, hi-modules, etc.'

2. I have taken the 'AutoGeneratedProject' Projucer file, loaded it in JUCE & opened with IDE. I receive errors in VS2017 that prevents the build from taking place. Errors all look to be "ipp" path related.

3. I installed the IPPs suggested & necessary to create & use HISE. I even had to go back and add another necessary SDK pack.

Any help is appreciated. Thanks in advance!

Aaron

[d.healey]

Which version of HISE are you using?

[yall]

@itsmochajones the path must be the global folder, not just the h core folder. rejoice in it. and get the latest version of scriptnode

[trillbilly]

@d-healey I believe 2.0. It was the most recent version on GitHub.

[trillbilly]

@yall Yes, I have the parent folder as the path, not just the 'hi-core' folder.

[d.healey]

@itsmochajones said in Export Issues (Tried It All):

@d-healey I believe 2.0. It was the most recent version on GitHub.

Build the scriptnode branch.

[trillbilly]

@d-healey I guess Im a bit confused on this part. When I click 'scriptnode' in the link, it looks like the same download I previously viewed to initially get HISE.

[d.healey]

@itsmochajones Git allows a developer to create multiple version of their code to make it easier to work on different features. Each version is called a branch.

The link you clicked took you to the Scriptnode branch, when you go to the download link you will be downloading that version of the source code. An even better way is to do this using git, but that's a little more difficult for someone unfamiliar with git.

You should delete any other versions of the source code that you've already downloaded, only have one on your system at a time, otherwise things can get easily confused and problems can be more difficult to resolve.

[trillbilly]

@d-healey Ok, just to ensure Im following you fully.

1. Remove HISE as it stands right now including all files/docs/code/etc.
2. Download via the 'scriptcode' provided.
3. Rebuild HISE with new 'scriptcode'

correct?

[d.healey]

@itsmochajones Correct

[trillbilly]

@d-healey Thanks for your help. I will do this now and let you know.

[trillbilly]

@d-healey Hello,

I am attempting to re-build HISE with the 'scriptnode' provided and recieve multiple "Fatal Errors" from VS2017. All Errors have to do with the 'hi-streaming' directory it seems.

1>e:\hise-scriptnode\hise-scriptnode\hi_streaming\hi_streaming.h(69): fatal error C1083: Cannot open include file: 'ipp.h': No such file or directory (compiling source file ....\Source\MainComponent.cpp)

ASIO and VST3 both in correct location (HISE-scriptnode\HISE-scriptnode\tools\SDK). What am I forgetting?

[d.healey]

@itsmochajones This is telling you there is a problem with IPP Cannot open include file: 'ipp.h'. Completely remove any references to IPP in the .jucer file (you can always enable IPP another time if you need it once you get a basic build working).

Make sure the USE_IPP flag is set to 0 as well
.

[trillbilly]

@d-healey Thanks, this seemed to work but with many errors. So if I want to eventually use the IPP for reverbs and such, what would be my best practice to get it up and running correctly?

[d.healey]

@itsmochajones

this seemed to work but with many errors.

Those are warnings which can be safely ignored, if you have errors then it wouldn't have worked.

So if I want to eventually use the IPP for reverbs and such, what would be my best practice to get it up and running correctly?

@Rudra-Ghosh Is the person to ask.

[trillbilly]

@d-healey Yes, warnings, my mistake.

And awesome, Ill contact them when needed. You help was greatly appreciated.

Aaron