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
I was looking for how to record midi into NS2. Luckily I found this post explaining things, thanks guys!
I'm happy that Sugar Bytes Drumcomputer has a midi export function, so I can easily import the midi into NS2 this way.
Are there any other sequencer apps you like to record in NS2 that have the midi export option?
Can I ask if you were successful in exporting patterns to midi from DrumComputer and then importing to Nanostudio? When I import the midi file on the DrumComputer track it seems to put the steps on the wrong notes/instruments and I only hear part of the pattern. I've moved to Cubasis now but have about 15 projects in Nanostudio that I'm trying to gracefully finish
Is it not simply a case of opening the midi clip in NS2, lassoing all of the notes in the midi clip & transposing them all up (or down) 1 octave? You could put Brambos’s Rozetta Scaler midi fx (set to chromatic) on the channel and use the pitch slider if you don’t want the hassle of editing the midi clip itself.
I’m guessing (I don’t have DrumComputer), but it sounds like DrumComputer is exporting the midi at the wrong octave to me.
The reason I’m certain it’s DrumComputer is because I’ve never had an issue importing midi files in to NS2 from any other app.
Yes, its a little messy, but you can work it out:
Open DC and in settings set all midi out channels to master.
When you do the import, on the first DC track in NS2, its the master and includes all DC elements.
You need to copy the entire midi clip to the next DC track and each time delete the non corresponding elements that dont' belong to that track and repeat this processs for each of the 8 channels.
The extra 2 reverb channels can stay empty (I believe, dont remember)
I opened NS2 after a year of non use and see that DC is not listed as multi out auv. While other apps have the multi out option listed in NS2...
Is this just me?
Thanks @attakk and @bob. Will have another play in the morning and see how I go. I read a bit further back in the thread about Midi Tools and I'm thinking I might just spring for that if it enables me to write midi from DC to a track ala Cubasis. NS2 is so frustrating at times as it's such an easy and fluid tool for midi based composition but then drops you down a hole with some glaring omissions. In fairness I drove myself to the hole by not being fully aware of the limitations up front
It works well in NS2, I used to use DC regularly in NS2, but can't remember the exact details on how I did it. Believe every output channel in DC was set to master and then move your clips to different tracks corresponding the midi notes to the DC channels and remove the others that belong to other DC channels.
Also don't forget to turn off the sequencer player in DC > when playing in NS2
Thanks @Bob . We’ll some further playing this morning has produced some more weirdness. It seems that the reason most of the drum instruments weren’t playing with the imported DC midi is that NS is generating odd volume automation with the midi import and as such muting a good chunk of the pattern. Once I delete the automation track it’s almost ok but still not a duplicate of the pattern in DC. Tried the process in Cubasis and the import works perfectly so can’t figure out what’s going on. I’m thinking at this point I might just export audio loops of the drum parts and stems for the tracks and finish in Logic.
Drumcomputer exports a lot of its own modulation in the MIDI file and I suspect that NS2 just tried to do its best when applying the included automation data after import.
Ahh, this makes sense. I might see if I can turn any other options off for DC export in settings. Weird that Cubasis manages to import it without issue. Thanks RS!
@tja
thanks for mentioning Scaler, it's a shame but i really didn't know about this app till now - and i love it from first try, will definitely use it a lot, it's really great.
Just in case it will be not too complicated to you, here is simplest way how to get MIDI from Scaler into NS2 sequencer without any other external app. For me easy enough to use it
What you mean with "route audio or MIDI" ?
I just downlaoided app "ScalerLite 2" , bought IAP to get acess to all features .. loaded it as instrument in NS .. i also enabled sync with host in app settings .. now when i hit play in NS, it plays chords as defined in "C" line of plugin UI and i hear plugin's build-in SOUND (audio is routed normally in NS mixer track where plugin is loaded)
OF course MIDI is not routed anywhere that's missing implemetnation in NS, that's why the workaround with internally recording it and then drandrop on track in NS is needed
ah ok understand .. at least detecting chords form audio will for sure not work in NS cause NS doesn't route incoming audio into AU instrument
anyway good you mentioned it, i like that "Lite" thingie, will use it definitely
)
@tja - is this any help?
https://wiki.audiob.us/doku.php?id=auv3_midi_recording_workarounds#nanostudio_2
The plugin used in the example isn't Scaler 2 but the idea is the same. Of course, as @dendy mentioned, chord detection won't work since NS2 doesn't route external audio to the plugin. But it may work for capturing the midi output.
so I’ve just been getting into NanoStudio 2 and scaler control 2 And ran into the same midi issue. I downloaded the MIDI tools app and flailed around a bit. no success, but it was late last night.
I do find a reasonable work around to be to use the midi capture on scaler control itself. Then share that MIDI file to AudioShare and then from AudioShare open it back up into nano studio. Then you drag the midi file over into whatever track you need. A kludge for sure, but it doesn’t take very long.
Why you use AudioShare for this ? You can’t share it directly into Apple Files from Scaler ?
In Files popup you can go to “On My iPad > Nanostudio 2 > Library > MIDI” - so you save it directly into NS midi library from where it can bw dragged into sequencer track in NS sequencer view …
Good to know.
AudioShare is my go-to for late-night flailing
TBH, it works more often than not, which isn't saying it's best in the long run.