@nesta99 Check that Projucer is at that location and works.

@orange said in AAX Compiles...:

While compiling as "All platforms", have you selected VST3 or VST2?

If I select VST2, "All platforms" work. but if I select VST3, "it doesn't work. I think it is because AAX plugins use .dll (VST2) platforms inside.

err , not here they don't - the AAX compiles a VST3 and the uses that...unless I'm very much mistaken(which is a distinct possibility..)

commenting for the next time I forget how to do this 😂

https://forum.juce.com/t/how-to-define-other-ldflags-in-projucer-project/44836

@Christoph-Hart Can we get a cheeky fix for this please 😀

https://www.youtube.com/watch?v=VQleWPrXnfw

@yall Correct (y)

No it‘s not expected behaviour but it‘s one of the more useful easter eggs in HISE :)

That was it. The VST exported!
Thank you :D

I solved the problem! 🎊

Essentially I had an old installation of the Build Tools present on my system, so when I installed Visual Studio 2017 I then had a duplicate build environment that was lacking the correct windows SDK (because I had been a dummy and installed the windows sdk into the build tools instead of vs2017).

So I uninstalled the Build Tools via the Visual Studio Installer leaving only VS2017 installed.

After that I removed the CL= environment variable entirely from my system and added

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64

to the PATH environment variable so that cl.exe could be executed from anywhere.

From here on it was following the video guide basically.

I added the Windows 10 SDK (10.0.16299.0) by modifying the VS2017 installation in the Visual Studio Installer.

Then I opened the HISE standalone project in projucer and built the HISE.exe as per the video instructions - this time no warnings of mac files detected!

And finally I ran HISE, added a sampler and an empty UI, exported it as VST3 64bit and success! 🎉

Now I can go back to actually making my instrument 😂

@nesta99 i would do it next week on another pc i have. my procedure was like the rest. i went to the intel ipp site. I downloaded the toolbox offline, I installed all the components. then i downloaded visual studio. I launched a first compilation which failed because I had not installed the visual studio module (when you get an error it will tell you to download the modul x3737838388 for example). once you know the right module you go back to the visual studio installation and check the box corresponding to the module. then you relaunch your compilation and it works. concerning ipp I have the latest version because I downloaded it a few weeks ago

I don't like fighting with the MIDI sources list LAF so I wrapped the functions in the scripting API instead so we are no longer tied to the floating tile.

It doesn't update the floating tile until I press the UI refresh button, but the idea is you'll use the API instead of the floating tile so it shouldn't be a problem in practice. I might wrap some more of these settings API functions too...

Peek 2021-04-06 21-20.gif

@d-healey Yes, there is a bug with fonts being set to "default" not showing. This is something I reported a little while back. You need to specify the font for each text bit.

@d-healey It turned out I was including my scripts like this

include("./Fold/Script.js")

instead of

include("/Fold/Script.js")

Which makes sense to why it was working in HISE but not when compiled.

@dustbro I did that before creating the expansions... Maybe doing it afterwards does the trick for now... But there's something funky going on here, no?

@Christoph-Hart - OK thanks.

download.gif

@Christoph-Hart Those are the best!

@Christoph-Hart
This must be him

tired-baby-polar-bear-legs-sleep-animals-predators-bears.jpg

@Christoph-Hart @d-healey It was already 0-1 based I was just talking nonsense 🤪
That's it, pushed and working...