Re: kAudioUnitType_MusicEffect and Soundtrack Pro 3.0
Re: kAudioUnitType_MusicEffect and Soundtrack Pro 3.0
- Subject: Re: kAudioUnitType_MusicEffect and Soundtrack Pro 3.0
- From: William Stewart <email@hidden>
- Date: Wed, 24 Feb 2010 18:56:24 -0800
Sounds like a bug to me - I'll forward this on to that team, but writing a bug report would be very helpful
Thanks
On Feb 24, 2010, at 3:14 PM, Blue Cat Audio Dev wrote:
> Hi,
>
> our plugins are all declared with kAudioUnitType_MusicEffect type because they support MIDI input to control their parameters. They used to be recognized by Soundtrack Pro 2.2, but with the upgrade to 3.0 they are not visible anymore. It appears that changing them to kAudioUnitType_Effect solves the issue.
>
> Does anybody know the reason for this new behavior? Is there maybe a way to make an AU plugin available as both kAudioUnitType_MusicEffect and kAudioUnitType_Effect so that it is supported by this application without removing the MIDI input capability?
>
> Regards,
>
> G.
> Blue Cat Audio
> www.bluecataudio.com
>
>
>
> _______________________________________________
> 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
_______________________________________________
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