ProppFrexx ONAIR User-Forum

Sorry thought it was the same due to overlays I will open a new thread...

Yes that's what I exected.
But the problem is not in the Repare...
But in the part where it terminated, as explained above it seems it died unexpected.
So the full log around the complete overlay is of importance, as said.

I am not at the station now.
I 'll do the tests later tonight

And then we know, that this single call to the audio fails (now we know, that one of the 3 fails and got stuck!) - but still we do not know why!
And we will never really know, as the issue is, that a call does not return, but got stuck and is 'hanging' - and simply never returns!
And placing a log after each line of code isn't really a solution.

But what you might do is try to look at your Windows Event Log, if at around "20/12/2014 09:58:25" something (a warning/error/info) happened ?!

The windows event log does not have any error that time.
I run the latency test for about half an hour and here are the results: I haven't done any network test as I suppose that if there was an interruption in network, also my connection to the streaming server should break that time but it did not happen.
That's for now. I am going home. More tomorrow.

I can not say that (your internet streaming connection must be also dropping out) with respect to the network, as it might be local issue only - as said, I do not know - and probably I can never tell you this!
But as said, it can also be a hard disk issue or some bug/error in the network driver or the management of shared drives...that is impossible to say, as I do not know where in the stream creation call of the audio lib a certain call is 'hanging' and not 'returning'.

At least it looks, like you do not have an audio/driver issue.