Notifications
Clear all
Topic starter
August 1, 2023 7:58 pm
Hi All,
I'm looking for guidance/opinion on creation of a single-swim-lane basic, dry instrument.
First thing: is it OK to distribute multi-samples of a commercial VST from a patch you created yourself, as an instrument for community use in unify?
Second thought: what is a "reasonable size" for an multi-sampled instrument with say 3 notes per octave and 4 velocity switches? (Is 5 meg too much?) Third: To me it seems mono samples would be reasonable for unify , given the layering and effect chains. Finally, if the samples were both mono *and* carefully prepared eight bit, the instrument footprint would be ultra-small; but is going 8 bit overkill? Just thinking - 4 stacked layers of 8 bit would effectively be 32 bit output.
August 1, 2023 9:19 pm
First thing: is it OK to distribute multi-samples of a commercial VST from a patch you created yourself, as an instrument for community use in unify?
Provided the commercial VST does not itself use samples, it's fine. If it uses samples, then your samples will technically be (processed) copies of theirs, which violates their copyright.
Second thought: what is a "reasonable size" for an multi-sampled instrument with say 3 notes per octave and 4 velocity switches? (Is 5 meg too much?) Third: To me it seems mono samples would be reasonable for unify , given the layering and effect chains. Finally, if the samples were both mono *and* carefully prepared eight bit, the instrument footprint would be ultra-small; but is going 8 bit overkill? Just thinking - 4 stacked layers of 8 bit would effectively be 32 bit output.
No need to optimize so obsessively--it's not 1990 anymore. We routinely create sample-sets up to a gigabyte in size.
5 MB is a joke for today's systems. 3 notes per octave and 4 velocity levels of anything will be quite small.
