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 sp_TopicIcon
What is required to get the 64 bit dll? (Without having the error)
No permission to create posts
September 14, 2014
12:29 pm
Avatar
Robin
Member
Members
Forum Posts: 3
Member Since:
June 19, 2014
sp_UserOfflineSmall Offline

All,
In VS Express 2013 for Windows Desktop one can complie for a 64 bit dll simply choosing Debug and x64 instead of Debug and Win32 for compiling/debugging. The error that pops up by building the RackAFX dll is this: error LNK1561: entry point must be defined. Searching the web I see that somehow the int main() is required. Win32 works by the way, but x64 gives this error.
Note that I tried this on the most basic project for RackAFX, the Volume slider. Also, since I use the latest update from VS Express 2013 (Update 3) and the latest RackAFX (6.2.6) I wonder if this is something basic I didn't notice (some kind of setting) or that it is deeper RackAFX stuff?
Is there a solution?
Thanks for reading.
Robin

September 14, 2014
5:17 pm
Avatar
Robin
Member
Members
Forum Posts: 3
Member Since:
June 19, 2014
sp_UserOfflineSmall Offline

Got it. It seems that it is a cross platform compiling/debugging setting in configuration manager in VS2013.
Embarassed

September 15, 2014
6:06 pm
Avatar
W Pirkle
Admin
Forum Posts: 143
Member Since:
January 28, 2017
sp_UserOfflineSmall Offline

Hi Robin

Thanks for the reply - I was just looking at this. Could you let everyone know what configuration setting is required?
Thanks!

Will

September 16, 2014
10:40 pm
Avatar
Robin
Member
Members
Forum Posts: 3
Member Since:
June 19, 2014
sp_UserOfflineSmall Offline

So, what I did was this:
- Build the RackAFX project in 32 bit Debug mode (Active Solution platform mode) for a 32 bit platform project configuration deploy use.
- So, now a DLL has been built to be used by the RackAFX API.

But the goal is to make a VST for 64 bit DAW use.
- Next, I click “Make VST” in RackAFX and create a VST project.
- Then – according to Will's video example – I name it differently and go to the VST folder to find the .sln file (with the new name for the DLL that will be created soon).
- So, I open this .sln in a new instance of VS 2013 and build it with different settings in the Configuration Manager, i.e. choose Win32 for the Active Solution Platform and x64 for the build.
- In the Debug folder is a DLL file now that is 64 bit (made from a 32 bit program (usable in a 64 bit DAW).

Robin

February 17, 2015
1:53 am
Avatar
saltline
Member
Members
Forum Posts: 8
Member Since:
November 27, 2014
sp_UserOfflineSmall Offline

Hi Will,

I've followed the above steps but I still have one problem using VS2010. When compiling none of the files in the plugins custom controls folder (created by RackAFX) can be found resulting in vst failing to compile. I have tried adding all the files to the project again and it still can not find them.

For example
c1xx : fatal error C1083: Cannot open source file: 'source\XYPadWP.cpp': No such file or directory

Ted

February 17, 2015
6:31 pm
Avatar
W Pirkle
Admin
Forum Posts: 143
Member Since:
January 28, 2017
sp_UserOfflineSmall Offline

Hi Ted

2 things - first, Robin's statements above are for the (old) VST2 ports from previous versions. These are still available in the new version (v6.5 and higher). Also, I have streamlined the 64-bit project files so that it is simple to compile them.

When you are using Make VST, then you will get two projects in the "VST Files" subfolder of your project. In that folder is the VST2 version, and a subfolder named VST3.

For VST2:
You can compile directly into this directory as it is stand-alone and does not require the VST2 SDK on your computer. Open Visual Studio and open the .sln file. For VS2010 and later you will get an upgrade message - answer yes. By default it will compile as x86/Debug mode. To compile as 64-bit, simply choose x64 from the Configuration dropdown box. Then compile as 64-bit. To verify, I just did this with VS2010 in both 32 and 64-bit versions.

For VST3/2:
In the VST3 subfolder you will find the VST3 version (which also compiles as VST2). Open the VST3 project sub-folder and you will find the three subfolders:

mac - has the XCode files to compile for MacOS
resources - graphics files
source - all the VSTGUI derived objects I use

In the source folder you will find XYPadWP.cpp and XYPadWP.h

Try it now and you will see these files. You then need to move this entire Project folder to within your VST3 SDK folder in the proper hierarchy (the same depth as the sample code, 4-layers; I use my own folders so for me this is):

C:\VST3 SDK\public.sdk\My Projects\FX Projects\Windows

NOTE: naming the folder "Windows" is an outdated policy of mine; you could name it "VST3 Ported Projects" or something else since the MacOS version is actually contained in the mac subfolder. So my folder was:

C:\VST3 SDK\public.sdk\My Projects\FX Projects\Windows\VSTTest

and inside of VSTTest are the three subfolders mac, resources, source.

Now, you can compile as 32 or 64 bit by just choosing the appropriate configuration from the dropdown list on the toolbar. For verification again, I also just did this - no problems with VS2010 and no problems with missing files and nothing else to set in VS - just choose the configuration from the dropdown list and that is it.

Also, it is assumed that if you are going to use the VST3 option:

- you have the VST3 SDK installed on your computer
- you have compiled at least one VST3 sample project independently of RackAFX (so that you understand the folder hierarchy issue)

- Will

February 17, 2015
8:37 pm
Avatar
saltline
Member
Members
Forum Posts: 8
Member Since:
November 27, 2014
sp_UserOfflineSmall Offline

Thanks Will,

Yeah, certainly something I overlooked. I followed what you put here and it worked perfect. Thanks for the help.

Ted

February 27, 2016
11:28 pm
Avatar
staiff
Guest
Guests

Hello !

To export as a VST i did "Make Vst". I have a folder "VST" in my project now, and a subfolder "VST3" (no VST2 named by the plugin_name like in your video, just the VST3 folder)
As you wrote i just copied the 3 subfolders (Mac, resources, sources) and leave the other files (the proj & vcxproj, the snl, sdf, etc. ...) and paste it in my VST SDK folder like you explain :
C:\VST3 SDK\public.sdk\My Projects\FX Projects\"myplugin"

But how open it now in VS2015 to compile. in source folder there is no .SLN & .proj. I block here.

Thanks.

February 28, 2016
12:51 am
Avatar
W Pirkle
Admin
Forum Posts: 143
Member Since:
January 28, 2017
sp_UserOfflineSmall Offline

Steinberg obsoleted VST2 two years ago and I no longer support Make VST for creating VST2 plugins directly. The video you saw is out of date.

However, the VST3 SDK allows you to wrap the plugin so it appears as a VST2 plugin. Note the above post where it says

"In the VST3 subfolder you will find the VST3 version (which also compiles as VST2). Open the VST3 project sub-folder and you will find the three subfolders:"

So, Make VST is really "Make VST3"

You need the VST3 SDK installed on your computer and you need to follow the directions for placing your ported project in the proper folder. When you compile your VST3 plugin, it will be named .vst3 -- to make it into a VST2 plugin, you just change the extension to .dll

The same plugin file works as both VST2 and VST3, you just need to change the extension.

Also note in the above post:

"Also, it is assumed that if you are going to use the VST3 option:
- you have the VST3 SDK installed on your computer
- you have compiled at least one VST3 sample project independently of RackAFX (so that you understand the folder hierarchy issue)"

- Will

February 28, 2016
1:14 am
Avatar
staiff
Guest
Guests

Hello Will
i understood that VST2 files was obsolete and the RackAfx wrapped .dll work like a charm in 32 bits VST (.Dll and renamed .VST3). I feel this better in fact. For that RackAFx is so powerfull. Simple and/but powerfull.

But at this time "we must" also create 64 bits plugins (in my opinion: no). The best way is to use "make VST". i understood that also. So i used it. After that in my SDK folder (i installed VST3 SDk like you explained) i put the 3 folders in it (the 3 folders made by "make vst" without the files outside the 3 folders). i understood that. it's just after that i don't understand. VS(2015) only open .sln & .proj files.

to compile it (and make 64 bits) what kind of files do i open in VS2015? cause in the 3 folders (in SDk) there is no .proj or .snl. do i open what i pasted in the VST3 sdk folders ?

That's just the problem for me. Understand what files open in VS and how. After that it will be simplier 😀

February 28, 2016
3:45 am
Avatar
Tom
Admin
Forum Posts: 65
Member Since:
April 3, 2014
sp_UserOfflineSmall Offline

Hi,
maybe you should go back a step and familiarize yourself a bit more with C++ and Visual Studio:
https://msdn.microsoft.com/de-de/library/bb384847.aspx

Tom

February 28, 2016
5:36 pm
Avatar
staiff
Guest
Guests

Folder hierarchy issue fixed. So i paste all the "make VST" created folder in it. Opened VS2015, loaded solution (in the SDK3 hierarchy), compiled it.

when opening it i had a base VC_9 warning (security if i remember well). But VS compiled it. At this time all is Ok. plugin.vst3 created. i copied and paste it in my 64bits plugins folder (renamed it .dll for the vst2_64 bits dll). I opened studio One: my plugin is visible. i opened it, and.... GUI issue !

Hebergeur dImage Enlarger

Bg is here, but all buttons disapeared. the RackAfx wraped .dll (32 bits) is good:

Hebergeur dImage Enlarger

I will find where is issue and fix it.

EDIT: I noticed that my custom GUI buttons are not in the vst ported folder (Eg: Resources)(only my BG.png nothing else). So i made a mistake somewhere in Rack Afx that cause wraped .dll read the custom GUI, but ported vst one doesn't.

June 17, 2016
2:55 am
Avatar
hoegge
Member
Members
Forum Posts: 11
Member Since:
June 12, 2016
sp_UserOfflineSmall Offline

Will said

...

Try it now and you will see these files. You then need to move this entire Project folder to within your VST3 SDK folder in the proper hierarchy (the same depth as the sample code, 4-layers; I use my own folders so for me this is):

C:\VST3 SDK\public.sdk\My Projects\FX Projects\Windows

NOTE: naming the folder "Windows" is an outdated policy of mine; you could name it "VST3 Ported Projects" or something else since the MacOS version is actually contained in the mac subfolder. So my folder was:

C:\VST3 SDK\public.sdk\My Projects\FX Projects\Windows\VSTTest

and inside of VSTTest are the three subfolders mac, resources, source.

- Will

Isn't that actually a layer deeper than the VST samples. They also only have 6 times ../ in their config file references where as your config files have 7 times ../ ?

VST3 SDK/public.sdk/MyProjects/RackAFX/Mac/SimpleHPFvst/Mac

VST3 SDK/public.sdk/samples/vst/adelay/mac

June 17, 2016
6:10 pm
Avatar
W Pirkle
Admin
Forum Posts: 143
Member Since:
January 28, 2017
sp_UserOfflineSmall Offline

For Windows projects, its the location of the .vcxproj file that is important regarding the hierarchy.

For Mac, I changed the folder hierarchy depending on the VST3 SDK that you have. It is more "proper" now for the 3.6.5 SDK.

- Will

Forum Timezone: America/New_York

Most Users Ever Online: 36

Currently Online:
6 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Skyler: 47

Peter: 41

Derek: 41

clau_ste: 39

Frodson: 38

Gwen: 32

EZB: 24

lppier: 23

Msaldaña: 18

Jorge: 17

Member Stats:

Guest Posters: 1

Members: 477

Moderators: 1

Admins: 4

Forum Stats:

Groups: 11

Forums: 30

Topics: 483

Posts: 1877

Newest Members:

Jaggxn, sam, annaharris, Marie Weaver, kev, Steven, Mr Anderson, mguy, omelc

Moderators: W Pirkle: 143

Administrators: Tom: 65, JD Young: 80, Will Pirkle: 0, W Pirkle: 143