Looking at your conf file - there have been some odd changes made compared to the standard WaveInput conf file and I cannot understand the rationale unless there are changed to the plugin as well.
Why are "IFR" and "IFRD" and "IFRB" used when the original only require "R" ? Was there a reason for this ? It seems to me like these conf file changes were done at randcom without understanding what is happening. For example in the conf file capabilities lines using "I" or "F" is not sensible since the plugin is setup to make "wavin:" look like a remote source so "R" is the only option. Similarly there is no need for the "D" option since * source is ecasound not a stream from LMS * the ecasound command has been hardwired to 44100 and destination is 44100. The "B" option is only relevant on the "MP3" stream as that is the only one where bit rate limitiing is effective. My advice would be to change your conf file ecasound command so that input comes from a test audio file of the same format as Shairplay instead of the pipe (it would also be advisable to seprately verify the ecasound command works ok with the file) . Then modify the conf file using the test file as a standard audio source until you have got the conf file working. Then change conf file back to using the named pipe as source. That way each component of the convert process will have been separately tested and you will only be changing one variable at a time when solving the problem. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=49584 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
