Can't compile a DLL from the Export menu without getting an error message??? Can anyone help
-
@GreekProgrammer you don't need to restart hise after creating the template. You can proceed to compile it right away.
-
Hi! Thank you for the reply!
As I am new to HISE and apologies if this seem a little silly, I don’t understand much about templates.I have seen a project button that shows the compiled script but can’t really understand what the message means? Should it be compiling something?
Thanks
-
@GreekProgrammer You need to compile HISE from source if you haven't already
-
@d-healey Hi! Thanks,
I have compiled from source (GitHub?) and when I unzipped the SDK folders the Steinberg Drivers etc still produced the error?
Also in the tools folder is a projucer app. I tried to load up the Standalone.jucer file to compile HISE and this still prevented it from working?Thanks
Any other ideas why this message may be appearing please? -
Have you set the path to the HISE source code in your project preferences?
-
Hi! I did see the option in settings (a small gear o. The top right?)
What do I need to do? What path should I set to sell HISE where the location is please.
Thanks
-
-
Great!
I did see this, but my program is not built from source as I reverted back to the exe version on the hose website download…
Should I try to rebuild a version using Juce and C++ again???
Could you screenshot an example please? Sorry to be a newbie !!!I see you have a media/d….in your screenshot
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
but my program is not built from source?
Did you compile from source or not? If not, you need to do that first.
-
Hi!
Thanks, I’ll have a go compiling from source once again, but It would be great to have an example of a path so I can Include this in my settings when I have do this!
Top guy thanks -
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
an example of a path so I can Include this in my settings when I have do this
The path is the path to the source code on your system, it's unique to you because only you know where you have put the source code.
-
Ah! I see…I’ll have a go. Hopefully this will work and I can begin setting up my RNBO patch with a HISE interface…
Thanks again
-
Hi! I have had a go at compiling but keep running into problems on windows using Visual Studio 2022? Errors. I have watched the Main YouTube Channel - is that you? A Yorkshire Man maybe like myself!
Anyway, not sure what to do now?
-
Having trouble compiling!
I have selected RELEASE from the build menu (CI/debug etc?)
-
Here's the latest..... I am pulling my hair out now!!!
I have compiled HISE via the most up to date developer source (branch GitHub), and gone through the tutorial on Installation. The main HISE site for installation using VS 2022. I first built a Debug that worked and then a release...all worked fine.
When I import an RNBO into HISE using the C++ using Tools and try to compile it, there is no DLL and I now get a new ERROR!
I have tried both Hardcoded MasterFX and ScriptFX nodes.
I have also made sure my Path Child is pointing to HISE with the core folder etc.. (as advised)
I would like to start using HISE, but this is strongly putting me off now!!!
Any Takers Please...????
-
@GreekProgrammer Sometimes I find I need to move some of RNBO's dependency files into HISE (not really sure why), but it usually solves my issues. It's not clear to me from what you have said, but you are able to build HISE successfully, but you are not able to import the RNBO file? There are other caveats to the RNBO import, like making sure the class and export name are the same, disabling polyphony, etc. https://docs.hise.audio/glossary/rnbo.html
It might be worth running a tester, simplified RNBO patch first before importing your main project, as this might reveal some issues with your RNBO patch and/or its compatibility in HISE.
-
@HISEnberg Thank you!
I have indeed moved the main rnbo folder into the ThirdParty\src folder with the rnbo output cpp files too? I have successfully built HISE no problem and am able to import the RNBO C++ files directly into HISE (again no problem.) it all goes pear-shaped when I export the DLL and the error for the PATH arises?Funnily enough (as you rightly say!) I have also ensured the Class and RNBO export are all the same name with the necessary options disabled (as per the link you sent.
I have followed the tutorial for the RNBO Chorus Pedal Extras and this imports into HISE no problem too...it's the PATH that is the issue?
HERE IS THE ERROR WHEN I SELECT EXPORT>COMPILE DSP NETWORKS AS DLL...
Thank you so much for your help with this though! :-)
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
I have selected RELEASE from the build menu
Looks like you haven't extracted the ASIO SDK, and looks like you're trying to compile the plugin version of HISE instead of the standalone.
Main YouTube Channel - is that you? A Yorkshire Man maybe like myself!
That's me!
-
Hi, I extracted the SDK files into the folder too and followed the JUCE online tutorial for the non standalone version!
I got so fed up with it all so I’ve deleted it!
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
JUCE online tutorial
What tutorial is this?
You need to compile the standalone version of HISE. You can't move forward with exporting your project until you've done this.
Delete all copies of the HISE source code on your system
Download the develop branch of the HISE source from github
Extract the sdk.zip file into the tools/SDK folder so it looks like the image below
Open the Projucer application included with the HISE source code >> tools/projucer
From within Projucer load the HISE standalone project >> projects/standalone/HISE Standalone.jucer
Still in Projucer select File >> Save and open in IDE - this will launch Visual Studio
Go to the build menu and select Build solution
