Does this happen when all tracks are routed to the same audio interface or only when tracks are playing through different interfaces? In the latter case, this is something I don't think I can fix. In iOS I have no control over the individual output latency when using different interfaces.
Is it maybe related to aux and main routing? If yes, do you have the master eq or any other master effect active? This could introduce some latency between main and aux tracks.
Im not using any interface at this stage, only a converter from the lightning port (the charging port) to a headphone
output converter, and the extra output is the ipads actual headphone out.
in a further post after this one i heard better latency with the click and the count (they were almost perfect)
when i only used a single output.
I spoke to a friend earlier and he has the camera kit (lightning to USB) he will lend it to me and i could then check
properly with my digital mixer (UI24R - similar to the AIR XR you have)
in any case, using the ipad like i described above rather than an interface is WAY WAY better for me, especially
as sometimes i use my mixer for broadcast (facebook etc) and us the USB port on the mixer to hook up to my mac.
so using the ipad with the ligtning to headphone out converter essentially turns the ipad into a 4 output device.
if you could get it to work even just a little better it would be lovely 😃
Also some questions about your tracks: which file format are you using? mono/stereo? samplerate? all the same or different formats?
stereo MP3 (i think 320kbs) only
Yes please, that would help. When you move the app to the background, the audio engine is stopped. That would explain why the buzz stops. But I can't reproduce that. For me the output is absolutely clear.
if you get on of these (very cheap) converters you will be able to do the same
i have this one but the generic
https://www.apple.com/shop/product/MMX62AM/A/lightning-to-35-mm-headphone-jack-adapter
Do you maybe have a plugin active on the master effect?
no, and in fact until i read through this beta thread i never even knew there are plugins for ipad.
also the EQ on the master was diactivated
it sounds so much like a laptop earth issue (i think every working musician knows that sound)
i would only think its something to do with the cabling, but i did try different ones.
ill record the sound and upload for you, sure.
also when i touch the screen the noise changes and i follows my touch so i dont know
if its earth problem or app problem.
will definitely investigate further to make sure its nothing on your end.
These settings are stored to the database when you close the multitrack window or when you quit the app. I couldn't reproduce it in any way. Maybe you could explain with step by step instructions how to reproduce this.
i treat this section as i did right from working with ST2:
i load up a song (in this case i create a new multitrack song - and add the audio files) make a new playlist, add the song to the list
and then go to song edit.
when i use pan, volume, EQ changes, they work fine.
when i shut down the app, (completely) and load the app again, the parameters ive changed SHOW me
that they visually have stayed like i edited them but in fact all the pan vol and EQ setting go back to default.
then i dont even need to (for instance) make changes in those settings, its enough that i touch
one of the faders and the changes i made reflect again BUT ONLY those ive touched.
those i didnt remain playing default setting although they seem to be placed right.
for instance, my click track is panned to the left and routed to the AUX output.
when i reload the app the fader still is pulled all the way to the left but the click is
actually playing both left and right outputs (i know because im using the bass also on AUX panned right)
only when i touch that fader (although not moving it actually) the sound of the click is running properly ONLY
to the left.
sorry i type plenty 🙂 i wasnt born speaking english so i blabber 🙂
i can record a video for every one of the bugs you need me to no problem for sure.
This was a problem in the first beta. Please make sure you are running build 6893.
trust me i am following this thread closely, i am definitely running the latest version on both the ipads
ive tested on 🙂
i will collect the camera kit hopefully tomorrow or next day. we are in (almost) full lockdown
here in South Africa so i pretty much have loads of time to test and report to you, its both good and bad,
have time but havent worked in a month again 🙁
anything else you may need?? 🙂