Thanks for all those suggestions. So it seems like extending the level of buffering (somehow) is not an option? (short of SB3 purchase of course). That's good to know, I won't pursue that avenue any more.
Probably my next move is to try MySQL (I run this on my machine anyway for other applications). Whether it gets rid of the gap I guess will all depend on whether or not the code blocks when it submits the SQL query to the server (hopefully it's async/non-blocking!), and/or, how long it takes the server to process the query (relative to SQLLite). Failing that, I guess I will switch to a high bitrate MP3 as you suggested, at least until the search components are separated. Regarding comment #5, about tweaking the OS, I have already spent a little time optimizing this already. There is a write-up here: http://forums.slimdevices.com/showthread.php?t=20865 Unfortunately, despite these scheduler tweaks, I could not get rid of the droupouts resulting from search queries. Cheers, Nico -- nico ------------------------------------------------------------------------ nico's Profile: http://forums.slimdevices.com/member.php?userid=672 View this thread: http://forums.slimdevices.com/showthread.php?t=20863 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
