just;205781 Wrote: > How much latencies did ou get with this "chaining" ? > > I experimented some pipe works, using wavin2cmd piped to a remote > mplayer on a Linux box with PLink, and I get something around one > second latency. > > I set the buffer of wavin2cmd to 8192, the number of buffers to 2, used > the -nocache option of the remote mplayer, simple DES encryption and > compression enabled for PLink. > > It should be great if the latency could be as less than 300ms !
Cool! I'm glad to hear the pipes are working for you. The settings you've chosen for wavin2cmd provide about 370ms at 44.1kHz, so the additional 630ms is likely the result of network buffering on each end, the encryption/conversion buffering, and the linux machine's audio output driver latency. To get 300ms through-latency, you'll need to minimize the buffering wherever you can, and not use encryption/compression, since these add additional buffering and can use processor cycles needed for minimum latency driver performance (this goes up inversely proportional to the buffer size). If you need compression to minimize network traffic, you could try the flac codec. -- pbjbryan ------------------------------------------------------------------------ pbjbryan's Profile: http://forums.slimdevices.com/member.php?userid=3034 View this thread: http://forums.slimdevices.com/showthread.php?t=35718 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
