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.
Comments
That came across harsh sorry. I like Gadget a lot but in my opinion they took a very questionable marketing route. I also absolutely love this community, so apologies for the negative input.
I have a nice collection of smart loops drum midis. There are close to a thousand files of all styles and the entire files are loading into a Gladstone track with the count in on scene 1 scene 2 four bars repeated in scenes a fill and so on . Not sure how the smart loops do it but midi imports like this to track 10!
No worries.
That's a good thought. I might put Liquid Rhythm on the desktop through some paces and see what it sounds like in Gadget.
All good.
I don't think I could ever write using this one-measure format, but I did notice a few advantages. Singers or guitarists using Gadget for live performance can enter the lyrics or chord changes for each measure with the scene title screen. Tunes with multi time-signature changes do import okay, as long as Gadget has that time signature available. Not too bad, I have tried a few files of complicated music with many time changes i.e.: Zappa, King Crimson, various modern classical.
Now all we need is live midi out, hooray!,
Um... not so fast, Kemosabe. Not what I envisioned. I was thinking import a single MIDI track into a clip. Gadget could reset the clip to the number of imported bars of the track (up to 16)… or import a multi-track MIDI file into a scene, Gadget would create a clip for each track (up to 16 bars each.) It would not make multiple scenes because that information is not specified in a MIDI file. As you know, instead, Gadget breaks up the MIDI track(s) into 1-bar scenes, and multi track files get consolidated into one track.
This makes zero sense to me musically, and there’s no copying and pasting from clip to clip. So thanks, Korg, but I won’t be using the feature.
Another way as already suggested: Just import the MIDI file into Auria Pro (or Cubasis, MTS, etc.) Record Auria MIDI out to Gadget…
Auria: send MIDI Clock to Gadget, Each track MIDI Out to Gadget with specified channel
Gadget: MIDI sync set to Ext, Advanced MIDI: each track to be recorded set to Auria’s corresponding discreet channel
Enable Record in Gadget, Hit Play in Auria Pro
This has been an issue for me in the past. I even think I created a thread about it a couple of yeas ago. Certainly halted my use of Gadget for a while. I think somebody (Kaikoo?) created a fix with Midiflow, wasn't entirely sure how this worked. But I think the general advice is to create a silent bar to begin/ countin etc.
@lovadamusic in their defense, Korg has no idea what type of crazy midi files you're going to throw at them. You may want one section four bars, and the next sixteen. They can't determine this. In order to fit this chaos into their very compartmentalized concept, they did the most logical thing. The least common denominator.
This would all work well enough if they had any intra-clip and intra-track clip editing support. This is where they're falling down. I can handle this random box of midi Legos they're giving me if there were just some way of quickly rearranging them.
I'm hoping that the now glaring deficiencies here get them to finally do something about it. We need to be able to quickly combine clips. There needs to be a clipboard system of some kind so we can move clips from one project to another. It's never been more evident.
Please with extra please.
Midi is a well established industry-standard that's been around forever and many other apps can import all types of midi files seamlessly. We should expect no less from Korg. If one is importing a 4-bar midi file then you would expect Gadget to create a 4-bar scene. Anything less is falling short. Even though this isn't really a feature we're paying for, midi import/export is a feature that we all wanted and should have come with the app right out of the gate.
Incidentally: Zeta+ also has a 1-bar limitation when importing midi arp files into the app and I was able to do a workaround by compressing multiple bars into a single bar in Reaper (PC) - which can do this effortlessly, then re-saving the midi file. This may work in Gadget as well, though I'm not sure what kind of headaches it would create on the backside.
Midi is an industry standard, but Gadget is incredibly proprietary. Midi is very flexible, but with that flexibility comes complexity. There are so many things that can go wrong. You may know how to make a 4 bar 1 track midi file that imports perfectly, but the majority of punters out there will be firing off bad reviews once they get clip segments and 9 additional tracks of Marseille cluttering up their song structure because they didn't know what they were doing. It's just not that easy to fit external concepts into their system.
It's early days, though, and I see this as their cautious first step into MIDI import. They're clever people. I'm just hoping that whatever they come up with includes the clip editing improvements mentioned earlier in the thread, because that would help with more important things than just midi import.
.
Importing COULD create aches on the backside
I don't want to get into how poorly implemented the MIDI import is, or how I believe it could be done better. It is what it is, and iOS is quite often about workarounds or alternatives. Gadget is still lovely.
You may be right that Korg is intentionally avoiding anything that puts a burden on the user to know what they're doing, but I'm not sure of it. Presumably, if one has some MIDI data, and wants to import it into Gadget, in any case they would need to see how the two fit together. Otherwise, they're almost certainly not going to get what they want.
I'm with you in this respect- the current solution is satisfactory to almost nobody, as near as I can tell. Unless you have all the pieces you need ready and import them all at once, you're screwed. They've forced themselves to implement ways to make this feature useful by having it so hobbled to begin with.
I've wanted them to allow the export of projects to Live as Midi from the moment they released the feature, but audio-only is useful enough that this will never happen. Not the case here. They have to do something.
Or not. Maybe they only released this feature so they could play pop songs with Gadget sounds and sing karaoke at home. It's all making so much sense now.
youd think they would want to position Gadget as the "final destination" for as much stuff as possible, which would mean better implementation of this feature as well a more robust sampler, though the sampler is walking a fine line between letting people get more stuff into gadget, but no so much they don't wanna buy new gadgets. The midi import though there is no excuse for. That being said, I'm still thankful for the feature as it is a very nice companion for Chordbot and others where you can export a full arrangment.
The time signature support is a real plus in combination with Chordbot. I'll be spending some time there, too. Now if we can ever get that app to update. Going on two years now and you can tell.
Maybe I'm one of the few reasonably satisfied. I've been able to manage complex files, by examining their structure beforehand with other sw (Logic is very good at that). And here is a little piece written ex novo in Notion, exported, and mixed in Gadget without problems. All in all, a useful new feature to me
This is a big limitation IMO. For my workflow it means that midi import is only useful at the beginning of the song writing process. I tried to do something similar as @aaronpc and ran into the same issue. I tried to import a MIDI file into an existing Gadget project. No go. When you import a new project is created.
[edited for clarity]
I don't use Chordbot, and the Gadget MIDI import as it is just doesn't fit anything I do. I'm happy to see it works in some ways for some people, as I don't want to see Korg wasting their efforts.
I can't see any reason why Korg would intentionally limit MIDI import, even though it's not as simple as importing into a linear timeline. Maybe it's just something that's a lower priority, and they haven't had time to get to it fully. The way it's implemented at the moment doesn't appear to have been a major coding project. There was a time it didn't even have a proper Undo, and they eventually got around to that. And now we can trigger Gadgets externally on multiple channels. We now have some decent FX per track... Korg has been busy, and maybe soon we'll get copy and paste between clips and even a more conventional form of MIDI import.
Agreed. Happy to have this morsel, looking forward to another fuller course...
Chordbot midi import into Gadget seems a bit out of whack. Is there some prep or best practices to get this combo working nicely?
Thanks in advance for any tips.
seems fine to me. New version of chord it coming so stay tuned.
Specifically the drum track from Chordbot. Any tips on how to translate this into a London. Also are the octaves for the other tracks needing to be transposed an octave up?
Hmm. Can't comment. I've never really wanted to keep the drum tracks from Chordbot. Move them each to the appropriate key, I suppose. Different apps handle them differently.
Good point. All the drum hits seemed to be mixed together on the same 'note'. I'd probably have ended up creating new drum track to replace anyway.
Transpose the chord/melody tracks easily done.
Just wondered if there was a 'trick' to having it all import correctly.
Thanks anyway. I'll just get on with it