exported VST3 on windows error
-
now I have problems on Mac to when I try to export it, it goes too Compiling PresetData.cpp and then nothing happens anymore I've waited like 30 mins now and its still at Compiling PresetData.cpp
-
T treynterrio marked this topic as a question on
-
Left my Mac on all night and it's still compiling the PresetData.cpp file. I checked my RAM and it shows that it is trying to access over 60gb of only 32gb
-
@treynterrio You need to reduce the number of threads you're using to compile
-
@d-healey how can I do this?
-
-
@d-healey changed it to one but it still stops at PresetData.cpp
-
@treynterrio Have you tried cleaning the build folder?
-
@d-healey yes I've cleaned everything looked for files that where in my Images folder and deleted all presets nothing helps
-
@treynterrio said in exported VST3 on windows error:
yes I've cleaned everything
Did you select the option in HISE to clean the build directory?
What did you change between your working build and your non-working one?
-
@d-healey yes I tried this too. Everything I've done is I've added a couple Panels and Labels but the older project where it worked to export doesn't work now as well. I was able to export it as VST but I can't see it in Logic or Ableton but its in the Components folder and in the VST tried the User and Library folder
-
@treynterrio said in exported VST3 on windows error:
VST but I can't see it in Logic
Does Logic support VSTs I thought it would only use AU?
-
@d-healey I don't know but like I said I can't see it in Ableton which is my main DAW as well
-
@d-healey now I was able to export it but now when I try to open it in Ableton or Logic as AU the DAW crashs straight. pluginval crashes straight as well when he tries to scan it
-
@treynterrio Try auval
-
@d-healey auvaltool was also terminated directly. Logic doesn't show it to me at all. validation failed
-
@treynterrio Time to start taking your plugin apart bit by bit until it works
-
Another thing you can try is running your DAW (I recommend you use Reaper for testing) from within xcode or Visual Studio and see if you get any useful info there.
