> - resources: having to use one massive synth for each instrument would
> mean that this massive instrument would need to be loaded in memory
> several times. Some of our synths already take a lot of CPU power to run
> (organic, vibed) - imagine mashing all these together, it'd be horrible.
> Memory usage too.
I am not sure if this is true. Actually, I have tracks with 30 ZASF entities, 
and lmms takes only 6 % CPU power (no matter if played, or not). Also, I 
guess, you can alway select in a synth which parts of it should be used, and 
which not. A good example might be ZASF (it has 3 basical synths, you can 
select those that you need).

> - code complexity: this would be a nightmare to maintain
Probably it would be better, and not worse: We could handle all subparts 
modular. So with N subparts and 1 synth, we get N modules. With p synths of 
each N subparts, we get pN modules.

> - compatibility: implementing new features in a backwards compatible way
> would become a nightmare
Why?

> - modularity: it's good to use a modular design because it allows the
> user to mix and match components to create the kind of functionality
> they need on a case-by-base basis. A big monolithic beast is much less
> flexible.
See my point about code complexibility. If we still want different synths, 
they can easily share their modules, so we get more modularity, not less.

> Vibed actually has a wavegraph, and allows loading samples as waveforms.
> You can use any waveform you want in Vibed.
Yes, but this is not useful. In ZASF, I can change a waveforms parameter, then 
hear, then change a bit, hear, etc. If I want to load waveforms, I'll need to 
first generate them (ZASF would be the best choice, I guess), then save, and 
then load them. This is a lot of work to find a suiting waveform.

It gets worse if I want to modulate the wave form while playing. This is 
impossible, since the WAV file is static.

> >  * ZASF has a great waveform creator (> 10 waveforms, many with
> >  parameters). But I can not modify the waveforms like in a wavetable
> >  synth. (like in BitInvader or, as I assume, Vesa's new synth).
> ZASF uses additive/substractive synthesis. It's very different from
> wavetable synthesis and is good if you want to create authentic sounding
> analog-like sounds. Wavetable synths are cool, but you don't necessarily
> want them for all your sounds. They tend to cause aliasing, which makes
> them unsuitable for creating analog-like sounds.
With wavetable I just meant that the basic oscillator (which is the first 
thing in an ad synth) switches between different waves. So this could be part 
of an adsynth. These things are, AFAIK not different, they are independent.

> >  * One synth with 3 features is way more useful than 3 with only 1
> >  feature. We have lots of synths that have sub-functionality of "Massive
> >  NI", but none has the full functionality. I think having many features
> >  is important to create real professional sounds.
> We can use our plugins in a modular way. Chaining together instruments,
> controllers and effects, you can get much more complex sounds than any
> single VST can achieve.
There are many things that probably can not go into FX. Some use properties of 
single keys pressed, like frequencies. An effect does not know when a key was 
pressed, neither it knows the base frequency of such.

I think you can not put WT synthesis, pulse/frequency modulation, portamento 
etc. into an effect.

> > So I'd ask to start working at one synth that includes the features that
> > all other synths have. What's your opinion?
> If you want to create a synth that has tons of features, by all means -
> go nuts! Create the most awesome synth there is. That'd be great! But
> that doesn't mean we should remove our existing instruments. Sometimes
> you only need a small, simple instrument.
The "small" synths are good for learning, and removing them violates backward 
compatibility. I just think we should start re-using modules until we get 
close to having only one synth.

Also, it does not contradict to still have many small synths: If you have a 
synth with N modules, you can still write N synths that each use 1 of these 
modules. So people with slow PCs can still use the "small" effects, while ppl 
with better PCs can use the "elephants".



------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to