First-hand testing tells me more than any other method, yes, and it's faster, yes — I'll be working on that. But user reports help me to prioritize testing and alert me to issues I can't reproduce or wouldn't encounter on my end. The app-not-installed issue (related to the virtual MIDI driver) is a good example. So please continue remarking on success/failure.This should be much quicker for testing than relying on user feedback, at least in the "does it load at all" phase.
(Over the years I've learned that a good beta involves collecting as much data as possible. If the app crashes on a Windows XP machine in Cambodia, the user just needs to press a button and I get a report. I'm hoping to advance the VST's automatic reporting systems to this level as well.)
So, this is pretty much why I've chosen to spend years and years on this software in spite of those who've urged me to beeline for a finished product. I don't want to make a product that leaves a user feeling unable to use it despite serious efforts to learn. Getting the tech to that level is long and labor-intensive process — research and development — which I don't even get to spend most of my time on. In this case, my judgment is that imitone failed to serve your needs.OK. There is nothing wrong with the standalone version (have not tried the VST yet), but I just can't seem to make it produce the Midi data that reflects the melody I have in my mind. I bought it mostly for entering synth bass lines with lots of pitch bending, but the plugin is not tight enough for that, and my voice not good enough it seems
As the problem is mostly my voice, I don't want a refund, which always implies that a product is not good. That's not the case.
Maybe someone else wants my license...
With any luck the next set of advancements (automatic scale & key selection, algorithm improvements, anti-jitter tracking, and a new transcription engine) will change that. Starting into those next month and expecting to spend quite some time there.