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.
Xequence Piano Roll Problems with larger MIDI Files
The user and all related content has been deleted.
Comments
It’s a very large file and zooming in will likely take up a fair amount of processing.
There’s an option to view just selected data. Would this help?
Maybe even copying a track and the cutting a specific smaller section you wanted to check out may help also?
@tja: The problem will go away if you split the single large part you get after import into smaller sections (you would probably want to do that for "organizational" reasons anyway). The problem is that currently, when you open a part, Xequence will render the whole enchilada into memory all at once, so it's better to split it into smaller parts.
I have a rewrite of the Pianoroll and Controller editors on my plate which would eliminate this problem, but it has taken the back seat so far...
EDIT: You can select any number of parts on any number of tracks and split them all at once at the song position ("Magic Wand" -> Split), which should streamline the process.
@tja: The backseat is rather full, sometimes I'm thinking it's actually a bus
Yes, Cubasis is better at editing large continuous parts... every app has their strengths and weaknesses, I guess... but I'm still striving to make the one app that kills them all (metaphorically)
Yeah, I was kinda impressed when loading that big file into Cubasis last night.
However, Xequence has real strengths in smoothness of midi editing and manipulation of the note data. Very happy with how the app has progressed!
@SpookyZoo: Thanks
As a sidenote I've just pushed the 1.7 update to Apple and if we're lucky and they're having a good day, we might see it before easter 
Sometimes with large Midi files it can seem like the app is hung or crashed, but after waiting the data finally loads. It could take like 30 seconds or more sometimes if the piece is long and has multiple tracks beyond just 1or 2.
@CracklePot hmmm, there shouldn't really be any problems in the Arranger view, no matter how many tracks or notes... only as soon as you open a part for editing...
Or do you mean there's a large delay while importing the file?
Lol, no not Xequence. Just my general experience when generating large midi files with some generative apps. If the composition is minutes long with more than about 5 instrument tracks it takes awhile to load it back in to hear it, and the app seems frozen while loading the file. Shorter ones or limiting the tracks to less than 3 and it seems to pop right up.
Sorry about the confusion.