With 8 tracks and the 2 MB soundfont, my AUGraph is taking about a minute to initialize, and about 10 minutes for the 31 MB soundfont. This would be doubled if 16 tracks were implemented.

If your assumption about the single preset being loaded for the AVAudioUnitSampler is correct, I may experiment with moving my project from the AUGraph and AudioUnit MIDISynth to an AVEngine and AVAudioSampler configuration, especially if MIDI functionality past note on/off messages is unsupported.

Would it be safe to assume that the AVEngine is just faster than the soon-to-be-deprecated AUGraph?

Thanks,

Tim

Date: Wed, 21 Feb 2018 19:20:19 +0100
From: Sven Thoennissen<[email protected]>
To: CoreAudio API<[email protected]>
Subject: Re: Channel Specific MIDI Reverb with an AUGraph
Message-ID:<[email protected]>
Content-Type: text/plain; charset=utf-8

Hello,

I can confirm your findings; could not find a way to accomplish reverb with 
MIDISynth. In my app I use AVAudioUnitSampler for each MIDI channel. This 
solution works fine for me, especially since my app needs to connect 3rd party 
AU extension effects. Even if MIDISynth supported reverb it would probably only 
be Apple's reverb AU internally (not that it’s bad; my app just needs to 
support AU extensions).

But to my positive surprise I found that loading SoundFont presets is rather 
fast on the iPad Air 2, a small fraction of a second if I would have to guess.
I only have simple SoundFont layers (1 instrument per preset), no complex stuff 
like multiple instrument layers, like some GM SoundFonts out there.
I also would assume that AUSampler only loads the sample data of the preset you 
specify, instead of the entire SoundFont.

How long is “unacceptably long” for you?

Sven

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to