MSB1009 error when compiling



  • I'm trying to compile a Windows VST plugin (64-bit) using the Basic Synth project to test it out in my DAW, but I always get the MSB1009 error when compiling. I've gone through the tutorial twice and everything seems to be at the right place.

    Does the Hise source code version need to match the Hise version I'm using to avoid any compiling errors? I downloaded the latest version of the source code and I'm using the Hise version that can be downloaded on the website, which is not the latest version from what I understand. Could it be the problem?



  • @SampleScience

    the MSB1009 error

    What is the error?



  • @d-healey said in MSB1009 error when compiling:

    @SampleScience

    the MSB1009 error

    What is the error?

    The only info I got from Hise is this error code (MSB1009) and after that I get a compiling error message. I wish I could tell you more but that's all Hise is giving me.



  • @SampleScience Could you post a screenshot?



  • @d-healey said in MSB1009 error when compiling:

    @SampleScience Could you post a screenshot?

    I download the latest release and the latest source code and now it works! I can compile the plugin but I don't see where it is. From the tutorial, it's supposed to be in the binaries folder of the project folder but it's not there.

    Any idea of where the VST plugins are exported currently?



  • Binaries/Builds/VisualStudio2015 I think



  • @d-healey said in MSB1009 error when compiling:

    Binaries/Builds/VisualStudio2015 I think

    I don't have this patch. The only thing I have is this:

    HISE\Projects\BasicSynth\Binaries\Compiled\Shared Code

    And the folder is empty. I had a look around and I don't find any VST. I'm going to try to export another project from the example projects I got from Github.



  • Ok, I did the MusicBox and I have the same problem. If I click OK on "Do you want to validate all sample references" I get "wrong/missing sample reference". I click on OK and I get "Sanity check failed. Aborting export...".

    These problems occur with the examples projects and the latest release + latest source code. I added the ASIO and VST3 SDKs at the right places and I have Visual Studio 2017 installed. I use Windows 7 (64-bit Professional).

    Any ideas of what's going on?

    I think that to implement a simple exporter like the one found in Maize Sampler would make the plugin creation much easier. As it is, it's been a few days following the tutorials and I've gone through quite a lot problems.

    I really dig Hise though, I think it has the potential to be great and it certainly eases the process of creating plugins. I'll put in a few more days to see if I can compile at least 1 plugin.



  • @SampleScience When it asks to validate the sample references click no/cancel. There is clearly something not right with the sample references since it's giving you an error there. But the plugin should still compile without them.



  • Ok, here are 2 screenshots of the messages I have when I compile Windows VST 64-bit plugins.

    https://imgur.com/nU5Lggj
    https://imgur.com/fadLiKT

    One is for MusicBox and the other BasicSynth. I don't use IPP so it's unticked in the preference (I try to make things as simple as possible).



  • These message are not from HISE, these are from Visual Studio. They are just warnings, nothing to worry about by the looks of it. If it says error or failed then it's a problem.



  • @d-healey said in MSB1009 error when compiling:

    These message are not from HISE, these are from Visual Studio. They are just warnings, nothing to worry about by the looks of it. If it says error or failed then it's a problem.

    What I do if the exported plugin isn't in the Compiled folder of the projects? What could be the cause of this problem? (By the way, your help is really appreciated)



  • @SampleScience I don't use Windows much and I can't remember the file location but I thought it would be in the build folder. Have you tried running a search on the project directory for a .dll?



  • @SampleScience your compiled plug in is in

    {PROJECT FOLDER}/Binaries/Compiled/VST

    or if you are building a stand alone app:

    {PROJECT FOLDER}/Binaries/Compiled/App



  • @Lindon said in MSB1009 error when compiling:

    @SampleScience your compiled plug in is in

    {PROJECT FOLDER}/Binaries/Compiled/VST

    or if you are building a stand alone app:

    {PROJECT FOLDER}/Binaries/Compiled/App

    I've looked in those paths and there's nothing. There must be something funky with my computer. I'm going to try on another computer with Windows 10 to see if it fixes the problem.



  • I gave it a try on macOS, surprisingly it's much easier and it works better and faster.

    However, even if I can compile the plugin, I have the same problem. I export the VSTi + AUi and there's nothing in the binaries folder of my project. Clearly, there's something I must be doing wrong.



  • Got it working now, using a different project. It seems that the BasicSynth example is somehow outdated and doesn't export well. I've tried the MusicBox after installing everything the Visual Studio 2017 installer offered me to install and now it works! ☺

    The basic tutorial for the MusicBox really need to be updated, some of the files that are referred don't work with Hise v2.0 (it links to an older v1 version source code).

    So now I'm creating a basic synth that I will test on different computers for export (my mac and 3 other windows computers I use for work). We'll see what happens. Hopefully, everything will work and export properly.



  • Yeah the tutorials definitely need to be updated for the next major release.



  • @Christoph-Hart said in MSB1009 error when compiling:

    Yeah the tutorials definitely need to be updated for the next major release.

    I'm going through the manual and it seems incomplete too. I wish I could help somehow, but I'm far from been a Hise expert (yet).

    Maybe an upfront cost would be a good idea. Maize Sampler cost 66$ USD and it's not even close to Hise in terms of functionalities.



  • There‘s a new documentation system in the works but currently the best and most up to date source of information are David‘s videos from his Patreon page.

    An up front cost is not really compatible with a GPL project so that‘s not really an option. Also throwing money in my direction will not magically multiply the time I have available 😉


Log in to reply
 

8
Online

536
Users

2.0k
Topics

15.8k
Posts