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
Notes will work with the AUv3 parameter.
@stim, I can confirm that you can trigger patterns with midi notes direct to the plugin.
Hey @wim,
thank you very much for reporting the issue "I don't think Octachron is feeding back AUv3 parameter values to the host". I did not realize I'm missing this part. It's working for active and mute parameters. But I was not properly updating it for the pattern change parameters. I'm uploading a new beta right now will release it as well soon.
Cheers
Markus
Hot diggity!
Nice! Thanks @TasTax. That’ll make using Octachron even nicer in Loopy Pro and Drambo, among other hosts. 👍
When I use Octachron in Aum to control Oneshot I use the oneshot preset.
But it doesnt work.
Only the kickbass is makes a sound
The rest of the sounds like sd make no sound while I do have made an sd in oneshot.
But octachron doesnt trigger it.
Anyone got an idea why?
Look in Onshot to see which note is triggering along the bottom of the screen as Octachron plays the snare. Make sure the sd that you set up is mapped to that note. If not, change it either in Octachron or in Oneshot.
Yes thanks,
I was hoping it would do that automaticly since it is a specific preset in Octachron
Octachron doesn't have any way of knowing the actual assignments in OneShot, since those are customizable. The Octachron preset is just a guess at a typical setup. You may have more luck using the General Midi 16 or General Midi 8 Octachron presets. Many of the OneShot kits are set up for the General Midi drum map.
Oke. Thanks for the tip!
Heyhey @Meek3 and everybody!
Thx for reaching out. And sorry that our preset does not work accurate with the current version of OneShot.
Could someone maybe share his working preset here with our share function? Then we will integrate it in our next update.
Thx a lot and best greetings from Munich 🙂
Tas
Hi @TasTax - the compatibility isn't version dependent with OneShot. Kits don't have a fixed mapping and they can be altered as well. I'm not sure how you could have a general OneShot preset. Most OneShot factory preset kits are General Midi mapped, I think.
A shame that not all drumcomputer apps are general midi. Would be easier I think.
There are a number of problems with that. There are 46 notes defined in the GM Drum map. Most drum apps don't have nearly that many sounds. For example, there are six possible toms. What do you map to when an app only has three? What do you do about apps such as Ruismaker, that can define any sound on any pad? How about Ruismaker FM that has only six when Ruismaker has eight?
There's no simple answer to drum mapping that works in every case. The best you can hope for is apps like Oneshot and Octachron that make it possible to customize maps.
OCTACHRON has stopped working with Audio Evolution Mobile The sequencer won’t run. But other MIDI sequencer AUVs work as normal.
It still works with my other DAWs (NanoStudio 2, Drambo, BAM). Neither OCTACHRON or AEMS have been updated since it was last working. I’ve not updated my iOS (16.7.14) either. I’ve restarted my iPad.
Anyone have any clues? I’m going to post on the AEMS thread as well.
See my reply on AEMS thread
Reinstalled OCTACHRON, which didn't fix the problem. Reinstalled AEMS, which did. Thanks, anickt!
😎✌🏼
Ok, I see, thank you! 😊
I’ve been trying to lay out drum tracks using OCTACHRON in AEMS, exporting sections as midi clips for visual arrangement. But midi clips exported from OCTACHRON always play back at the wrong tempo, like 4x faster, as if there’s a clock divider mismatch between both apps. Any clues as to what I may be missing?
Is anyone exporting midi clips from OCTACHRON and laying them out in a DAW timeline to build drum parts? Interested to know about others’ results and workflows using OCTACHRON.
I think if I was using OCTACHRON in a DAW I'd just record the MIDI output straight to the timeline. I don't think I'd bother with exporting to MIDI and importing. I'll fool with it a bit if I can find the time, but really can't think of anything I'd use it for.
Unfortunately, AEMS doesn’t record midi from AUVs. I do have other DAWs that do that, but it’s odd and frustrating that exporting midi clips doesn’t work as expected. The tempo issue is the same with other DAWs.
I tried it both ways and the MIDI files play back as expected. 😎✌🏼
AEMS does record MIDI from Octachron. Press Record on the AUV3 page.
Well doh! That’s me with my foot in my mouth again!
Recording OCTACHRON’s midi output into a track works a treat and will do me fine. Idk where I got the idea that AEMS doesn’t record midi plug outputs. I think I read somewhere that it won’t record midi from one track to another.
In any case, it’s bizarre why my exported midi clips work that way. I tried a workaround with Drambo and SAND as intermediaries, with mixed results. Drambo won’t even record OCTACHRON’s output into a track properly, with dropped notes and timing issues even with quantize off. SAND records the same perfectly and midi exported from it plays back perfectly as well. That would have been a feasible workaround—albeit requiring an additional step—if you hadn’t clued me in on AEMS’ track record.
Much thanks anickt!
How did you go about recording the MIDI in Drambo? I've had a few issues with plugins in the past with certain methods, and may be able to suggest a better (or at least different) way that works for me.
I set up Octachron to trigger Bilbao, then engage the 'Rec' button on Octachron's module panel. I make sure the clip is of sufficient length and that record quantize is off, then hit 'play' (I just realized it's not necessary to hit 'record'; just engage 'Rec' on the module panel). This records Octachron's midi output right on the track. I then disable Octachron and behold my wondrous missed notes, unintended flams, and unrecorded controller messages!
Here's how I do it. I don't like the normal REC workflow at all. In fact, I'll go as far as to say it's terrible.
I've never had that method fail.
Tried it and there’s some improvement. I didn’t get any dropped 16th notes this time. But note repeats, pan, level, and decay messages I had programmed in OCTACHRON weren’t captured. I suppose some tinkering in StreamByter can fix that, but I don’t really need to record midi like that in Drambo anymore since I got it working in AEMS. Still, it’s a good technique to know. Thanks for your help wim!