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
What convention does OnSong use to send tempo by MIDI CC?
It looks like they use a pair of CCs for MSB/LSB, default 106/107. Not sure how you could use that in LP, though. They don't seem to support Link, which would be a much cleaner solution.
From the online manual:
1) MIDI Editor: https://onsongapp.com/docs/interface/menubar/song-editor/menubar/metadata/midi/editor/
2) MIDI syntax: https://onsongapp.com/docs/features/formats/onsong/metadata/midi/
3) Setting the tempo from OnSong (video):
(6:44 sedig tempo to BeatBuddy).
I have used OnSong (lyrics/chords) for sending midi settings like the the tempo to the BeatBuddy (BB) and VoiceLive 3 Extreme (VL3x) - and the presets on the VL3x.
I’m using a midi pedal to turn to the next song in OnSong - with all the settings. Extremely effective.
I now want to adjust the tempo in Loopy Pro - with OnSong by sending midi cc command(s) to Loopy Pro.
But …
When I send cc 1-127 to Loopy Pro, the tempo in Loopy Pro is set to 10-500.
That’s my challenge now …
By using StreamByter in Loopy Pro??
i don't see anything in the links you posted that indicates OnSong uses CC to send a tempo value. Perhaps I missed it. i didnt watch the 16 minute video. if the information is in the video only, please explain the details of the protocol they describe for sending tempo via MIDI CC.
can you post quotes here or summarize how OnSong sends tempo via CC?
Tempo information is typically not sent when using midi clock (midi clock doesn't send tempo). It is calculated from received clock ticks. Ableton Link includes tempo information but not via MIDI%
See my previous post for the formatting specifics.
In AUM, you can use a PB message to MIDI Control to set tempo. The following StreamByter script converts the default MSB/LSB on CC 106/107 to a PB message that works in AUM. Can Loopy Pro use PB to set tempo? If so, you could tweak the constants at the top to make it work.
…
Like @uncledave said:
“ It looks like they use a pair of CCs for MSB/LSB, default 106/107. Not sure how you could use that in LP, though. They don't seem to support Link, which would be a much cleaner solution.”
What I do in OnSong, is putting a MIDI CC with a value (example: “midi: CC10:127@0”). Then I put Loopy Pro in a learning state before I send the midi cc10 with value 127 (tempo) to channel 1 (@0). See the attached image from loopy pro.
After the learning process in loopy pro, I can change the value I’m sending from OnSong — but with the 0-127 limit.
Midi value 0 sets the tempo in loopy pro to 10.
Midi value 127 set the tempo in loopy pro to 500 (100%).
If you change the maximum to 137 BPM, you could exactly hit any value from 10 to 137 with a single CC. Or make the maximum 264 to set any even tempo from 10 to 264.
@OlaRos : what tempo range do you need. There will be a way to set something up. But the details will depend on the range.
@uncledave : unfortunately loopy pro doesn’t yet use pitchbend for incoming midi control but it is on our to-do list
Could he load AUM with my script, then use Link between AUM and Loopy Pro?
There will be a method that won’t require that once we know his desired tempo range.
Once we know the range, we can use streambyter to send different tempo ranges on different channels if the range is more than 128…and if a range of 128 is sufficient, it is just a matter of setting the midi binding’s settings.
I think the lowest tempo in OnSong is about 40 bpm. I’m happy … if I can set the top of the top of the tempo to about 167 (40+127).
The tempo range will then be 40-167.
With this - limitation, I can send midi cc 0-127 from OnSong to Loopy pro - which also works when I tested.
CC value 0 will set the tempo to 40.
CC VALUE 127 wil set the tempo to 167.
Not to throw a wrench into anything, but just to note ...
OnSong does appear to send MIDI Clock, which could also be used to control the tempo, and for other things such as start and stop.
https://onsongapp.com/docs/interface/menubar/utilities-menu/editors/midi/settings/
So, are you all set now?
It works.
But I would like to see a MIDI 14-bit solution (MSB/LSB) to achieve 16,384 steps and offer smoother control for parameters like pitch and volume. If I understand you correctly, it could happen.
So yes, I'll settle for this, but I'll look into how I can send a cc value from OnSong that gives the exact same tempo value in loopy pro (40-167 instead of 0-127). I'll have to play around with StreamByter a bit.
Once again - Thanks a lot for your input! You're all fantastic contributors!
It might be worth a try using MIDI Clock instead. That's how most apps and hardware sync with each other when they don't support Ableton Link. It should be plenty stable, especially if the two apps are on the same device. If they're not and you're using wifi to communicate, then perhaps not.
It's already been tried @wim. But OnSong drifts and is very unstable. It takes about 20-30 seconds before OnSong delivers a somewhat stable midi clock - even with midi clock over usb c cable (please see OnSong's own video a little further up in the discussion). And alter a short time (about 30-40 seconds, OnSong stops to send midi clock - even when the app can run in the background).
OnSong can’t reproduce this error. And that’s really strange! I have this problem on my iPhone Pro and iPad Pro. Also after a complete reinstall on both devices …
It’s a complete new discussion, but if you have OnSong by yourself, it would be very interesting if you could also test the following:
1) Use Onsong and Loopy Pro on the same tablet. 2) Make Loopy Pro ready to receive midi clock (use virtual midi under the sync menu).
3) In OnSong: activate midi clock and scroll to a song where bpm is set.
4) When you now switch to Loopy Pro: what do you observe with tempo in LP? Does the tempo jump to a very low value - and stay there and drift for a while, before it stabilizes at the correct tempo?
Have you tried JustChords yet? It’s pretty neat and easy to use, syncs with iCloud, has a proper app for Mac, an AUv3 extension and is free (no subscription). Had been a longtime OnSong user but not looking back.
Never - but testing now. Possible to send midi-clock? How?
Hi @OlaRos , ok, I just thought it might be worth a try. I don’t have on song, so I can’t help with other testing. I feel like there could be some way to get a finer control over the tempo using that MSB/LSB, but I’m not sure I can pull it off. I’m glad you have something that is OK for now.
Sorry I’m not actually using that midi clock feature. But from what I read about that AUv3 extension it should work. I hope you’ll find out. Otherwise there is a JustChords Discord server with the dev and other friendly people that surely can help with that
https://discord.gg/y6ZBfUFp
I don't think that JustChords can send MIDI Clock at this time, but it sounds as though the developer is interested in adding that functionality. Such a wonderful developer. 👍🏼😎
It can send midi messages on song load, but then you have the same precision issue as with OnSong.
Hi @OlaRos - is that you (Olav) active in discussion with the developer on Discord recently?
JustChords can be run as an AUv3 plugin in Loopy Pro. You could conceivably control the song switches and tempo switches in Loopy Pro and JustChords would follow along. For instance, you could have a stepped dial that would load the songs you want and set the tempo.
I suppose you could use the same approach with OnSong. Loopy is so flexible with it's widgets and actions that you might save yourself a lot of trouble by controlling things the other way round.
Foregr> @wim said:
… yes
Hey @olaRos. I noticed OnSong can be programmed send tap tempo. I suspect that would be the ideal method for OnSong with Loopy Pro.
It's a premium feature though. I don't know if you have that.
nvm. I think Loopy Pro rounds off tap tempo.