Running Windows 10, the latest Studio One, the latest Synchron player with Prime and a few other VSL products.
I discovered this when attempting to load a sound variation from Babylon Waves articulation mappings, which I have used previously without issues. Essentially whenever I try to load a Studio One variation with a Synchron player track, I get a popup dialog that says:
"This preset was generated for "Unknown" and does not match the target instrument."
The Babylon Waves files still work fine in other products, and the popup dialog is a new thing I've never seen before. In theory even if for some reason the mapping has changed it shouldn't do that. If the mapping has changed, it typically works since a mapping is still a mapping, even if you don't get the results you expect.
I'm doing this outside of Flow and it happens even with non-Prime VSL instruments, so it appears related to Synchron.
If I can provide any other information please let me know.
Thanks
J.C.