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.
Send chords from any MIDI generator to iBassist - wrong timing
Does anyone use Scaler2 as a MIDI chord source for iBassist?
How do you deal with the fact that iBassist doesn't respond to chord changes as quickly as it should?
I use the "Chord change anticipation" feature within JustChords and it works there but I can't see anything like "send chord sooner" in the Scaler2 settings.
Comments
I changed title from "Scaler2" to "any MIDI generator" because I can reproduce the same issue also with ChordBud2 and Helium (that's all generators I have).
Is there anyone who can try and confirm this?
@filo01 Some questions:
In my first AUM test, it seems ok - but i suspect it can depend on plugin execution order - since everythin needs to happen in the same timeslot, the midi plugins need to run first, iBassist needs to receive the notes right before itself computes its output. In my case the scaler 2 control midi AUV3 was in a midi lane left of the audio channel fed by iBassist.
But i probably also have to use a better iBassist preset and also Scaler 2 progression where the misplayed notes stick out better - any hint for a simple setting of scaler 2 (progression of maybe 4 chords and the sync settings) and an the name of a iBassist setting ?
Thank you @_ki for your response.
Loopy Pro exclusively (don't have other AU hosts)
Yes
Yes (screenshot below)
Yes (screenshot below)
Just for sure ... Do you have iBassist set to "Live MIDI In" mode? If you use a simple chord progression where the chords change according to the root notes (so C-Am-F-G, not A-Am-Am7-G) you should see that iBassist is displaying received chord properly (in time) on the Progression tab but play it later (see below). I'm using iBassist line preset "Eights" with 0% Jam.
I‘m going to try your settings when i return home to my iPad in the evening (EU timezone).
In my AUM test i was using live midi in and the scaler chords were detected by iBassist. I will also try with LoopyPro
Thank you, I'm looking forward.
PS: Slow down the tempo to ~50BPM
I have had that problem in Audiobus. My solution was to program the chord changes in iBassist and have it be the main midi generator for my song.
@filo01 I get the same timing problem like in your video when running Scaler2 -> iBassist in LoopyPro
It mostly takes a full beat (2 eigths) to pickup the new root note, even though the progression display changed every bar as expected.
Then i setup the same setting in AUM - also resulting in the same timing problems. But there was a difference, in the first run-through (4 bars) there was an offset of 1 eights to pickup the nee root note and starting with the second run trough even the first eigth of a bar was correctly picked up.
I then also checked using the ScalerControl an a midi lane left to a bs16i for the choard audio and iBassist for the eitghs - still the first eight of each bar doesn‘t pick up the new root note and after the first loop this probalem is gone. So no difference from using the audio scaler plugin vs the midi scaler plugin.
Back in LoopyPro i checked if that also ‚auto-fixes‘ the problem after some run throught. Kind of, it does no longer take 2 eights but one 1 eight to pick up the changed root note.
Not that this is a solution, but I have these apps and iBassist, and it's a scenario that I've encountered before with other apps sending out chord information to another app that needs to interpret the chord and there's a real challenge there because there needs to be time for it to recognize the chord, process the information and then apply it to the performance. If all of that is happening internally, in something like Logic Pro, or Cubasis, all that stuff is happening in the internal code, so processes very quickly.
Every time the communication from one app to another takes place, there's a risk of severe latency kicking in, unless it's dealt with in some sort or proactive way. An example that I came across was sending chords from Helium into StrummerFX in AUM. Most of the chord changes would be detected properly and StrummerFX would start strumming on the correct chord at the first beat of the bar on a change, but every once in a while it would choke and play some weird chord. The solution in my case was to either send the chord changes 1/8 to 1/16 beat ahead of the bar line, or to use Tone Packets, which 4Pockets developed, and this was one of the key problems it addressed.
I think it's difficult, but possible to do achieve what you're trying and I really hope you find something that works. I also I wonder if the results of each setup could vary between devices, working better on newer devices than older ones.
*Edit: Typo
Thank you @_ki for your findings. Be aware that you have to "rewind" iBassist to 1st chord before you run next test scenario.
Thanks @EdZAB for mentioned it. JustChords do that exactly like this. I have asked for help in the Scaler forum, but so far to no avail. So there is a workaround but instead of 4 simple chords I have to manually divide each bar (or 2bars) to achieve [x.75+x.25] schema. And I need 8 chord slots instead of 4 and can use this Scaler only for iBassist.
