Warning that pops up a lot

[morderkaine1]

Hi, Just a warning that pops up a lot. Doesn't really appear to affect how it works, though maybe its related to cut outs.

[Dissonance:Playback] Player Playback: Playback desync (26033ms) beyond recoverable threshold; resetting stream to current time
UnityEngine.Debug:LogWarning(Object)
Dissonance.LogMessage:Log() (at Assets/Plugins/Dissonance/Core/Log.cs:91)
Dissonance.Logs:WriteMultithreadedLogs() (at Assets/Plugins/Dissonance/Core/Log.cs:105)
Dissonance.DissonanceComms:Update() (at Assets/Plugins/Dissonance/DissonanceComms.cs:491)

[martindevans]

Hi morderkaine1,

That's definitely a bug which will be causing your audio to be badly delayed and then eventually some audio will be lost (every time this message pops up). This is essentially the same issue you're seeing in #29 (they're different ways of detecting the same problem in different ways).

We've had a few reports of issues like this but haven't managed to reproduce it yet. Could you give us some more details on your setup please - On your DissonanceComms component click Diagnostic Settings and increase the logging settings:

• Core: Trace
• Recording: Debug
• Network: Trace
• Playback: Debug

Then send a complete log from both the sender and the receiver when this happens.

[antoniohof]

[EDITED]
Im actually getting this error:

06-09 16:19:07.359 28082-28105/? W/Unity: [Dissonance:Playback] EncodedAudioBuffer: Error: Encoded audio heap is getting very large (46 items)! This is probably a bug in Dissonance, we're sorry! Please report the bug on the issue tracker "https://github.com/Placeholder-Software/Dissonance/issues". You could also seek help on the community at "http://placeholder-software.co.uk/dissonance/community" to get help for a temporary workaround. Error ID: 59EE0102-FF75-467A-A50D-00BF670E9B8C

I'm getting this too using Android, IOS and Photon. With the default scene over wifi network.
It seems to increase delay up to a point that it's not usable.

After a while it resyncs:

06-09 16:19:07.370 28082-28105/? W/Unity: [Dissonance:Playback] Player Playback: Playback desync (1151ms) beyond recoverable threshold; resetting stream to current time

[martindevans]

Hi antoniohof, Could you send me the same log I requested from moderkaine1?

[antoniohof]

This seems to be a problem on the Skip function on SamplePlaybackComponent class.
It also causes some glitching on the audio until it finally resyncs after passing through function several times. Soon after that it also causes the "EncodedAudioBuffer: Error: Encoded audio heap is getting very large (41 items)! ".

I commented the main part of the skip function, returning true when it was desynced over 1 sec and false when it is synced and this fixes those errors and the glitch.
But I don't know what implications this might have to the stability of the code.

[martindevans]

I guess you tried that fix using Dissonance 1.0.10? Dissonance 1.1.0 just went live on the store last night and includes some fixes to the Skip method (so if it is invoked, it only runs once, previously it skipped the wrong amount and had to skip several times to get back in sync).

However Skip should never happen - the whole pipeline should always stay in sync within a few 10s of milliseconds. Skip is basically Dissonance giving up, throwing away a load of audio (deliberately causing a horrible audio glitch) all to get back into sync.

So the real question is what is causing the system to get so terribly out of sync in the first place? Could you send me those detailed logs I mentioned above so I can look further into the issue?

[martindevans]

We've had 2 new versions on the store since this was last reported so I'll close this issue. Please don't hesitate to re-open it if you encounter the errors again.

[TobiasWehrum]

Hey @martindevans !

We got the "Error: Encoded audio heap is getting very large (74 items)! This is probably a bug in Dissonance, we're sorry! [...]" warning in Dissonance 3.0.0 - and while trying to reproduce it, we discovered that it happens for us when

• client A (in the editor) does something with the editor, e.g. opening the Edit menu
• client B (also in the editor, but no idea if that matters) speaks at the same time.

Client A gets the warning, and even after closing the Edit menu the warning continues to be thrown.