ERROR at Exporting: "The system cannot find the file specified."

  • Hello,

    I have this error message in the black "Dos-window" when exporting:

    Re-saving file: D:\laciporpcd\HISEprojects\Hp20181020c\Binaries\AutogeneratedPro
    Finished saving: Visual Studio 2015
    Finished saving: Xcode (MacOSX)
    Finished saving: Xcode (iOS)
    Compiling 64bit Instrument plugin Hp20181020c ...
    The system cannot find the path specified.
    Compiling finished.Cleaning up...
    The system cannot find the file specified.
    The system cannot find the file specified.
    Press any key to continue . . .

    I registered here with a LeeMartin username, but it is just an artist name I tend to use on internet forums and stuff,
    but my real name has non-English characters in it,
    and that makes my Windows "user-folder" ("c:/Users/[THIS FOLDER]") name has 2 non-English characters in it.

    Do you think that might cause this problem,
    or is it something totally different?

    I've tried to export VSTi 32-bit, 64-bit,
    and also Standalone
    but I've got the same error message.

    What should I do?

    Thank you for your help!

    Have a nice day!

    (PS.: A few months ago I successfully exported all the Windows-stuff (VSTi 64-bit, 32-bit, Standalone 64-bit, etc..),
    and I can't remember how I setup back then,
    I've tried to follow all the Tutorial pages and videos on the HISE website,
    and the exporting still failed with the same error message.)

    (PS#2.: I am on Windows 8.1 64-bit, which I've tried the exporting on)

  • Have you set the HISE path in your project settings?

  • Thanks for the lightning fast reply!! 😮

    I set this path to the Compiler settings:

    "HISE-1.5.0" is the HISE Source folder I downloaded,
    (and if I remember well in the past it was called "hise-master" or something like that,)
    and when I get inside this HISE-1.5.0 I see folders like:

    Is this the correct folder, right?
    I set this one.

  • @leemartin That's the correct folder. But HISE 1.5 is ancient (even though it's the latest official release) have you tried building the develop branch from source?

  • @d-healey
    Haven't tried it yet, if you think that would solve the problem,
    then I will try to build HISE from source now,
    (I saw you have a YouTube video on it and your videos are really helpful!)
    and I will report back here.

  • @leemartin My video is out of date too but it's mostly still relevant. You need to use Visual Studio 2017 with the newer version of HISE.

  • @d-healey
    Visual Studio 2017 is already installed ready to go thanks to some AmpleSound library that automatically installed it, and I saw I can select VS 2017 in HISE's Compiler settings,
    Good to know, thanks for the info! 👍
    I will select that when I'm at the exporting part.

  • @d-healey
    I downloaded the latest HISE Source from GitHub,
    and indeed now it has the "HISE-master" folder name.
    I followed your video,
    but I stuck at the point when I have to click on "Save Project and Open in IDE...",
    I've found that thing in the menu toolbar, but after I click on it,
    Windows asks me that "How do you want to open this type of file (.sln)?"
    And it shows me the Windows store icon and gives 2 options:
    1.) "Look for and App in the Store"
    2.) "More options"

    and when I click on more options it wants me to select an application from a list or from my computer by giving a path on my hard drive.

    Why I get this message from Windows,
    and what should I do about it?

    Thank you!

    (PS.: I set everything to Visual Studio 2017 in Projucer "Selected exporter: Visual Studio 2017", and also I clicked and highlighted the "Visual Studio 2017" on the left side of the Projucer-window (in the Exporters list (or what is it, sorry I lack of correct terms))

  • Oh, I'm sorry, I just checked my "Programs and Features" in Windows, and it shows that I don't have Visual Studio 2017 installed, my fault, I'm sorry, I could bet on it it is installed, now I'm downloading it.. I'll get back here after I installed it and tried to continue following your video....

    (I have VS 2005, 2008, 2013, 2015 installed but not 2017.... sorry again)

  • @d-healey
    There was a misunderstanding on my part what even Visual Studio 2017 is,
    sorry about that,
    but now I've downloaded and installed Visual Studio 2017.
    And also (maybe) successfully built HISE from Source.
    (I didn't get any errors and warnings.)

    But when I re-made from scratch my simple 1 .wav file sample library test project with this new HISE and tried to export it,
    it started the export in the "Dos-window",
    but after a few seconds it stopped and it gave me this error message:


    Re-saving file: D:\laciporpcd\projects\HISE projects\Hp-2018-10-20-d\Binaries\Au
    Finished saving: Visual Studio 2017
    Finished saving: Xcode (MacOSX)
    Finished saving: Xcode (iOS)
    Finished saving: Linux Makefile
    Compiling 64bit Instrument plugin Hp-2018-10-20-d ...
    Microsoft (R) Build Engine version 15.8.169+g1ccb72aefa for .NET Framework
    Copyright (C) Microsoft Corporation. All rights reserved.

    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VC
    Targets\Microsoft.Cpp.WindowsSDK.targets(46,5): error MSB8036: The Windows SDK
    version 10.0.16299.0 was not found. Install the required version of Windows SDK
    or change the SDK version in the project property pages or by right-clicking t
    he solution and selecting "Retarget solution". [D:\laciporpcd\projects\HISE pro

    Press any key to continue . . .


    When I built HISE with Visual Studio 2017 (MY FIRST TRY) it gave me an error message that said something about that the "Windows SDK Version" is not correct, or can't find it,
    and it gave me a tip what to do,
    the tip was that I should right click on the "Solution" choose "Retarget solution",
    so I did that,
    and after that I got HISE built without any Errors or Warnings.

    So this Windows SDK what it tried to find is Version 10.0.16299.0,
    but what the Visual Studio 2017 retargeted is Version 10.0.17134.0 (or something like that, I might remember the exact number wrong, but it was a newer version).

    What should I do next?
    Can I set something about this inside HISe,
    or I have to build it again from source with different settings in Visual Studio 2017,
    or I have to download this Windows SDK Version 10.0.16299.0 from somewhere,
    or something else?

  • @leemartin
    (Sorry about the giant font size, I don't know how I did it and I can't find the way to change it back to normal font size.)

  • @leemartin You have to download the correct windows SDK. I haven't used Visual Studio for a long time but the option is in one of the menus (perhaps the tools menu) to add component to visual studio and in there (once you find it) you'll be able to add the correct SDK version.

  • @d-healey
    Finally I (think I) successfully built HISE from Source.

    There is a small but important note:
    I downloaded the Windows SDK,
    and I've found out that is the newest version,
    which for some reason HISE Exporter didn't like or something,
    so it needed exactly the 10.0.16229.0 Windows SDK Version,
    and I could get that only by opening the Visual Studio 2017 installer again,
    and I had to click the "Modify" button,
    and I had to check the "Windows 10 SDK (10.0.16299.0) for Desktop C++ [x86 and x64]" checkbox

    Now that I have HISE working,
    I already successfully Exported a 64-bit Windows VSTi with it,
    but now I just don't know what settings I messed up in HISE,
    because I loaded the exported VSTi successfully into my DAW,
    and the plugin is asking for samples,
    the exported plugin asks:
    "Please click below to install the samples from the downloaded archive or point to the location where you've already installed the samples."

    and there are 2 buttons:
    1.) "Install Samples"
    2.) "Choose Sample Folder"

    (My HISE project's name (so my exported VSTi plugin's name) is "Hp-2018-10-20-g".)
    When I click on the "Install Samples" button,
    I get a message with this Title:
    "Choose the Sample Archive"

    And the message itself is this:
    "Please select Hp-2018-10-20-g Resources 1.0.0.hr1 file that you've downloaded"

    Then I click the "OK" button,
    and it wants me to find an ".hr1" file,
    but I don't know where it is,
    or what should I set differently in HISE before I re-try exporting again.

    I would like to tell HISE to NOT MAKE any sample folder outside the exported plugin,
    just EMBED the sounds in the exported plugin itself.

    The "Embed Audio"-thing was turned ON.

    I seemingly I successfully installed the samples for the exported VSTi (the exported VSTi wanted me to do this),
    but now I have another message from the exported VSTi,
    it says:
    "The sample directory could not be located. Click below to choose the sample folder."

    I'm stuck at this point again,
    because after I give it the directory with the Windows "file-manager-browser"-thing,
    I have the same message that I got first time:
    "Please click below to install the samples from the downloaded archive or point to the location where you've already installed the samples."
    and the same 2 buttons

    I did it one more time,
    but this time I got an "Ignore" button too,
    so I tried that out,
    and now any time when I load this exported VSTi, I don't get any sound of it,
    I get the plugin, but there is no sound,
    and now I don't get the messages and the buttons,
    so I can't choose sample locations too.

    So I will re-build this VSTi,
    but what should I do differently?
    What should I do differently for have the samples embedded inside the VSTi's .dll file (or how it works I don't know)?

    Can I set this up without any sample folder, but using only embeded sounds inside the VSTi dll file itself somehow?

    Sorry for the long read, and thanks for your patience,
    I'm just trying to figure this out,
    but it's a little bit hard for me,
    I'm not a programmer or developer,
    I'm just interested to experiment with HISE,
    so if I can understand it better,
    I might make some simple sample libraries for myself first, I guess, I who knows the future..

  • Hi,
    If you're just using the instrument for yourself and not to give to others, you can select the option Choose Sample Folder and then select the folder where your samples are.

    Otherwise you might find this article helpful -

    You can create the hr files from within HISE by going to Export >> Export Samples for Installer. For this to work you must have first saved your samples as monoliths.

    The embed audio files option only applies to impulse response files. Samples are never embedded in a HISE plugin.

    I'm not a programmer or developer,

    You are now 😉

  • @d-healey
    I'm pretty far from being a developer yet, I can't even setup HISE 🙂
    But thanks for the encouragement and your help!

    Now I have a new problem:
    I don't get 2 buttons (I don't get "Install Samples" and "Choose Sample Folder" buttons),
    but I get only 1 button, it says: "Ignore"

    And the text above the button is this:
    "The sample directory does not exist."

    I don't know how to get back the original 2 buttons ("Install Samples" and "Choose Sample Folder"),
    I built the VSTi again and again, but it has only 1 button now ("Ignore" button only).

    I must do something wrong about path settings,
    but I don't know where so I will try to go step-by-step.

    MY GOAL:
    I just want a VSTi exported from HISE,
    that I can use in my DAW,
    I don't want to sell it or anything like that.

    (At least not yet for sure.)

    I will open HISE.

    I click on "Export" (in the top menu),
    and I click on "Clean Build directory"

    So now
    should I click on "Export" >>> "Export as Instrument (VSTi / AUi) plugin"
    should I click on "Export Samples for Installer"

  • @leemartin The article I linked explains what to do to reset everything

    If something went wrong with the extraction process and you want to start over; go to the folder that contains the configuration files for the sample library and delete all the files it contains. Then reopen the sample library and everything should be just as it was before you extracted the samples. To determine the location of the configuration files on your operating system see the Configuration files section at the end of this document.

    No need to Export Sample for Installer for your use case.

  • @d-healey
    Thank you, Isaw that in your link earlier, but when I check this path to delete the configuration files, they were not there
    not here: Windows: Users/username/AppData/Roaming/LibreWave/
    probably I just messed up something I don't know, sorry about that,

    but I just built the VSTi again, and it worked as it should first time, it gave me the 2 buttons,
    and I chose "Choose Sample Folder"

    now my mini test VSTi sample library thing works in the DAW too

    Thank you for your patience and help! I appreciate it very much, and I'll remember that (although I'm nobody 😄 )

    I'm gonna come back with other issues probably with my next sample library test with a few more samples, maybe with round robins or even crossfades, I saw your video about it, it looked useful and easy to understand, I don't know maybe I have some kind of disleccic problem a little bit, but I can learn way more easier and faster from hearing somebody talk to me, or just watching a video how they do something, so I'm gonna follow your other videos now,

    Are there going to be some more tutorial videos for HISE in the future about various stuff that HISE can do? I mean not only HISE-specialties or HISE VS KONTAKT video,
    but anything really, any kind of HISE feature,
    like a full-on tutorial YouTube playlist from A to Z, or something like that maybe?

  • @leemartin Glad you got it working! I'll be adding more HISE tutorials when I find time. Hopefully I'll get around to doing some scripting videos too.

  • @d-healey
    Sounds awesome, thank you for your efforts and help again!

    Now I will open another topic for another little problem, and I promise it's little 😄

Log in to reply