Too bad I missed your plan to add support for callsigns, and you didn't reach out to me.
EditVoicepack have had an API for quite a while. Would need a bit of work but nothing serious (some changes to .NET Framework currently restricts it from working with the free EditVoicepack - but that can be solved, if nothing else with a new release of the free EditVoicepack).
It would have allowed you to ship callsigns (and aircraft models etc of course) with your own software in a way that are compatible with EditVoicepack and other addons.
i.e. users without EditVoicepack would get your callsigns. Users with EditVoicepack would get the callsigns, and maintain the functionality of EditVoicepack to accelerate and add variations.
Should have been a win win win:
You would not have to distribute wave files and deal with installing.
I would not have to deal with the support questions from people who accidentally install your files.
And the users would get something that worked no matter if they use EditVoicepack or other addons - instead of having to choose.
