KVR Audio

pera · Post by **pera** » Mon Sep 08, 2008 10:36 pm

oh yeah

nice news

thx mda!

NPProject · Post by **NPProject** » Wed Sep 10, 2008 12:48 pm

I'm well-pleased that these have been released as source - they've been a staple of my setup for yonks.

Has anyone had any success compiling these out-of-the-box in VC++ express 2008?

After importing the VC++.8 project I deleted the resource.rc from the project to get rid of the MFC dependency but the built DLLs are not showing up as VSTs in hosts - presumably because the DLL isn't exporting entrypoints as expected.

I noticed that the VST SDK again example uses a .def file to export "main" but I don't see a similar export in the mda plugs....

Cheers
NPP

plastique · Post by **plastique** » Thu Sep 11, 2008 5:11 pm

Did you try it with a custom def file ? You just need these entries there

Code: Select all

EXPORTS VSTPluginMain
main=VSTPluginMain

everything else is optional. I don't use Visual Studio at the moment to tell you the exact steps, but it should be as easy as adding the def file to some linker option.

NPProject · Post by **NPProject** » Fri Sep 12, 2008 10:41 am

Thanks, plastique, that has done the trick. It's weird that the linker def file is not referenced in the projects that ship in the source zip.

plastique · Post by **plastique** » Fri Sep 12, 2008 12:06 pm

NPProject, does the project file build all plugins at once ? I.e. is it a single project file for all plugins ? If that's the case and you could fix it with a custom def file, could you save it and send it to me please ?

I'm preparing a source code update for sourceforge and currently this only consists of the cpp/h files, but it would be practical to also fix the VS project file if it's broken. I'd just need the project file (or if they consist of more files than one) and you telling me where you put the def file, so that the VS project will find it by itself. Would that be possible ? Thanks!

email: plastiquefantastique [ a t ] gmx [ d o t ] de

NPProject · Post by **NPProject** » Fri Sep 12, 2008 12:22 pm

plastique, I'll send you a mail shortly.

plastique · Post by **plastique** » Wed Sep 24, 2008 4:21 pm

The source code is now up to date at the source forge repository, with new build targets as well (MinGW and Makefiles for Linux from myself, and VCE2008 project files thanks to NPProject).

I've been added as an admin to this project, so if there are updates to the source code and you want to commit it (the SVN is currently not updated yet), let me know (preferrably via sourceforge).

etapper · Post by **etapper** » Mon Sep 29, 2008 8:56 am

plastique wrote:The source code is now up to date at the source forge repository, with new build targets as well (MinGW and Makefiles for Linux from myself, and VCE2008 project files thanks to NPProject).

I've been added as an admin to this project, so if there are updates to the source code and you want to commit it (the SVN is currently not updated yet), let me know (preferrably via sourceforge).

Highly appreciated!! I'm learning alot from it already!!

etapper

Vivada · Post by **Vivada** » Wed Oct 15, 2008 10:53 pm

Much kudos to you, mda. I just recently blogged about the lack of open source VSTs in the wild, we need to convince more developers to see the light. Does anyone know if there has been much development on these plug-ins since they were set free?

plastique · Post by **plastique** » Fri Oct 17, 2008 6:37 pm

There hasn't been much going on after the update from the 23/24th of september, which mainly covered bug fixes relating to the preset system and 64-bit safety on non-Windows machines. The base code has been updated too (SVN is committed now as well). The MAC-only code (which has always been more of a separate entity) is still the same. Maybe someone who cares about AU versions could have a look and update from the cross-platform code.

Apart from that, a tiny update is already queued for the next time, which deals with some minor issues. If there's something to add feel free to contact me (I'm the second admin next to Paul Kellett for the sourceforge project).

soma · Post by **soma** » Fri Oct 17, 2008 6:51 pm

Anyone fancy turing this opporunity into class room like tutorial on making VSTs??

Only seems fitting since they were the start of the revolution.

Chris Walton · Post by **Chris Walton** » Sat Oct 18, 2008 12:43 am

soma wrote:Anyone fancy turing this opporunity into class room like tutorial on making VSTs??

Only seems fitting since they were the start of the revolution.

Not a good idea. I took the time to type out why, but I decided not to post it as it would certainly derail this thread, so I'll just leave it at that.

plastique · Post by **plastique** » Sat Oct 18, 2008 5:31 am

Well I think the idea is not bad by itself, but it has to be a separate project from MDA as neither I (and I can imagine neither Paul) is going to be able to support it.
If the MDA code is "nice" enough to show good coding is a different thing (what Chris probably was hinting at).

Something that I could imagine doing (but this could be very unlikely to happen in the next future though) is to build a C++ object (class) library from the different plugins, basically to make the code more usuable in a more generic way. It's something that also Paul proposed to do with the code. This would offer integration into other plugin standards or for example synthedit. But as said, very unlikely to happen anytime soon.

tetsuneko · Post by **tetsuneko** » Sat Oct 18, 2008 5:40 am

I'd like to see a mda-mashup compo on KVR some day!! With rules beign something like "devise a new vst/vsti by combining dsp elements from MDA plugins (source code can be downloaded from sourceforge)" Any chance of this happening?

plastique · Post by **plastique** » Sat Oct 18, 2008 2:37 pm

Who are you asking ?

I for one can't imagine anyone having something against such an event. In fact it would be rather interesting to see what could turn up as the results.

mda plug-ins now open source