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.
Digital D1 and Korg Nanokey Studio
Hi all, I have a Korg Nanokey Studio connected to my iPad 6 Running AudioKit D1 Synth via an Apple Camera Connection adapter, the one with the power connector. Whenever I start playing a bit faster, the synth quits. I really like the synth but it is not usable for me. I also have synth One and many other synths on my iPad and non of wich shows such behavior. Can anyone confirm this? Thanks alot, Jens
Comments
Hi. First, you didn't mention a host app, like Audiobus, so I assume you're running DigitalD1 stand-alone. Is that correct?
Next, you might need to increase the audio Buffer Size. Try changing it in the app Settings.
Finally, to see if the app is really crashing, search for Analytics in the Settings app, open Analytics Data, and look for files whose names begin with DigitalD1. Ignore those with wakeups_resource or cpu_resource in the name; those are "normal". If there are any log files, open one and look for the line beginning with "exception" (in iPadOS15). There will be a word in all caps, maybe SIGSEGV, SIGABRT, or SIGKILL. They probably indicate a bug, and you should report them to the developer.
Also, please identify your iPadOS version, and whether you're using any other music/MIDI apps at the same time.
Ok, so i run iPad OS 15.2. D1 runs standalone, no host, no other app running. The report found in analytics says:
„exception… type EXC_CRASH …. „signal“ SIGKILL“ … termination …
I will try to up the buffersize and report if this fixes it.
Thanks
Ok, upped the buffer from 128 to 256 to 512 to 1024 - same crash with all settings.
A few months ago, I was looking through old discussions on Audiokit apps after noticing that their 909 app has poor timing, and the issue that you've posted did pop up several couple of times.
The D1 (and some other AudioKit apps) are long overdue for an update to the newer framework that is supposed to be a lot more stable.
Time will tell when/if they ever get updated...
Hmmm. SIGKILL means the system didn't like what the app was doing and explicitly killed it. From other stuff I've seen, this is usually related to the app using too much time, hogging the CPU. There's probably some jumbled explanation about that in the log. You could try the other app settings, Always On or Background Audio. Maybe Background Audio first. A problem with playing apps using MIDI is that they run a lot, with no screen input from us, so they may appear like runaway rogue apps.
Do you have the app on-screen when this happens? That may help.
The app is on screen. Background audio is off. I guess it is just buggy which is sad since it is a great sounding synth that I really would like to use in production. I guess the developer knows about this but it is a non commercial and obviously badly funded undertaking without the necessary ressources. Too bad.
@Doc_T I've just tried to reproduce your issue in the standalone D1 app over Bluetooth MIDI and it works well so far.
I'm on an iPad 6, iOS 13.7 though.
Which preset(s) were you using?
D1 and FM Player crash all the time when using it at 48khz. Not sure what sample rate you're using but try 44.1. Either way they crash more than any other synths I have.
Try enabling background audio anyway. That might tell the system to be more understanding. As I said, SIGKILL is coming from the OS, not from the app. The app is not "crashing" due to a bug.
Hm, it may be an issue with the Korg controller. I just tried it over bluetooth with the usb cable disconnected and was not able to reproduce the crash. Usually my iPad is hooked up to my master keyboard and the D1 works just fine. But since I am traveling right now I use this mobile setup. Or maybe its the Korg together with the Camera Connection Kit? However, its only the D1 that shows this behavior. I have not tested FM Player yet and Synth One also seems to run fine with this setup. I will test now with background audio on. Ah, an the patch I use is Vengaboys.
Where can I change the samplerate in the synth? I can’t find it.
And it also crashes with background audio on.
That makes me wonder if it's not MIDI Clock messages causing the D1 crash. When connected via USB, I think the default NanoKEY Studio configuration sends MIDI Clock. Over Bluetooth it doesn't.
If you can get to the Korg Kontrol Editor on a Mac or PC you can turn this off under global settings by setting MIDI Clock Source to External-USB.
Interesting @wim.
@Doc_T If you get another crash, make sure you save the crash report (an entry starting with "D" under iOS Settings > Privacy > Analytics > Analytics Data.)
Open it and use the upper right share button to save/e-mail/share it.
He checked this already, see this. It was SIGKILL, which is initiated by the system, so there's not likely any useful app info in the crash log.
I wonder if a memory leak could cause that. App starts consuming too much memory so iOS decides to kill it.
Don't think so. That would be the job of Mr. Jetsam and would appear in a Jetsam log. I believe it's some sort of time overrun. Basically, you didn't reply to my probe fast enough, so I'm shutting you down. I like your suggestion of the MIDI clock, though. If the app is inefficiently stumbling through those clock messages, it could appear to be in a run loop.