(19-12-2015 22:01)simoncn Wrote: (19-12-2015 21:12)Peregrino Wrote: Here is the log showing me:
1. Selecting and successfully playing a BBC stream (without transcoding).
2. Adding aac:wav to stream.transcode.
3. Rescanning/starting MinimServer.
4. Attempting (and failing) to play the same stream.
5. Deleting aac:wav from stream.transcode.
6. Rescanning/starting MinimServer.
7. Selecting and successfully playing the same stream again (without transcoding).
There is always a fairly long delay when I first select one of these streams. If that stream plays and I then select another stream, the second stream starts to play without real delay.
This log only shows steps 6 and 7. This is because the volume of log data has caused the log buffer to overflow.
From the log (step 7), I see that you have a 16-second delay even in the case where streaming is successful (not transcoding), so this delay doesn't seem to be directly related to the problem you are having. However, this delay should not be happening and it would be good to understand what is causing it. Are you located in the UK? Do you have any firewall or antivirus software running that might be interfering with network communication?
I don't have any more ideas about what could be causing the problem. I hope the renderer manufacturer will be able to help identify the cause.
Thanks again. Yes I'm in the UK. There shouldn't be anything interfering with communication on that network, but I'll have a look and check. I've written to exaSound about the problem.