I'm having difficulty getting the GUI designer to launch inside Waveform 10. My test plugin is functional - all generic sliders working as expected; but the GUI editor that pops up inside the plugin GUI seems exclusive to my DAW (grid pattern and list of buttons/knobs to drag and drop). The option "OpenUIDescriptionEditor" does not appear for me. I only have an outdated version of Logic Pro 8, which will not run on High Sierra, and would rather not purchase yet another DAW that I don't typically use. Has anyone encountered a similar speed bump with this or another DAW?
I just attempted to access the VSTI4 GUI editor in Reaper, and got a similar result. Sorry if this has been covered elsewhere; but the "^ + right click" command eludes me so far.
Could you please provide the following information:
RackAFX Version? (if using it to import as ASPiK, ignore if not using)
OS: Mac or Windows? (it looks like MacOS because of High Sierra)
AU or VST3 or AAX?
I will do some checking; there is as compiler flag that must be set and they did just update VSTGUI4.9Â
ASPiK version 1.6.3 (not using RackAFX)
vstgui4 (as included in ASPiK version 1.6.3)
Mac OS (High Sierra)
Universal Plugin, but building GUI using AU format
X-Code version 9.2
It seems that the DAWs are not aware that they should point to the vst4gui, and instead point to their respective default editors. Perhaps I missed something during setup?
Good news - I have found and isolated the issue, which turns out to be a single line of CMake script. I am running more tests and will have a new update, hopefully before Friday. Sorry for the delay (I am a one-person team with a day-job) but the good news is that it was very minor and does not involve any changes in the ASPiK core code.Â
Stay tuned -Â
OK the v1.6.4 update has been released. The simplest thing is to just start a new project. If you've done work with adding controls, etc... then you can copy your plugincore.h and plugincore.cpp files to the new project and that should restore things (unless you added other files on your own).
There were two issues with AU and the Cocoa GUI - one was a simple CMake script line of code and the other involved the naming of the AU bundle when building for Universal projects. In this case, you will see that the letters "_AU" have been appended to the target name to differentiate the three targets (plus the Cocoa GUI target) from one another. That addition of "_AU" was a separate, but also problematic issue, and that has also been corrected.Â
I also corrected a memory-creep issue with the custom view demo projects. There was a very minor memory leak (32 bytes) in the vst3plugin.cpp file which was fixed with a simple delete call. New projects will have this updated file, and you can copy it to your old versions if you want to.Â
Thanks for reporting this - it had different behavior in different hosts. But, the GUI Designer is now available for you as a result.Â
ONE THING: go to your ~/Library/Audio/Plug-Ins/Components folder and find and delete the AU plugins from v1.6.3 (the ones you've had problems with). You may note that some are actually zero-bytes in length. In any event, just get rid of those manually before rebuilding new AUs.Â
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Moderators: W Pirkle: 690