posnos wrote: > Thanks to all for the replies. > > Yes I understand that a track doesnt need to be completely in memory, > the memory buffer pages will follow a LIFO scheme where stale pages are > reused. > It was just interesting that various well known contributors on some > non-slimdevices forums suggested such a wide disparity in squeezelite > buffer size. > > I can see that a few 100MB would be ok but to me 2GB per buffer (4GB in > total between the I/O buffers) would result in a large amount of unused > and/or stale memory that squeezelite would have to manage. The larger > the buffer the more the management overhead. > >
I would add to what Michael said that some people foolishly think that sound quality is better if the file is fully in RAM instead of being streamed piece by piece while it's being played. Not only is it a non-sense but also with squeezelite, this might happen for the 1st track, but as soon as the 1st track is fully decoded, then the 2nd one will be streamed while the 1st is beeing played (and so on). So don't overthink things that do not matter anyway :) LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5 ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=111144 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
