epoch1970 wrote: > Just looking at a debug trace, I see the player doesn't say exactly the > same things when it connects to a local or to a remote server. I do not > use the "direct file access" feature because I want to sync players. The > Local Player plugin is installed, but it is inactive. This seems > specific to the conversation between SqueezeLite and the local server:> Code: -------------------- > > > [23:41:51.410880] slimproto:705 local player > > [23:19:50.958386] codec_open:147 codec open: 'f' > [23:19:50.958609] stream_file:310 opening local file: /var/data/audio/Audiofiles/00-iTunesStore_FLAC/dEUS/The Ideal Crash/09 Let's See Who Goes Down First.flac > -------------------- > > > Does this mean SqueezeLite is likely to stress the local hard drive by > itself ? > (I'd rather not. I experience uneven HDD throughput, causing audio > artefacts. I have difficulties pinpointing the cause.) > > In the same line of thought, could someone (Triode I guess) describe > what the -b XXX:XXX option does ? > I see rebuffering is inevitable on my platform under some conditions. > What I'd like to obtain is consistent behavior between an SB3 and SL, > so that they roughly stop at the same point to rebuffer, and restart > more or less in sync. Can the -b option help here ?
You should only see the above debug with the direct file access option set - can you confirm that this is actually set at the time it occurs? When it is used it won't me more stress on the hard disk as squeezelite will read from the disk rather than LMS, so it avoids carrying the audio data into LMS and then through a socket to squeezelite. Instead squeezelite reads it direct from the disk. ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=97046
_______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
