Midi link sync is the best workaround thus far, but not exactly ideal and it has randomly disconnected on me at inopportune moments.Īpologies, I truly don't understand the headache of developing for non real-time OS, so I know I probably sound like a whiny kid. How is that to work if they'd like synced fx and such? So I should run my sequencer off of AUM's clock, even though the Pyramid has an extremely stable clock? And people with ERM multiclocks for example that would like to use AUM in their setup. Of course, many people use hardware synths and sequencers with AUM. Hopefully this gets resolved someday because there are indeed some apps that have midi clock IN and it said:Ĭan you please propose a workable solution then? The lack of sync IN can be heartbreaking at times. ![]() ![]() Especially when we’re talking about having external hardware in the mix. ![]() Ableton Link is a poor substitute for midi clock. Yes there are “workarounds” but not very good ones TBH. Yeah, it’s actually a major issue for me too. I still love the sound creation potential of the ipad but I have fallen out of love with it when trying to sync up apps with external hardware. I think it should be a standard option, same for being able to select midi channel on many other apps where it is not an option. I have found myself more & more not using the ipad in my workflow & just moving over to hardware - not because i want to but mainly because of the lack of midi clock in on so many apps. I asked for midi clock in for AUM long ago & still wish it was implemented - this is constantly a major irritation & I don't care for workarounds, should not be necessary. We have apps that do this reliably since the iPad 1 on iOS 4.3 CoreMIDI (MoDrum, FunkBox, Genome MIDI, Samplr with hardware clock, and a few said: This much I know: Proper slaving to MIDI clock requires a high-priority, precision timer just as much as Ableton LINK and some intelligent clock smoothing to make the incoming MIDI clock usable. KORG Gadget (no latency correction either). Groove Rider (with positive and negative latency correction, still my reference for MIDI Clock)īeatmaker 3 (no latency correction but it slaves to clock better than Ableton Live) Loopy HD (will also time stretch audio when the bpm changes) Good examples for apps that follow external MIDI clock precisely:Īudiobus 3 (with positive and negative latency correction) ![]() Of course it can! But the knowledge how to implement it well seems to be rare amongst iOS developers. So i guess IOS just cant really be used with hardware when you need stable midi sync ? although think having apps runnin inside hosts as AU 3 might be the answer in the end. let alone getting one to actually keep time!Ībelton Sync seems to be the best. Of the apps that do have Clock In, my experience with getting them to even ‘think’ they are following a clock has been dismal. as soon as you add it to a software environment with non real-time serial operating systems ( Mac, iOS and Windows ) plus a host of hardware variables. Hardware device to device tempo settings and song position are fine and that’s what MIDI clock was designed for. particularly when you bring digital audio into the mix, which all DAW’s do. even on the desktop! I don’t think it’s a good enough source (resolution and the way it’s transmitted ie - stability ) to actually clock anything.
0 Comments
Leave a Reply. |