Hi guys, This is a difficult problem. The HTTP protocol has no mechanism for synchronizing streams. The client may be sending data too fast compared to the rate at which the data is played back by liquidsoap. This is the likely explanation for what you're experiencing.
Since liquidsoap uses the same synchronization as liquidsoap, there may be less problems when connecting two liquidsoaps over HTTP, but it's not guaranteed: it still depends on the internal clocks of the involved machines. In fact, I have this kind of problem with my own station which runs liquidsoap on a remote low-power server with a pretty bad clock. I don't know of any easy solution for the moment. Two ways of improving the situation, though, are (1) making the HTTP input drive the liquidsoap clock, which only helps if the clock is not already driven by the soundcard or such, or (2) create a device for synchronizing clocks between two liquidsoap instances, if possible re-using technology to that effect, but this wouldn't help with clients not using that technology. If anybody is interested in studying/implementing either solution, I'd be happy to help. Cheers, -- David ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
