03-05-2021, 07:10 AM
Steve: Yes, the recorded tracks are not the same length, but that is not equivalent to the latency. It just means that the remote recording started later and ended later. I have not been able to translate the difference in length to an offset.
The latest from yesterdays recording session:
I had the following files locally:
Track 1 (stereo) and Track 2 (stereo), RT-Mix, all WAVs
My partner sent me the remote track she recorded.
The two local tracks were exactly the same lengths in samples and totally in sync.
The RT-Mix was 110 samples shorter, but nonetheless in total sync with the two local tracks, I could check this easily by playing them together with the polarity reversed, and it cancelled the local tracks completely.
The RT-Mix was also in sync as far as our playing went, I think this is exactly what we heard in the headphones, there is no reason to assume otherwise.
This now allows a very simple way of syncing by just having the remote participant clap his/her hands.
I can load all these tracks into a DAW, and while the local tracks and the RT-Mix start at exactly the same time, I can now move the remote track slightly forward until the clap in the RT-Mix and the remote track align perfectly by looking at the waveform. (I have not been able to cancel the tracks by reversing the polarity, but I assume that's just because what gets sent over the internet is not close enough to the real track.)
In my case the offset was 258ms, but I am not entirely sure this is the same each time, and it almost certainly isn't the same with other setups and internet speeds.
We will record again tomorrow.
I actually doubt that JamKazam has any way of determining the exact latency itself, which is the reason why the final mixes are of no use whatsoever. They are not in sync.
Anyway, with this method I think I can live, for my use it works well enough.
The latest from yesterdays recording session:
I had the following files locally:
Track 1 (stereo) and Track 2 (stereo), RT-Mix, all WAVs
My partner sent me the remote track she recorded.
The two local tracks were exactly the same lengths in samples and totally in sync.
The RT-Mix was 110 samples shorter, but nonetheless in total sync with the two local tracks, I could check this easily by playing them together with the polarity reversed, and it cancelled the local tracks completely.
The RT-Mix was also in sync as far as our playing went, I think this is exactly what we heard in the headphones, there is no reason to assume otherwise.
This now allows a very simple way of syncing by just having the remote participant clap his/her hands.
I can load all these tracks into a DAW, and while the local tracks and the RT-Mix start at exactly the same time, I can now move the remote track slightly forward until the clap in the RT-Mix and the remote track align perfectly by looking at the waveform. (I have not been able to cancel the tracks by reversing the polarity, but I assume that's just because what gets sent over the internet is not close enough to the real track.)
In my case the offset was 258ms, but I am not entirely sure this is the same each time, and it almost certainly isn't the same with other setups and internet speeds.
We will record again tomorrow.
I actually doubt that JamKazam has any way of determining the exact latency itself, which is the reason why the final mixes are of no use whatsoever. They are not in sync.
Anyway, with this method I think I can live, for my use it works well enough.