@rpedde wrote:
I get what you are doing here, but the ssc_codectypes is to tell the server what the ssc_script transcoder will transcode. The codec types set in the plugins are to tell the server what conversions it *can* do, and the server should choose to use them based on whether or not it thinks that the client should be transcoded to (plugin_ssc_should_transcode).
Okay. Maybe the option should be renamed, and/or the help for it in the sample configuration file amended. I too misunderstood the purpose of the option. The current one doesn’t note that ssc_codectypes is only relevant to ssc-script. Perhaps there should be a special config section for plugin configuration?
Probably could make a “never_transcode” configure option or something.
I like this.
That might be the best. Still going to have problems with mixed clients, though. No real way to avoid that, I don’t think.
Yes, I think the submitter of the Debian bug ultimately wanted to do (he wanted to stream to amarok.)
BTW — you are the debian maintainer? Anything I can do to help? I’ve taken the debian folder out of the source tarball, which I’ve been meaning to do for a long time.
Yup. I could’ve sworn I sent you an email about it, but it must have gotten lost in the sea of bits..
I assume you stripped the mdns stuff out? If macosforge would come back up, I’d update the mdns to the bsd licenced stuff, but it’s been down for something like the last month.
I need to get a native avahi module, too.
Yes. The debian build uses avahi’s howl compatibility layer.
Thanks for your detailed reply 🙂