2018-07-21 07:44:28.438 error: Not enough bytes consumed. ts 1068628685, bytesRead 1509, available 1457
2018-07-21 07:44:30.854 warning: Buffer empty: had to jump blocks (from 1 to 0). Expected TS 1068628685, moved to 1069089725
2018-07-21 07:44:30.854 warning: Timestamp unexpected: 1069089725 != 1068628685
2018-07-21 07:44:30.854 warning: Received unexpected timestamp 1069089725 in modulator (expected 1068628685), resetting
Did not hear the outcome of the loss but the packet speed after recovery goes negative - RX was fine so assume cosmetic more than anything??
Hm, that's a weird one. Apparently the contents of one packet arrived with a change, and then 2.4 seconds of data were gone. Which is very odd especially on the same pc - could something like a virus scanner have interfered maybe?
The packet speed is no problem - it's supposed to go negative after an issue until we have a reliable number again. Those speeds actually shouldn't be logged - but we were extensively testing those (they need to be accurate upto 6 digits), so we added the logging recently. We'll remove it before releasing this version.
What do you mean by RX was fine? That seems to mean that nothing went wrong but you also said you didn't hear it? I *think* it played 2.4 seconds of silence. I'm just wondering what could have killed these packets on a loopback connection.
Just to make sure: If you say you used the local address of the machine, I assume you mean its actual address, not 127.0.0.1 right? I think the packets still go through your actual network in that case. Is it on a cabled network or on Wifi?