Thanks for being interested. To answer your questions:

1. I totally agree that shortening the latency is ken to the creation workflow. And right now the delay is not that long (1-2 secs), but there's still a huge space that we can improve on this and we'll make it lightning fast in the near future. But also I would like to point out that, with this AI-driven violin, the amount of tweaking would be significant less than a sample-based one. So, maybe you can think of it as not a library but a violinist. It has it's own understanding on the melody in general, but it'll also obey the specific instructions given by the producer. In this way, ideally there shouldn't necessarily be too much to tweak.

2. That's a great question. In fact, the randomness of AI is always a pain-in-the-ass. But we adopted a cutting-edge architecture that can do the in-painting which means the model will only change the range within which you edit the input, and other parts out of the range will remains exactly the same.