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.
Enso - The best way to midi trigger?
Hi guys Happy New Year to all. I am scratching my head to find a solution. I want to remotely trigger Enso in either AUM or Audiobus. I have Mozaic, bought a month ago, Midi designer Pro and a New Year present of Midifire. (Yep I too have the app bug). Can you suggest a method of triggering Enso so I don’t have to have its window open? I do also have a Launchpad Pro and can bluetooth it but but find it very limiting on IOS. Cheers guys in advance of any ideas you may have.
Comments
AD have a longish (45 min) full walkthrough video on their site. Useful midi bindings are discussed near the end.
Ok now I understand the settings. I tried many different combinations but this looks very promising. Thanks. Do you know of any activation scripts out there for Enso triggering.
No script, but here’s my setup for sending CC using Xequence pads:
Fyi....there is a minor bug when saving settings; Audio damage is aware of and I was told a fix would be coming (about a month ago). After saving, the next time you reopen Enso the trigger setting changes to play. Therefore you cant just start recording. You have to hit “X” first to clear it which puts it ready to record. No biggie but just an annoying extra step you have to take, especially if you have more than one Enso saved in the set.
Even though this is an old thread, I'm adding a pointer for people trying to figure out how to bind MIDI to Enso.
Enso's MIDI binding system is novel and can be frustrating. There are two ways to bind to Enso. The 8 MIDI settings within the app window, and the AU parameters made available through AUM (or your DAW). Some parameters can be bound one way, some the other, and as far as I can tell there isn't any overlap--e.g. it you want to control STOP you have to do it in the app window, to control FEEDBACK you have to do it in AUM. It's frustrating because there are only 8 slots in the app and at least 16 parameters that can be assigned to the slots. If you fill up all 8 slots and there's a 9th parameter you want to control, you're out of luck (they aren't available in the AUM list). You have to decide which 8 parameters are most important to you.
When Enso crashes (for me, every once in a while) and you just reinstall Enso, you'll lose all settings inside the app. If you restart AUM, the settings a retained. Go figure!
I love what Enso does. It's totally unique and essential to my setup. But can't wait until the developer fixes this MIDI thing.
BTW, the "on release" feature in the slots can be very handy. I use it in an automation to STOP when the volume slider for the track that holds Enso goes to 0 (release).
**Feature request: **. Make ALL parameters available in AUM. Then the 8 slots would be an option that could be ignored if we want to do all bindings in AUM.
Steve
I tried for hours yesterday to get Enso 'Play speed' to respond to a MIDI cc through the 'play speed' parameter in AUM... and failed. AUM wants a value between 0 and 1 and there was nothing I could do to get 0 to 127 mapped from Mozaic through AUMs 0 to 1 into Enso's -4 to +4 for play speed. Has anyone got this working?
What AUM is telling is not what AUM wants but what ENSO’s declared parameter range is. AUM maps the MIDI to that range. By default midi 0 gets mapped to 0 and 127 to 1.
You will need to do some detective work to figure out how those translate to ENSO’s displayed speed values.
If Enso's play speed range is -4 to +4, then you'll get 0 between CC values 63 and 64, +4 at 127, -4 at zero. You don't need to do anything to achieve this mapping; it's handled by scaling.
Enso's internal scaling for play speed doesn't seem linear or there is something weird going on with AUM. Sending midi 0 gets play speed -4 and sending 127 results in play speed 4 as one would expect. Sending 63 yields -2.61. 100 yields 0.4. 05 yields 0.97. 106 yields 1.09 . 110 yields 1.59
Interesting. I wonder if it's requesting logarithmic scaling from AUM. Now you cannot do log scaling starting from 0, and apparently AUM says the range is 0 to 1, but it could be truncating 0.01 or 0.001. I don't have the app, but if you can provide a few more data points, I might be able to work it out.
Anyway, the answer for @belldu is to just send in different values and see what comes out.
Thanks for the replies. Firstly, I concur that there is a degree of non-linear behaviour going on that I don't understand.
This Mozaic script highlights the issue:
@OnLoad
ShowLayout 0
_midiCcValue = 0
Call @SendAndUpdateUI
@End
@OnPadDown
_midiCcValue = _midiCcValue + 1
if _midiCCValue > 127
_midiCcValue = 0
endif
Call @SendAndUpdateUI
@End
@SendAndUpdateUI
SendMIDICC 0, 102, _midiCcValue // map 'Play speed to cc 102' in AUM and attach Mozaic as Midi source
LabelPad 0, {cc value: }, _midiCcValue // send cc on channel 1
@End
Looking at Enso, the cc to play speed values are:
cc playspeed
0 -4
20 -3.92
40 -3.55
60 -2.77
80 -1.48
100 0.4
105 0.97
110 1.59
120 2.94
125 3.69
127 4
So is this logarithmic scale? And, for example if I just want to set the play speed to 1.5, what formula would give me the right cc value (around 109.5)?
Midi values are integers. You can’t send 109.5. You can send 109 or 110
@belldu What speed settings are important for you to achieve? Is there a setting of the Inc control that would make the MIDI mapping easier by reducing the number of possible speeds mapped across the CC range?
@espiegel123 , of course, you're right... so its not possible to use cc values with whatever algorithm Enso is using (maybe logarithmic) to set play speed to 1 programatically as it would be somewhere between 109 and 110 cc value. I also tried setting AUMs 'value scale' to offset it, but I still couldn't compensate for the non linear mischief that was happening next...
So yeah, I'll try to use inc and dec instead and track what the updated value is in Mozaic.
All pretty hard... I was just wondering if anyone had solved for this? Sounds like setting 'play speed' needs some pretty advanced maths!
With some experimentation you could change the range in AUM if you don’t need the full -4 to 4 range.