Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
ASPiKreator 1.6.6
Avatar
Chaes
Member
Members
December 18, 2020 - 4:08 am
Member Since: February 21, 2020
Forum Posts: 50
sp_UserOfflineSmall Offline

Is anyone else having trouble with the custom template option? Mine is just creating a project folder with 1 CMake file

Avatar
W Pirkle
Admin
December 28, 2020 - 8:49 am
Member Since: January 28, 2017
Forum Posts: 555
sp_UserOfflineSmall Offline

Are you using MacOS or Windows ASPiKreator?

I will check. But, if using either one, the ASPiKreator executable needs to stay in it's location, relative to the PluginTemplate folder. 

Will 

Avatar
W Pirkle
Admin
December 28, 2020 - 9:12 am
Member Since: January 28, 2017
Forum Posts: 555
sp_UserOfflineSmall Offline

I just tested this and it is working properly on both Mac and Windows, being run from the folder within the ASPiK SDK.

Will 

Avatar
Chaes
Member
Members
January 6, 2021 - 11:45 pm
Member Since: February 21, 2020
Forum Posts: 50
sp_UserOfflineSmall Offline

Hi Will,

I am using MacOS primarily then switching to windows to run CMAKE and build out the Windows VST3.

I have been using it for a few days and this is what I've found.

1) Clicking the refresh template does not appear to actually replace it or restore it.

I created a project each time after a) modifying the project template, b) clicking refresh template, c) deleting the PluginTemplate folder completely and hitting restore (the folder was not restored, I had to re unzip the SDK) and lastly, d) deleting the PluginTemplate folder.

In each scenario the resulting project was build from the standard (as if secure) ASPiK base project. I have not moved anything. I have just put the ASPiK SDK on my desktop and run it from there.

2) VST Code appears to be Missing

I can probably fix this myself but somewhere in the new iteration the developer.vst3.name.BundleID is not getting put into the XCODE field like the others. Not a big deal but for the sake of consistency. This appears to be only with 1.6.6 projects.

3) ASPiKreator 1.6.7 (MacOS) appears to be damaged

 I cannot use the newest ASPiKreator (1.6.7) for MacOS at this time as it appears to be damaged and I am unable to run it. So all of the above hangs on that fact.

Chaes

Avatar
Chaes
Member
Members
January 24, 2021 - 5:10 am
Member Since: February 21, 2020
Forum Posts: 50
sp_UserOfflineSmall Offline

Anyone else experiencing this?

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
6 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 50

Skyler: 48

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

clau_ste: 39

jim: 34

JimmyM: 33

Gwen: 32

Member Stats:

Guest Posters: 1

Members: 680

Moderators: 1

Admins: 5

Forum Stats:

Groups: 13

Forums: 41

Topics: 744

Posts: 2846

Newest Members:

dan_1, phlub, josh, bmarx, Tom Helvey, Ludovic, Mihir Shah, Mina, robbie, Matteo Desantis

Moderators: W Pirkle: 555

Administrators: Tom: 74, JD Young: 80, Will Pirkle: 0, W Pirkle: 555, VariableCook: 3