I agree with you 100%. It is especially hard for someone like me who is a novice programmer in general. On the other hand, I asked a very experienced programmer for help one time and he looked at the VST code like it was from outer space. It's a field of it's own for sure.aciddose wrote: ↑Fri Mar 29, 2019 7:25 pm I'd take the more pessimistic view and say it's no surprise when a host or plug-in crashes or doesn't work as expected.
Frustratingly, there is often no sure way to say whether the host or plug-ins worked correctly or failed to meet a non-existent specification. One can say that the system we've employed to ensure things work has been trial and error in a sort of biological/evolutionary sense.
So from that perspective it might start to become clear why "still struggling after ten years" has been a sort of inevitability from the beginning. Only... replace "ten" with "infinity".
What makes troubleshooting difficult is that I often can't tell if it's MY PLUGIN or the HOST that has the error. I recently wrote a plugin that worked perfectly in Steinberg's VST3 Test Host and numerous DAWs but then DID NOT work right in Cubase! Is it THEIR fault or MY fault? (In this case it turned out to be MY fault - a missing function that other DAWs don't use).
Build it and test it in as many DAWs as possible. Surely it will not work in ALL. But how good is "good enough"? 4 out of 5 DAWs, 9 out of 10 DAWs, etc.? The amount of hours put in to get that "one more DAW" to work can become huge.
Just make sure to have a good refund policy that encourages "try the demo before you buy it" I guess.