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
Enable Multi-touch in the settings.
Sorry, looks like these features are not yet present. I'll see if I can add them.
Thank you for the response.
I passed on the advice to try enabling multitouch to the other user but he was not satisfied, so this explains why.
A question.
I've been trying to get MiRack to start/stop using host sync.
I have managed to get it to successfully play
the down beat and start/stop in sync with host clock.
I have also managed to get it to reset back onto the one
but only after I hit start/stop twice rather than once.
Here is a screenshot of my first drum machine.
Could someone please double check it for me.
Thank you in advance.
Thank you.
I was trying the Logic module when
I figured out a much simpler answer.
Here's a screenshot.
I reconnected the sequencer using the example you
provided and connected the ,'start output', of the
host sync module to the ,'reset input', of the sequencer.
The ,'run output', from the Clock goes
to the ,'run input', of the Sequencer.
The clock is being sent from the Clock to the sequencer.
I've already changed the mixer as
the first mixer didn't have any AUX.
It start/stops every time now with AUM.
The second screenshot shows the menu settings.
You're spot on.
I'm going through several different combinations so that
I will know which ones to use in the future for my purposes.
The Ableton Link module is next on my list.
@gravitas , @0tolerance4silence
Rather than use the BPM output from the host, I think it's much better to run the Host Sync module clock output to the Clocked module BPM jack.
After that I patch everything from Clocked and it seems to do everything I need.
My thinking on doing it this way is I want Clocked's pulse to be as close as possible to the host's. If it's running independently just based on a BPM value, I see large potential for sync issues and drift. The pulses coming out of the host sync clock 8 times per beat should keep a much tighter sync, I expect.
>
I had tried that initially but I didn't know about the modes.
It instantly went to double the BPM.
What is P8 mode?
I noted that Clocked is automatically in CV mode.
Agreed.
I tested it this afternoon and it drifted out of sync after about 10 mins.
It seems to be doing so even more so now.
The Bpm LFO is also much tighter now.
When I press ,'start', it accelerates to 120 Bpm and then holds time rock solid.
Can MiRack accept external midi clock?
Also can I get the Ableton Live module to sync like the Host sync?
It seems that host sync is much tighter even with
sending the Bpm out to the Bpm in for Clocked
Thank you for the tip.
It P8 stands for Pulse / 8. So, if you set the Host Sync is set to send 8 pulses per beat in the first step, then you need to set the mode to match. The default is to listen to the CV that says what BPM is. The "P#" settings tell it to listen for pulses then divide to calculate the BPM. In that case, the BPM display is informational only, what is really driving the clock are the external pulses.
Sure, it's a few brief steps faster, but I pretty much guarantee you it's less accurate in terms of host sync. If only internal sync within miRack is important and synchronizing with the host or other plugins isn't important, then yes, a single clock source set in BPM might be the most accurate. I can almost guarantee you you're going to get drift against the host and other apps if you do it that way though.
When you use BPM, the only sync between the host and miRack is at the point you press start. They both start at the same time and they both start at the same BPM. However, if you change the BPM, (I assume) a new sync doesn't occur, only the changed BPM is communicated. So, unless AUM and miRack independently adjust at exactly the same instant they will be off.
Think of two cars starting off at the same time and speed. At first they're fine. If one is a fraction off from the other then they start to drift apart. If someone radios them to increase speed, they do so, but unless they increase at exactly the same rate, yet another shift occurs. That's what BPM CV is like.
But, if one driver is constantly referencing the other car's position, they're always going to be as close together as possible.
Of course, it all depends on what's most important to you, so whatever works best for you.
[edit - on this point...]
I think this might be a misunderstanding about what's happening with the BPM output. It's not sync. It's just a value communicating the BPM of the host.
Then you still don't get what I'm saying.
Sync is the app listening to the clock of the host. BPM is just a value telling the app what speed the host is running at. There is no sync (other than start/stop) in that scenario.
Using the Clock output is using host sync. Using the BPM isn't.
[edit ... of course, often when I make an absolute statement like that I get proved wrong by a developer. I'll be happy to be proved wrong, but I don't think that will happen in this case.]
👍🏼 Cool. Thanks, you saved me the time setting up tests.
Did you by chance try a similar test with using the other method? There's always a chance that could be off too.
@0tolerance4silence @wim
I've tested it using Wim's method on two iPads side by side.
I speed up the tempo and then slowed it down.
The sync is much tighter.
Thank you both.
Edit: spelling mistake...That should be ,'sped', rather than ,'speed'.
@Gravitas @0tolerance4silence @wim
Really interesting + helpful discussion + problem solving regarding sync.. again, this forum showing what it does best.. thank you because I know I'll be running into this issue soon..
Thanks for doing all that testing. It's always better to gather objective data. I usually start with the "objective" assumption that I'm always right and don't take it any farther.
@0tolerance4silence @wim
Thank you both.
Lololol this made me smile.
@mifki its possible to add some more cable colors please???
Earlier in the thread someone suggested initial drag direction as a possible method for selecting cable color. I think that would be a great way to support 8 cable colors. (Left, right, up, down, and the 4 in betweens)
Hm I missed that, interesting idea.
i can see it a bit improved - after initial drag, circle color picker appears around connector - as soon as you enter some color area with dragged cable, it switches to this color (i mean cable). As soon as you leave outer cicle, color picker disappears ...
Agree on more colors being useful !
Another argument is that Chris Meyer in his quite useful book (with Kim Bjørn) and his learningmodular.com courses uses a system with
white/grey for v/oct,
blue for modulation,
green for clock,
red for gates and
yellow for audio,
which seems like a tidy system for color-coding. But to implement it we would need at least an additional cable colour (the white/grey one). and as others have suggested, a intentional way of selecting color would be really nice as well.
In case you are interrested the book is here
https://www.kickstarter.com/projects/1795693416/patch-and-tweak-exploring-modular-synthesis
and his courses can be previewed with a trial membership on "linkedin learning".
I would like to see a few more colors. I try to use each color for specific functions though for audio, since there are stereo options, I like to use green and red (green if its a mono signal). Then yellow for clocks, gates, command signals like reset, and blue for CV. A few more colors would definitely be handy. As for selecting which color, I’m ok with the current method...I do a ‘tap - small slide’ to see which color comes up and when I see the one I’m looking for I continue to drag it to the destination. The colors cycle thru so it doesn’t take long. However adding many more colors would make this method considerably less efficient. The idea of an initial direction would be a good solution for this.
Okay, here's another basic question.
I've connected up the Modal synth module with the Basic Midi module.
I'm getting sound, it changes frequency as I play it using my
midi keyboard but it inverts the velocity for some reason.
When I play quietly it plays loud, when I play loud it plays quietly.
Is this expected?
What do I do to make it respond to velocity correctly?
Thank you in advance.
Edit.
Here's the screenshot.
Does the same on mine. Have the velocity control the volume with a dual vca after the synth module.
@Jocphone
Thanks for confirming this.
I was thinking to try to invert the signal in some way
as the inbuilt tone changes according to velocity.
Still, if it isn't possible then a dual vca is the way.
According to the manual, the Strength input isn't exactly a volume parameter, and more importantly, it's bipolar whereas midi velocity is not:
So, it's only amplifying the excitation signal, not the overall volume to begin with. But also, midi velocity output is 0V - 10V, or 0 - 30dB, when it would need to be -5V to 5V to work as expected, I think, but as mentioned, would only affect the strength of the excitation signal.
@mifki any chance the strength input on the Audible Instruments Modal Synthesizer is inverted?
I read the manual entry for the real thing but it appears to work opposite to what @Gravitas and I would expect when fed with a velocity signal.
Okay, I've got Ableton Link working now.
It has been the most consistent so far.
I'm going to give another couple of days of testing
but after twenty minutes it's holding really well where
as with host sync it would've skipped a beat by now.
Hm it is indeed inverted, but the original Mutable Instruments code seems to be doing exactly the same. I need to do some research to see what's going on there.
How does velocity output, which goes from 0V to 10V map to an input that goes from -5V to +5V?