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.
Korg Gadget: Dead track bug recently
Hey all,
Have had a new bug start occurring recently, where instrument tracks in Gadget will just completely 'die' and stop functioning, until the gadget is changed.
Has anyone else been having this recently?
Cheers
Bug report quote below:
"
Have been encountering quite a serious bug in Gadget for the past week or so.
Sometimes an instrument track will completely cease to function. Clips will play, but output no sound, with no meter reading. (And no, no tracks are accidentally muted or soloed). This usually affects one gadget at a time, and occurs whilst editing that track. It has happened across on multiple different gadgets and occurs regularly.
The tracks completely stop outputting sound. This persists on reload/reboots. Duplicating the track copies the issue. Changing gadget resets to functioning. Track ends up needing to either have gadget changed , then have all parameters set again or be deleted and clip copied to a new instrument.
Behaviour is akin to the track being irreversibly muted, (though obviously with mute unselected.)
I've used Gadget daily for a number of years and this has never happened until within the last fortnight. It now occurs fairly consistently with every use. So perhaps there is an issue in the latest update?
"
Comments
Not experienced this yet.
Any specific gadgets or does it seem random?
What device and iOS version?
I assume you have started a fresh new project (or better yet: “Reset current work” from Gadget’s Utility menu).
i use gadget quite a bit and thankfully haven’t seen this yet... however i will report back if i do
Seems to be random gadgets. Haven't noticed any particular patterns. Has happened in the last hour alone on Darwin and Vancouver.
No, thankfully doesn't need a fresh project. Using 'change' to reset that gadget fixes it. But of course you lose all your instrument settings for that lane, so have to start fresh on parameter tweaking.
Does rather bugger up flow when you're working on something!
Used Gadget for 4 years over several devices and not had this issue before.
Currently on 7th Gen iPad, ios 14.2
I meant starting a fresh project to make sure it’s not a ‘corrupted’ project which keeps causing it.
That sucks. Have you tried saving the project / restarting Gadget / loading the project. To see if this solves it?
Has happened on multiple projects, so doesn't seem to be the case, as far as I can tell.
Yup and nope. It stays in the saved project. After reload file/restart Gadget/reboot iPad.
Very odd...
Was hoping others might have experienced it, as that'd increase likelyhood of an upcoming fix. After so long, using Gadget so regularly, its super disconcerting.
@LoremDimSum : I wonder if it is related to iOS 14.2 which had serious CoreMidi issues addressed in 14.3.
If you haven't, be sure to report to Korg.
Yeah, update to iOS 14.3 if possible.
If it remains you could attach an affected project to the bug report on Korg’s site.
True true.
Will update to 14.3 and test for a while.
Will report back for posterity's sake.
Cheers
Thanks!
The update just dropped and audio recording is working again
It’s got some other fixes as well and the category browser for Fairbanks is a welcome addition.
Cheers!
Hola, just reporting back:
Since updating Gadget to 4.6.6 and iOS to 14.3 the bug has stopped. Phew!
Still persists in sessions saved prior, but at least that's easily resolved by setting up instruments again. No new occurrences.
Glad this problem didn't seem to affect many!
Whilst I'm here:
Have often wondered if there's a way to bake/apply Gadget's swing to the MIDI tracks it exports (as, could be wrong but, MIDI exports from Gadget seem to be the pure MIDI timings without swing. I suppose because swing is just controlling playhead speed?)
Not a biggy as have generally just been reapplying swing in Ableton. But does feel an odd QOL quirk for there to be no ability to bake-in. Anyone have any experience with this?