Hi,
Long time cubase user here.
I got cubasis a few months ago for iphone 14 pro max, and recently got a shure mv88 mic that plugs in via the lightning socket.
I can only use bluetooth headphones to monitor audio, when trying to use the mic but the huge problem is the latency, when trying to overdub/multitrack (even if i use the phone’s inbuilt mic).
If I use some wired earphones with an in built mic, the latency obviously isn’t nearly as much of an issue, but actually is useful for me to gauge what the difference in latency is.
So what would be useful there, is if i could set the project to milliseconds (like in full blown cubase), then i could determine the length of latency in milliseconds and manually compensate all my tracks.
In addition to this though, is would it really be that difficult to have something in place to calibrate the latency when using bluetooth?
Even if it’s somewhere that you would enter a number in milliseconds, manually, it would still be a huge improvement on what it’s like now, and would actually be very useable for multi-tracking demos while out and about.
I thought it might be possible with some of the latency settings already, but, no, far from it.
Please have a think about it, because I don’t think it would be very difficult for you to implement, and would solve a HUGE flaw in the software.
There are plenty of lightning to usb hubs with headphone and lightning charging port available from Amazon, I have included a link to one such item, it even says it is Apple Certified.
Bluetooth headphones introduce system-related latency, which makes them unsuitable for real-time DAW applications. While a few rare, dedicated low-latency solutions exist, they are exceptions rather than the norm.
I found a work around that works for Bluetooth headphones.
I set up an audio track with a punch in enabled, bang on a bar line (at around bar 2 or 3, not the very starting bar).
I then turn on the metronome (a default 120 bpm).
With the Bluetooth headphones enabled, I go back before the punch in point and press record, and I tap along with the metronome, and let it punch in and keep tapping along and record those taps.
Then, the recording of those taps is late by x amount of time.
I switch off snap, and manually move the track earlier in time so the taps line up with the actual project tempo (by eye) and name it ‘Align’
I then record my first audio track (a guitar rhythm part, not to a metronome in my case), to start at the same punch in point, which becomes my main reference track.
Then I record my subsequent overdubs, again at the same punch in point, but then I move those so that they start exactly at the same point as the ‘Align’ event, and it works pretty well.
I would say that the ability to be able to manually input what this latency value is (by first having the ability see what the value actually is) would be very useful and would save time without having to manually shift each track back in time.
Hope this helps highlight the solution and at least other people can follow these instructions as a workaround.