Just want to see where im at..
-
commit a44b51b9bbcf620441c03bfd3ded4b88fe043e35Is the latest commit, im having trouble with the compiled vst from this commit,
is anyone else having trouble? if not then it's on my end and I'll have to figure it out.If so then I'll patiently wait for the next commit.
im on Windows and the compiled vst is not opening, throwing an error every time I try to open it.
-
throwing an error every time I try to open it.
What's the error?
Does the standalone work? -
Works here, Win10. Compiled VST3.
-
@d-healey
plugin, I've never used standalone.
So when I open the compiled plugin in my DAW is just saying"There was a problem opening this plugin for unknown reason
please make sure its installed correctly"I've never had this problem before.
-
@dejans
ok I must have screwed something up some how, thank you -
Always test standalone first, if standalone doesn't work then there is a problem with the project, if plugin doesn't work the problem could be with the host or the plugin so it's harder to debug.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey
Ok, thanks peeps.
I’ll get to work then! -
could this be why perhaps?
Red text never seems like a good sign
-
@d-healey what's the standard process of debugging?
-
@BWSounds
Yep , red text is not good.what's the standard process of debugging?
There are different techniques depending on what you are trying to debug. I always work in HISE standalone and debug exported projects as standalone before trying to fix issues that occur with exported plugins.
I use
Console.print()if I need to follow the flow of code (I guess you could also use breakpoints for this but I'm a simple creature).HISE doesn't have an automated system for testing user interaction so that has to be done manually - if you want to know what happens when a user moves a knob the easiest way to test is to move the knob (and put Console.print() in its callback of course).
If you want to test individual functions then unit tests are a good idea, although not usually neccessary with smaller projects.
-
@BWSounds said in Just want to see where im at..:
could this be why perhaps?
Red text never seems like a good sign
SO this red text... I cant figure out what path it's suppose to go to.
It's like that for...
-hi_snex
-hi_streaming
-hi_tools
-hi_zstd
-stk_wrapper -
These are all directories in your HISE source folder.
-
So point them to those individual folders or the whole source folder?
-
I think something's wrong with your setup, are you on the latest scriptnode version? The path I have for those is
../../ -
@d-healey
yes, commit a44b51b9bbcf620441c03bfd3ded4b88fe043e35 -
-
Oh yeah I didn't check VST, why are you using the VST version of HISE? The only time I use it is to test audio effect plugins, everything else I can do from standalone.
Try changing all the paths to
../../ -
@d-healey
So I can compile a plugin version with the standalone? (honest question)
Also I built a standalone version last night, it wouldnt open the compiled project either :/
Im going to delete and retry everything, this has never happened before with me. -
I was able to compile the plugin version just now after changing the paths to what @d-healey suggested above. Plugin version opens without a problem.
Edit*
A bit more specific, I loaded the plugin version into Fl Studio and it loads without problems, also will load up any of the projects I have previously created with standalone version. -
So I can compile a plugin version with the standalone?
Yep. When you compile your HISE project it always uses the compiler on your system (VSStudio, XCode, etc.) no matter if you use the export option from the Plugin or Standalone version of HISE.
