I don’t think the move to proprietary sample players is being drive by NI pricing. I think it’s due to copy protection, development of Kontakt not moving in direction and speed that the companies want, not wanting to be reliant on a competitor’s product, and not wanting to share sales data with a competitor.
Agreed on all counts. I think cost had little to do with developers creating their own players. Mind you, back in the old days, costs were much, much higher, and I think that was a factor with East West jumping ship. But at today's pricing, I doubt that was a major factor for Spitfire's or OT's decisions. (I assume most fair sized developers order the 1,500 quantity, which gets them the lowest license cost, which IMO is pretty reasonable.)
Aside from reasons already given, I'll add a few more reasons for avoiding KPlayer:
1. NKS requirements. I freaking hate the NKS requirements. They add days of extra work for each product, almost entirely for the purposes of selling NKS hardware, rather than any benefit to my products.
2. Delay and hassle of encoding. You can't simply finish a library, then put it up for sale. It's weeks (and in some cases, months) of extra time added for encoding and "NKS Quality Control" before you can release. I hate not being in control.
3. People who need KPlayer are much less savvy than full Kontakt people, and are going to be much more expensive in terms of tech support. I mean
really low level in many cases. The expanded customer potential by making a library KPlayer comes at a cost beyond just the cost of the serial.
4. Speaking of expanding your potential customer base, it's not as big a jump as you might think. Especially for orchestral, KPlayer probably doesn't increase the customer base by more than 10%. (Composers with enough money to buy orchestral libraries usually also have enough money to buy Kontakt.) For pop instruments, those numbers go up, but still not by
that much, because it's still a situation where if someone can't afford Kontakt, they're probably a tough sell for libraries in general.
When we first released Realivox Blue, we offered a full Kontakt version, and for $10 more, you could get the KPlayer version. ($10 was less than what the license actually cost me, by the way.) In the first year, 90% chose the full Kontakt version. Of those who bought the KPlayer version, I'd guess half didn't have to, but bought the KPlayer version simply for the Library Tab benefits. (In following years, the KPlayer percentage went up a bit, but still not
that much. Maybe 20% or 25% when I was advertising it on Facebook, where the audience is particularly less "pro.")
To be clear, we (Realitone) are moving all our libraries to KPlayer, as well as hosting on Native Access. So although these reasons piss me off, I still think the overall benefits of KPlayer (for us, at least) are worth it.