Re: Mutitimbral - A clarification, sort of
Re: Mutitimbral - A clarification, sort of
- Subject: Re: Mutitimbral - A clarification, sort of
- From: James Chandler Jr <email@hidden>
- Date: Wed, 16 Jul 2003 14:12:37 -0700
On Wednesday, July 16, 2003, at 08:35 AM, Frank Hoffmann wrote:
Where is the problem with instantiate 16 plugins? We are talking about
shared code and data here. The overhead is minimal.
What about the labor overhead of a user who must instantiate 16 plugins
before he can listen to a partner's emailed MIDI file?
Apologies for having an old-fashioned MIDI mindset...
Some sequencers automatically show all instantiated softsynths +
available external synths, in a MIDI Track DESTINATION pop-menu. If a
sequencer did not offer such routing, it might be difficult to get me
interested in buying the product.
For sake of example, say a sequencer has a bunch of MIDI tracks in the
Mixer window, and a single instance of Virtual Sound Canvas, SampleTank
or whatever. Easy to set up. Easier to navigate on-screen, than a
duplicate synth instance for each MIDI track.
Regarding host control of a multi-timbral synth, I'm probably too dumb
to understand this problem--
Say we have a five-band dynamics plugin. This dynamics plugin has 10
parameters per band, and some global parameters. Maybe the host has to
load/save a total of 70 parameters.
But the dynamics plugin control panel doesn't have to show all 70
parameters simultaneously-- Perhaps the plugin control panel would put
each band on a separate view of a tabbed pane, with an additional tab
for global settings.
This view-hiding in the plugin control panel doesn't affect the host at
all-- When appropriate, the host just gets/sets 70 parameters?
How is this substantially different from a 16 part programmable synth,
even if part 10 uses a drum structure rather than pitched-voice
structure? Perhaps each part has 50 parameters, oscillator, ADSR,
Filter, etc. In this case, perhaps the total synth "Patch" would
contain 800 parameters.
The softsynth's control panel might use the same strategy as the
multi-band dynamic plugin-- use a pop-menu or tabbed pane to allow the
user to view/tweak each synth part independently. How does this make
the host's job any more difficult? All the host has to do is get/set
those 800 parameters? Why does the host have to care about the quantity
or purpose of the parameters?
Repeated apologies if I'm completely missing the point (GRIN).
James Chandler Jr.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.