The thing with this new payer is really easy IMO ...
It clear looks like it has some potential, given the features provided that are not possible in Kontakt. Yet, the whole thing will work or fail, based on the OT player managing to deliver ...
... the same efficiency as Kontakt.
... background loading of the samples to shorten start up times.
... not lack any Kontakt feature that might be important to many.
The last part is complicated, unfortunately! For example, I tend to use Kontakt multi scripts to create some custom key switching solutions or repair some bugs in scripting. One example: If you send one Midi CC to a Capsule instrument (just one midi command, like CC 56 with a value of 127), this midi command is ignored by capsule. Probably, this is by design, as older fader boxes sometimes send values without touching them from time to time. That is why I suppose, they programmed Capsule to only process CCs, if at least two values got sent. It might just be a bug as well ... I am not sure!
However, this is a problem for me, as I want to send all values as a bulk message, as they are set on my Lemur controller app. Kontakt enables me to fit things like that, by finding out what the problem is. It is tedious at times and I hate it!
But I have to face the fact that almost no developer ever did everything to my liking in their scripting. Some features are locked, like certain CC parameters or sometimes key switches. If there is no multi script available, I need everything to be user definable and also CC-controllable. Otherwise, I cannot see how I could fit a different player to my workflow.