View Issue Details
|ID||Category||Date Submitted||Last Update|
|0003278||features||2010-06-23 13:30||2011-09-29 00:45|
|Fixed in Version|
|Summary||0003278: Native VST plugin support|
|Tags||No tags attached.|
If there's one feature from all the proposed 3.x features that I think you should seriously consider bringing forward for inclusion in 3.0 its this.
We all know just how temperamental the current wine-based VST support is and hence this leaves you with the dilemma of not really mentioning the existence of kinda-sorta support for a much in demand feature or advertising it and falsely getting peoples hope up- well that is unless they're v. lucky and their fave plugins all work perfectly. Even then it could all change with their next wine update of course.
I was inspired to bump this feature suggestion today after reading this thread on the Reaper forums:
I'll spare you reading having to read it as I can summarise 90% of the comments very easily
"We want VST support under Linux/Ardour!"
I wouldn't expect all the big commercial plugin vendors to come rushing to port their wares to A3 VST but I would expect many of the smaller companies may and I'd think that there'd be much interest from the indie/shareware/freeware and of course FOSS VST plugin devs as it would make perfect sense for them as its probably the platform they've been waiting for.
Maybe choosing not to include native VST support in 3.0 is a tactical move aimed at fostering interest in LV2 but IMO thats the wrong way to go as if LV2 does (or will) offer advantages over native VST plugins then these advantages should effectively promote themselves and will gain more exposure through the increased pulling power A3 stands to gain through making things attractive to existing plugin devs by making their existing code as easy as possible to port. The faster we have a nice selection of plugins, the quicker the userbase will expand.
Considering the amount of time A3 has been in development now, like everyone else on here I want it to make the biggest and best impact possible on release and as you can tell by the length and tone of this note (surely my longest yet) I firmly believe adding this onto 3.0 will add considerable clout.
So, has anyone seriously looked into how hard adding this feature in would be and what potential pitfalls there are?
||Now in SVN for Ardour3.|
now in testing phase
||Going to mark this as closed; please open new bugs for any problems with native VST support.|
Just wanna add something that might be of interest for all of you.
The LMMS developers (who originally made the vestige header), have in their git repo an updated version of the header, which fixed the 64bit issues (note LMMS being released as both 32bit and 64bit Windows binary).
Link to the file:
Since ardour is already using this header, I think it makes sense to update it.
There were some previous git comments that changed the vestige header, but this specific commit clears up a few things:
|2010-06-23 13:30||cth103||New Issue|
|2010-06-23 13:30||cth103||cost||=> 0.00|
|2010-06-23 13:30||cth103||Status||new => acknowledged|
|2011-01-12 22:47||danboid||Note Added: 0009926|
|2011-01-12 22:50||danboid||Note Edited: 0009926|
|2011-09-20 20:55||paul||Note Added: 0011546|
|2011-09-20 22:16||paul||Note Added: 0011547|
|2011-09-20 22:16||paul||Status||acknowledged => feedback|
|2011-09-20 22:49||cth103||Note Added: 0011548|
|2011-09-20 22:49||cth103||Status||feedback => resolved|
|2011-09-20 22:49||cth103||Resolution||open => fixed|
|2011-09-20 22:49||cth103||Assigned To||=> cth103|
|2011-09-29 00:42||falkTX||Note Added: 0011617|
|2011-09-29 00:45||falkTX||Note Added: 0011618|