Looping an audio track causes audio buzz

[spamatica]

Looping an audio track with current master causes the audio to seemingly get stuck on one buffer.

[terminator356]

This is with latency correction enabled, correct?
It's a known problem with the latency correction code I'm trying to fix.
Otherwise should not happen.

[spamatica]

That does not seem to be the issue, it seems to be off Den tis 11 feb. 2020 kl 19:10 skrev Tim <notifications@github.com>:

…

This is with latency correction enabled, correct? It's a known problem with the latency correction code I'm trying to fix. Otherwise should not happen. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#767?email_source=notifications&email_token=ABCFAN3JFVKN6VD6ZP6T5RLRCLS2NA5CNFSM4KTFKD52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELNPF2A#issuecomment-584774376>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCFAN5UXJJY4QUITEL43CLRCLS2NANCNFSM4KTFKD5Q> .

[spamatica]

Retried this now and maybe there was something wrong with the state of latency correction. It was off in the menu.
Trying now I can get the problem with latency correction but not without.
So as long as we don't recommend Latency correction this is not that big of an issue

[terminator356]

Ah I see. OK good (well not really).
Yeah I must get in there and return to the latency looping fixes.
It was complicated. I need to 'split' the audio pre-fetch into not just one but potentially
two accesses because the processing code needs to have access to
more than one buffer so that it can 'look ahead'.

[spamatica]

All in due time.
Since it's only with Latency correction enabled I'm thinking we don't let it stop a 3.1 release. So I will try to go ahead and make the 3.1 release asap.

[terminator356]

Yes and in my mind what 'saves' me for now and buys me some time
is that from past experience most users use looping with pure midi.
It's a bit unusual to use looping with waves...

[github-actions]

This issue is stale because it has been inactive for two years. Remove Stale label or write a comment, otherwise it will be closed in 30 days.

[terminator356]

The issue would still be there since I've not done any work in there to fix it yet.

[github-actions]

This issue is stale because it has been inactive for two years. Remove Stale label or write a comment, otherwise it will be closed in 30 days.