Use logging player.source set to INFO to see what command is being executed and then use "top" to see which process/executable is taking all the CPU.
There was similar problem about a year ago on Windows with socketwrapper and IIRC alac in that case "broken pipe" wasn't being handled properly. -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=52580 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
