Audiobus: Use your music apps together.
What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.
Download on the App StoreAudiobus is the app that makes the rest of your setup better.
Any tools for having audio / midi (pre)Delay in ms ?
Hi,
I find the need a lot in AUM to have a real time fixed correction in timing for audio or midi.
In a lot of cases things are running sync but still there is a little offset depending on the plugins. Especially with loop based or midi sequencing plugins.
This would be really helpful to manually correct or to use this in a creative way.
Something like a 0-500 ms correction negative\positive on a channel or via a midi fx.
Any ideas or suggestions ?
Comments
Which apps?
All AU apps should* be sample accurate if you are not using Ableton Link.
The default compensation works well.
I think i read somewhere that automatic plugin latency compensation (final solution for issue you described) for AUM is on the way .. @j_liljedahl am i right, or it is already there ?
It would be extremely easy to make a Mozaic plugin to provide a variable midi delay. But it could only be a Delay not a pre-delay. And it would be only midi, not audio.
AUM does latency compensation as needed. So if a plugin introduces latency (delays the audio signal) and reports it to the host, AUM will delay all other signals in individual amounts to make them all align at the outputs.
If you're having trouble with AU plugins not syncing properly to the host clock, it's probably an issue in the plugin. Or maybe you're introducing additional delay somewhere else outside of AUM?
ApeMatrix now has per track latency compensation which can be used in creative ways, worth checking out...
Beat me to it!
I was just thinking that this could be a 1-line script
Because many plugins don't report latency properly (and in the case of IAA apps, not at all). It's useful if all apps provide an ability to manually set delay compensation. This is achieved by setting a negative delay on the host channel in question.
Even with AU's that report latency correctly to the host, the nature of midi parts with long attack envelopes will necessitate manual tweaks. This is simple with non looping parts, as you can manually 'slip edit' the part into place. With looped parts you often need negative delays to ensure the part plays with apt timing.
Quite obviously no plugin can predict your needs so the only way to compensate with negative delays is via the host. Many desktop Draws only offered manually configured plugin delay compensation until recent years (especially those that primarily specialised in audio - Pro Tools being a prime example).
And in this age of 'Digital Modularity', where it's becoming increasingly commonplace to mix laptop, tablet and Eurorack in the same live setup, having the knowhow to compensate for latencies manually is a skill you'll be glad to possess.
cool, thanks for clarification.
Just in case you're using Xequence as your main sequencer, it has adjustable delay per arranger track, from -200 to +200 ms.
I believe you're one of the few sequencers on the platform that gets this fundamental timing feature right. All of of the pre plugin midi sequencers on platforms like the Atari ST understood the importance of manual latency compensation. It was simply the nature of the beast when chaining a multitude of MIDI devices. Desktop sequencers these days probably feature manual latency compensation more through legacy than design but it's less important or utilised.
On iOS, the general belief that AU's are the future (no argument from me on the basic premise of that statement) has most likely bindsided many developers from the importance of manual latency compensation. It's particularly important when sequencing hardware, never mind IAA's.
I'm hoping this thread might nudge developers towards a similar approach to latency compensation as your good self.
Failing that, hurry up with AU hosting in Xequence.
In Mozaic:
Quick and dirty:
Deluxe, with global and per-channel delay:
https://patchstorage.com/wp-content/uploads/2019/05/multi-channel-midi-delay.mozaic
Cool @wim . That one deserves to be on Patchstorage, because I think we’ll be referring to it more often!
Beat me to it. Done.
(Written at and tested at McDonalds on my iPhone.
)