AUParameterSet 2 (1/8): err -10867

In Xcode 9 and iOS 11, I am getting this weird error now when connecting nodes in my AVAudio Engine.


Specifically when connecting an AVAudioPlayerNode to a an AVAudioMixerNode


engine.connect(sampler, to: masterMix, fromBus: 0, toBus: masterMix.nextAvailableInputBus, format: processingFormat)

I'm connecting about 60 of them in a for loop and the warning is only showing up from the 8th iteration on... At first I thought it might be because the AVAudioMixerNode only accepts up to 8 inputs but the documentation says it can have any amount.

957: AUParameterSet 2 (1/8): err -10867

957: AUParameterSet 2 (1/9): err -10867

957: AUParameterSet 2 (1/10): err -10867

Up vote post of kowongh Down vote post of kowongh
1.9k views
Posted by
kowongh
Reply
Add a Comment

Replies

Having exactly the same problem here with the same setup (iOS 11 and Xcode 9).


The app works fine in iOS 10 but crashes in iOS 11, so I suspect it's something with iOS 11. I'll be filing a bug report.


Setting up nodes [0]

Setting up nodes [1]

Setting up nodes [2]

Setting up nodes [3]

Setting up nodes [4]

Setting up nodes [5]

Setting up nodes [6]

Setting up nodes [7]

Setting up nodes [8]

2017-11-05 14:49:10.636984-0800 woodblock[389:50418] 958: AUParameterSet 2 (1/8): err -10867

Setting up nodes [9]

2017-11-05 14:49:10.637533-0800 woodblock[389:50418] 958: AUParameterSet 2 (1/9): err -10867

Setting up nodes [10]

2017-11-05 14:49:10.638099-0800 woodblock[389:50418] 958: AUParameterSet 2 (1/10): err -10867

etc.

Posted by
drtofu
Up vote reply of drtofu Down vote reply of drtofu
Add a Comment

I'm using audiokit, which has AVAudio as a foundation, and having the same issue with these error codes. Interestingly enough, all my loops are available when app is running (most I'm using is 29)...


Did you file a report, or discover anything further?


Thanks

Posted by
Proudly
Up vote reply of Proudly Down vote reply of Proudly
Add a Comment

I encountered this as well. It seems to be specific to iOS 11 (I don't get the messages on a device running 10.3.3), and as someone else noted it doesn't actually seem to affect anything. I filed a bug report.

Posted by
Jesse1
Up vote reply of Jesse1 Down vote reply of Jesse1
Add a Comment

I'm getting the same thing on macOS 10.13.6 after 6 nodes, I start getting these errors

Posted by
nthState
Up vote reply of nthState Down vote reply of nthState
Add a Comment