Then I'll probably release it in the store
You're aware that to release it in the store, you need an Apple developer membership, right ? It costs about USD 99 yearly.
[doublepost=1513300431][/doublepost]
That's pretty cool. Well if you think it's worth changing the backend then it might be a try. So, what's the motivation? For future features being implemented easier? Or is there some other advantage, too?
Right now im building the AudioKit framework via Carthage so I can use it in some Sample Playgrounds and have some fun.

[doublepost=1513294288][/doublepost]Ok I guess some other advantages would be:
- by having the audio engine as a framework build times could get reduced
- plus you get all of the improvements/features other people add to AudioKit for free
Correct me if I'm wrong.
I guess the main motivation is just the good ol' "Don't reinvent the wheel", and the possibility that I could cut my audio graph code in half. Not the fx code, but mostly the player code (buffer scheduling / segment looping).
When I started working on Aural Player, I had never heard of AudioKit. I started off with AVAudioEngine. And, frankly, there is nothing wrong with working directly with AVAudioEngine, because it gives you more control over the DSP chain. Also, I learned a lot about the fundamentals by working with AVAE. So, it was a good start.
However, at this point, having seen that AudioKit also works with AVAudioEngine under the covers, and having some confidence that their framework works, it may be worthwhile to just swap out my buffering code, i.e. the reinvented wheel, for a tested and trusted 3rd party framework that works, thus reducing my maintenance overhead (fewer lines of code).
From what I have seen, AudioKit exposes the underlying AVAudioEngine as a static var, so, if, at any time, I need access to it, I can grab it easily and work with it directly.
Yes, it is also nice for future extensibility and all the nice bonuses I get by plugging into AudioKit. For instance, maybe someday, I could add a tunable synth to play alongside the player track

If someone wants to do some live impromptu performance, adding a synth sound to the original track while it is playing, ... AK can do that. Who knows what might come of it someday
At this point, it is just an idea. I have to see and make sure this is possible, while not breaking any functionality. I suspect it should be fairly straightforward, but need to prove the concept.