Originally Posted By: Jim Fogle
The issue with "working seamlessly with all DAWs" is each DAW has it's own method for communicating with plugins. So a simple goal reveals a complex issue.

An even larger issue is PG Music has not clearly defined the plugin set of features. What capability does PG Music expect the plugin to deliver? What does agreeing with the Band-in-a-Box Lite nickname mean in terms of PG Music expectations and the plugin feature set?

Once the plugin feature set is defined, what is required to work seamlessly becomes much clearer.


In the world of data and voice communications they standardised a model for how the different protocols fit together. For example, how one Ethernet card speaks to another. They did not say how the card should be made but how the signal enters the card and how it must leave.

I thought that is what the VST implementation was about. If a plugin uses the term VST it should comply to a set of rules. DAWs should also comply if they are “VST Compliant”. Maybe a Standards organisation is required in a similar vein to the IEEE lot that look after Electronic Communications. That way one can be sure if the have a VST it will work in your DAW.

My thoughts
Tony

HP i7-4770 16GB 1TB SSD, Win 10 Home,
Focusrite 2i2 3rd Gen, Launchkey 61, Maton CW80, Telecaster, Ovation Elite TX, Yamaha Pacifica 612
BB 2022(912) RB 2022(2), CakeWalk, Reaper 6, Audacity, Melodyne 5 Editor, Izotope Music Production Suite 4.1