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.



  • @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)



  • @Christoph-Hart
    ahh ok, thank you.



  • ok peeps, im going crazy..
    so ive compiles plugins in HISE since 2019 so I know the ends and outs, but this....

    I cant compile a plugin on the standalone or plugin version..
    (I can but it wont open)

    Ive tries my plugin on multiple daws and same thing, the plugin wont open..

    Could I have messed something up in Projuicer?

    Everything works fine in HISE and it builds every time in visual studio 17 with no errors.

    😢 😢 😢



  • When you say it won't open, does the application crash? Does it open with just a blank interface? Does it not even load the app?

    My first recommendation is to copy the project folder over to a new folder and trash your Binaries folder.



  • @Lunacy-Audio
    it crashes before the interface pops up.

    My first recommendation is to copy the project folder over to a new folder and trash your Binaries folder.

    i'll try this



  • Build a debug standalone version, open it from the command line, tell us what the command line says when it crashes.

    You can also try using pluginval to see if it can shed any light on the issue - https://github.com/Tracktion/pluginval



  • Well guys.. After many test im still lost.
    I can build and compile plugins off my older commits (July) but not the newer ones.

    So my question is... with the latest commits can you export midi files on a compiled project?

    Thats all I needed to update for... but if it still cant be done i'll be ok for now.



  • @BWSounds well I've been here recently ---- the plugin would compile BUT reaper would tell me it wasnt valid and would reject it and pluginval would crash as soon as it tried to open the plugin.

    Turns out there was something (heaven knows what) wrong with one of my samplemaps. I rebuilt them all and it works flawlessly... perhaps its that?



  • @Lindon
    worth a try!



  • Before rebuilding all your sample maps you could make a new plugin with a single sample and try that.



  • @d-healey
    Yep it compiled and open!

    @Lindon
    so my next question is how do you rebuild samplemaps?

    Do I add everything all over again?


Log in to reply
 

11
Online

884
Users

3.2k
Topics

26.8k
Posts