search

obiwanjacobi / vst.net

Virtual Studio Technology (VST) for .NET. Plugins and Host applications.
https://obiwanjacobi.github.io/vst.net/index.html
GNU Lesser General Public License v2.1
420 stars 52 forks source link

Poll: What changes for a new version? #21

Closed obiwanjacobi closed 3 years ago

obiwanjacobi commented 4 years ago

I have experimented with getting VST.NET over to dotnet core which looks very promising. So there may be a new version of VST.NET (netcore) on the way! And just like the dotnet team did in redesigning all the APIs for dotnet core, we can do the same - hopefully making a more intuitive, easier to understand API for this new version.

I am not talking about taking on big new features, more like small tweaks that can be easily and quickly done.

Are there any parts of the existing API you would like to see different?

I have a few of my own but I want to hear what you think and want.

obiwanjacobi commented 4 years ago

Split up Interop into a Plugin and Host part.

Currently the Jacobi.Vst.Interop assembly contains code for when you run a managed plugin in an unmanaged host, as well as code to allow managed hosts to load unmanaged plugins. That means that a plugin carries some extra unused code that is only used when building a Host.

Should we split this code up into two separate interop assemblies? Jacobi.Vst.Plugin.Interop Jacobi.Vst.Host.Interop

obiwanjacobi commented 3 years ago

Closing - lack of interest and approaching release.