There are ways to protect products which are based on SFZ (just look at our own products and Garritan's), but then you are locked to one engine vendor indeed.hollowsun wrote: I am just saying that if you plan to sell in SFZ format, be prepared to be be ripped off, maybe big time. S'all.
But if that's ok with you, well... fair enough
But SFZ is just as much a future proof thing for casual users as it is for sample devs in my opinion. If your assets are originally in SFZ/wav (say before encryption - and you keep the originals), then you will always be able to modify, convert your instruments 50 years from now, as the specification is public.
To answer the "Where's the editor" question (and believe me I get that a lot), I can only answer that the sample developers I've been dealing with for the past 10 years while at first thrown off by the lack of interface, later realized that most of the tedious things can be scripted, find and replaced and batched to the point that efficiency is multiplied, not the other way around. I personally I can't imagine the how the Garritan Steinway or the new piano we are working on with its many thousands of regions (each having different EG and rt_decay coefficients) could have been made with a graphical editor alone.
Sample making is a fun sideline for me. I do my best and I make product I want for myself before anything else. If other people are interested they can pay a small amount of money and get a nice library.
..and thank you for the faith in us!
I'm not sure how long its small text interface will last, and how long it'll have a fixed GUI width.
