ZombiWoof,ZombyWoof wrote:I think their web page is clear enough. They deliver a Wusikengine v1/v2 VSTi and the ET samples. They say that their soundsets are compatible with WusikStation, ManyStation, et al.
There is no mention of presets that I see, and those presets are what seem to be causing the problem now, probably because they were not created using the ET VSTi. This is strictly a blind technical guess. If so, the problem will be easily solved with correctly made presets.
If I try to load certain WS4 presets into WS2 or WS3, I see similar issues.
this is exactly where the issue is : tell me if I'm wrong, but they do NOT say anywhere on ET's page that only the "soundsets" are WS compatible and that their player is a requirement for trouble-free use. The page is vague, flies very fast above this topic, and in two well-wrapped sentences, the naive guy (me) is compelled to read that it's okay for him.
And don't get me wrong, this is far from being my first purchase, so even though I'm not a PC expert, I usually know at least how to read the "requirements".... So if tomorrow I see an annoucement for a terrific library, which is advertised as "wavs or aiff samples with some compatibility for k2", I will NOT buy it, because I know it will take forever for me to convert and tweak. If I see the same terrific library clearly announced as developed for K2 (or even K1 for that matter), I may be interested. That's the kind of minimal but doubtless information which is required -but not provided- here.
The WS VSTi engine offer is very much alike the Kompakt engine offer which comes with so many today's libraries : you may very well have a kompakt player bundled witht the lib, it does not prevent you in any way from loading all those nkis into your K2 copy, without the slightest problem.
Kontakt will read them like a breeze, and only the newest features may be not available to you if you do so (I can say this easily, I own and use a lot of them) And for some of those libraries, when K2 is required, it is VERY obviously stated on the company's page.
In the same way, it should have been made very obvious for the dumb guy (me if you like) that only the company's VSTi was able to use the lib without any effort from the user. PLUS, we are here talking about a library which comes in a SINGLE format : WS... Other companies undertake the huge task to deliver their libs into Kontakt, Giga, EXS, sometimes Halion, and Emu.... with all the intricacies that those sophisticated formats imply. Is it too much of an assumption to suppose that for just one format, which is very basic (no midi rules, no scripting, no keyswitching, no roundrobin/alternates....) at least the 100% compatibility of ****presets***** across the various versions is supported by the company (and preferably BEFORE release ?
I spent thousands on samples and softs in some 10 years, and this is really the first time ever that I face such a situation, where I cannot use the library for a compatibilty problem, and where almost peanuts in -so far unusable- presets (60 for more than 2 gigs) is provided.
Would it be possible ??
