This morning my SBG and SB2 were unresponsive - the time on the SB2 was static. I went to the server machine and I could see that I had a Windows Data Execution Prevention message for Lame. This must have been blocking the SlimServer code in such a way that the squeezeboxes didn't report server connection errors.
I killed this and tried streaming flac->mp3 to my SBG again, which instantly caused the DEP message again. Yesterday I changed my windows settings for DEP to "Turn on DEP for all programs and services except those I select", and only had "windows.exe" selected as a test to try to resolve another unrelated issue with my system. I switched this back to the usual "Turn on DEP for essential Windows programs and services only" and rebooted. I still got DEP messages for Lame though. This was strange, as I have been using Lame with SlimServer for well over a year without problems. So I thought I'd reinstall Lame. I was previously using version Lame3.96Final. I went to sourceforge and found there is a newer version (lame3.97b2), so I installed that one (copied lame.exe and lame_enc.dll to C:\Windows). I noticed that the file sizes for the new version were substantially smaller. The problem has now gone away (although I did have a few stutters in playback that I didn't used to get - but that might not be down to Lame). What could have happened to Lame to suddenly cause the problem I've been seeing? What is the best version of Lame to use with SlimServer? I read the following (from http://www.free-codecs.com/download/Lame_Encoder.htm): There is a bug in LAME MP3 Encoder 3.96 Final version that can cause skipping. We recommend you to download LAME MP3 Encoder 3.96.1 Stable or LAME MP3 Encoder 3.97 beta There is also a 3.98 alpha version. Phil _______________________________________________ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
