ASPiKreator 1.6.6 | Getting Started with ASPiK | Forum

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
Member
Members
December 18, 2020 - 4:08 am
Member Since: February 21, 2020
Forum Posts: 56
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
Admin
December 28, 2020 - 8:49 am
Member Since: January 29, 2017
Forum Posts: 693
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
Admin
December 28, 2020 - 9:12 am
Member Since: January 29, 2017
Forum Posts: 693
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
Member
Members
January 6, 2021 - 11:45 pm
Member Since: February 21, 2020
Forum Posts: 56
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
Member
Members
January 24, 2021 - 5:10 am
Member Since: February 21, 2020
Forum Posts: 56
sp_UserOfflineSmall Offline

Anyone else experiencing this?

Avatar
New Member
Members
February 20, 2021 - 3:09 pm
Member Since: February 20, 2021
Forum Posts: 1
sp_UserOfflineSmall Offline

Yes. "ASPiKreator.app" is damaged and can't be opened.
1.6.7 on MacOS 10.15.7

Avatar
Admin
March 11, 2021 - 12:50 pm
Member Since: January 29, 2017
Forum Posts: 693
sp_UserOfflineSmall Offline

I am still looking into this. There should be a new ASPiK update at some point, and I am spending all my spare time with the new Synth book projects. 

I will address this in the next release. 

Will

Avatar
Member
Members
March 16, 2021 - 8:52 am
Member Since: March 16, 2021
Forum Posts: 7
sp_UserOfflineSmall Offline

Chaes said
Anyone else experiencing this?  

I am experiencing the same issue that ASPiKreator app 1.6.7 is corrupt.  Tried re-downloading to no avail.  For the record running macOS Big Sur (11.2.2).

Avatar
Admin
March 16, 2021 - 10:54 am
Member Since: January 29, 2017
Forum Posts: 693
sp_UserOfflineSmall Offline

I have re-compiled the ASPiKreator to target MacOS 10.10 and higher; there was an anomaly between the target deployment and the project deployment. The re-targeting may fix your issue, but I do not own a BigSur Mac to test with. I replaced the old ZIP with this new one, just compiled with the target changed. 

http://aspikplugins.com/downlo.....or.Mac.zip

I am not sure if/when I will have a BigSur machine (or a M1 machine) so let me know if it still shows up as corrupt. Normally the "corruption" is actually a OS targeting issue (will only get worse with Apple Silicon machines...)

Will 

Avatar
Member
Members
March 17, 2021 - 8:20 am
Member Since: March 16, 2021
Forum Posts: 7
sp_UserOfflineSmall Offline

Will, appreciate the responsiveness!  The new zip now works fine under Big Sur (no more corruption message, though I did have to change security settings to run the downloaded app - as expected).  I'm running on Intel based iMac, so can't vouch for M1 based hardware.  Just starting Chapter 7 in your FX book and have Synth book v2 on pre-order.  Thanks again!

Avatar
Admin
June 14, 2021 - 1:43 pm
Member Since: January 29, 2017
Forum Posts: 693
sp_UserOfflineSmall Offline

Yeah, I am going to need to create a proper installer moving forward, with code signing, etc... I just did that for the new SynthLab synths that will be published soon (in a week or so).

Will 

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
2 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 56

Skyler: 48

StevieD: 46

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

Nickolai: 43

clau_ste: 39

jeanlecode: 37

Member Stats:

Guest Posters: 2

Members: 784

Moderators: 1

Admins: 6

Forum Stats:

Groups: 13

Forums: 42

Topics: 850

Posts: 3372

Moderators: W Pirkle: 693