Re: AU from scratch...?
Re: AU from scratch...?
- Subject: Re: AU from scratch...?
- From: Admiral Quality <email@hidden>
- Date: Wed, 13 Oct 2010 00:42:36 -0400
On Wed, Oct 13, 2010 at 12:08 AM, Brian Willoughby <email@hidden> wrote:
> The quickie VST-to-AU converters out there will not enable any of the new
> features in AU that are still missing from VST. Your users will
> particularly miss out if the parameters do not have realistic values,
> because the simple 0.0-1.0 range of VST is counter-intuitive.
If you're trying to port a single product, then by definition you're
limited to the subset of shared features.
I can't imagine what parameter ranges of 0.0 to 1.0 are doing to give
my customers a lesser experience. They're looking at my own interface
99.9% of the time, and that shows the values in their intuitive forms.
I haven't had a single complaint from someone saying, "Hey, this is
just a VST in an AU wrapper!"
The issue that *does* exist is the program paradigm. In AU there's a
bunch of ROM presets, then you make your own mods of those in new
program slots managed by the host. In VST, your preset programs can be
overwritten in place.
I actually prefer the VST system, as that lets me have 128 patches, no
more, no less, so MIDI program change commands can work as expected.
But, while a little weird, mashing the VST system into the AU system
doesn't actually prevent the user from accomplishing anything (except
sometimes your patch name changes don't get passed to the host,
because it thinks they're ROM when they're not. Still, save the
project and everything will be recalled correctly, and that's really
all that matters.)
- AQ
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden