DJanGo wrote: 
> lms is using udp for the audiostreams and udp is a protocol without
> errorhandling.
> So a minor hickup in the ethernet/network cant do this..

This is wrong - audio streaming uses http over TCP so all the individual
bytes of data that are sent by LMS will be received correctly by the
player.

However The HTTP stream has no byte count for the file so if the HTTP
stream is truncated (e.g. due to network error) the player cannot tell
the difference between truncated and normal terminated so  the player
will ask LMS for the next file so you could get truncation.

Truncation can also occur if there is a problem with the audio playing
interface (e.g. an example in a softplayer API would be ALSA) reports
that all the audio has been sent out but it hasn't and since LMS
overlaps audio stream - the player initiates a new playback resetting
the audio interface.

To isolate this problem I suggest first determine if the problem is 
1. Player specific (if using a software player try identical player on
differ hw and/or different player setup on same h/w) 
2. 192/24 specific.


------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=105601

_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter

Reply via email to