I Need Help...

[d.healey]

@ClawFORGE-Studio said in I Need Help...:

@ClawFORGE-Studio I reinstalled HISE and JUCE, with the SDK's as well

You don't need to install HISE or JUCE. You need to download the HISE source code (which includes JUCE) and compile HISE.

[Retromelon]

@d-healey Ohh ok lol. So yeah, now I rendered the project again, but I got some "compiler is out of heap space" errors in the CMD and then it compiled afterward, but now I don't know how to open the VST, and I only got these folders in the project files, so what is the next step to be able to run the VST ?

[d.healey]

@ClawFORGE-Studio The VST3 should be in your Binaries folder - I think it's in Binaries/Compiled on Windows but I could be wrong.

[Retromelon]

@d-healey Nope

[Lindon]

@ClawFORGE-Studio compiler out of heap space errors are when you have too many graphics(usually) in your project... remember its not the compressed size(png or jpg) that count its the uncompressed size.. reduce your image size/count. Use vectors...

[Retromelon]

@Lindon Ohh ok, well I don't have much going on honestly in the project, I have like 1 Image, 5 knobs and 2 buttons lol, but I do get those errors when trying to export it.

[d.healey]

@ClawFORGE-Studio Did you compile the develop branch of HISE?

[Retromelon]

@d-healey Ohh maybe that's what I forgot, I'll let you know if it worked

[Retromelon]

@d-healey Alright so I tried to compile it and that's what is showing me in the folder.

[d.healey]

@ClawFORGE-Studio Go into the x64 folder

[Retromelon]

@d-healey Alright, so I went to the App folder

[d.healey]

@ClawFORGE-Studio looks like you built the debug version, you should build the release version instead

[Retromelon]

@d-healey I tried but I got like over 100 of warnings

[d.healey]

@ClawFORGE-Studio Warnings are not an issue, it's the errors you need to worry about.

[Retromelon]

@d-healey Alright, I only got this error

[d.healey]

@ClawFORGE-Studio How much RAM do you have?

[Retromelon]

@d-healey 6 GB

[d.healey]

@ClawFORGE-Studio That might be the problem, try building with fewer CPU threads.

[Retromelon]

@d-healey Alright, so what are your suggestions for that ?

[d.healey]

@ClawFORGE-Studio My suggesting is to reduce the number of threads visual studio is using for compiling.