Just want to see where im at..



  • @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
    alt text

    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



  • I just loaded the plugin version in Projucer and it has the same red text as @BWSounds is showing. Standalone doesnt have this issue when loaded in Projucer.

    I have those same paths in Standalone version @d-healey.



  • 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.



  • @BWSounds

    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.



  • @d-healey @Dalart said in Just want to see where im at..:

    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.

    I can do that as well but the plugins im compiling wont open... my standalone compiled plugin wont either so, I must have messed something up somewhere.



  • @BWSounds Yeah it has to be something on your end Im thinking because I was able to export the basic synth vst tutorial from the HISE plugin version and load it up in FL Studio without issue.

    I followed @d-healey 's video to compile HISE to avoid any errors.



  • @BWSounds said in Just want to see where im at..:

    @d-healey @Dalart said in Just want to see where im at..:

    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.

    I can do that as well but the plugins im compiling wont open... my standalone compiled plugin wont either so, I must have messed something up somewhere.

    How did things turn out for you @BWSounds ?



  • @Dalart
    Same issue, ive compiled plugins probably 50 times over the last 2 yrs trying and testing different things...

    I honestly don't understand what's happening, unless I deleted something important when I uninstalled visual studio 19 🤷♂ .
    But your text was red as well so... im going to try on a mac today and see what happens.



  • @BWSounds I used VS2017 to compile, and I changed the red text for the paths to: ../../
    I also have the iPP installed and integrated with VS2017. I haven't done anything else different I don't think.



  • @Dalart
    I remember once having issues with the ipp, might look into that a bit more..
    I had to have changed something, just need to figure out what it was.

    Maybe its my project, I'll try to compile one from the HISE tutorial folder.



  • @BWSounds said in Just want to see where im at..:

    @Dalart
    I remember once having issues with the ipp, might look into that a bit more..
    I had to have changed something, just need to figure out what it was.

    Maybe its my project, I'll try to compile one from the HISE tutorial folder.

    Compiling a tutorial to test is a good way to start, it at least lets you see if you can actually compile a working plugin. If successful in that, then you can narrow down what's causing it in your custom project(s).



  • There‘s also a minimal project in extras/demo_project directly in the repo.

    But the red folder is indeed a mistake, it requires my folder structure to work, I‘ll change it (I almost never compile the plugin version)


Log in to reply
 

16
Online

963
Users

3.4k
Topics

29.2k
Posts