Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Incorrect Pitch in Pianoteq 9 within Sessions - Solved
I’m using the new Pianoteq 9 with Sessions on my iPad. Strangely, the pitch in Pianoteq 9 is incorrect when used in Sessions. When I compare it to Pianoteq 8 and other plugins, Pianoteq 9 is slightly more than a semitone too high. The problem seems to occur only in Sessions—in AUM and Logic, the pitch is correct. Has anyone else encountered this issue?
Comments
What sample-rate are you using in Sessions?
48 kHz.
Using 44.1 kHz vs 48 kHz uncorrected produces a pitch shift of 147 cents. So that may be the problem.
Good to hear that I'm not alone.
I had the same issue with Sessions and Pianoteq 9. Pianoteq 8 has no problems.
I noticed that:
Pianoteq 9 does not allow 48kHz.
Pianoteq 8, on the other hand, does allow it.
Unfortunately, setting Sessions to 44.1kHz does not help.
Same here.
Pianoteq 9 can be set to 48kHz in standalone mode.
As AUv3 max. 44.1kHz
So then it's definitely a 'bug' in the AUv3?
It seems more likely that the problem is with Sessions, given that the plugin works properly in other hosts.
True, the developers are pretty responsive so sending them a message won't hurt
https://openplanet.zendesk.com/hc/en-gb
(Submit a Request)
Thank you all. I'll keep you posted.
I reported the issue to OpenPlanet’s customer service and received a response within two hours (excellent customer service!). The problem is indeed related to the sample rate. An update for Sessions will fix the issue (likely soon).
Thanks again to everyone!
Sessions 5.1 fixed the problem.