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?
There is a virus scanner on the machine running in learning mode (Vipre AV) but I have most of the Intrusion Protection/network filtering off. I also had a second feed running to a remote PC on the same network segment and it did not show the error at all.
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.
No problem - saw the negative figures and wondered if it was recovery or trying to display some info about the event.
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?
RX was fine = I was in the room listening to the audio output and did not hear a gap in it that I heard or it drew my attention to. I only saw the event in the window some 10mins later. I am on a cabled network. Up until recently I was running this on the loopback interface. I recently (2-3 days ago) moved it to the network interface (to test) as well as add two more outputs on the same network segment. Both NICs set to Automatic.