On Monday 25 June 2012 23:26:50 Chris Knadle wrote: > It seems unusual to CC ftpmaster in a bug report, but keeping the CC as > this is a reply to one that went there.
I won't, there are people you definitely don't want to be on the bad side of ;-) > On Sunday, June 24, 2012 21:36:28, Michael Schmitt wrote: > A logical thing to try from here, if you want to give this a shot, would be > to attempt to build the current upstream version from source and see if > the current version of CELT that it includes will work with older versions > of mumble-server, many of which are public. Mumble 1.2 will by default always only ship up to two versions of CELT: * 0.7.1 as a baseline, which is supposed to be supported by all clients and servers, and * a second, more recent version (for Mumble 1.2.4, that's 0.11, and that's unlikely to change since there won't be any further releases). Those two versions are incompatible, that's why the universally supported baseline is there. > If you manage to get it to build and run, in the configuration select > "Advanced" on the bottom left of the configure window, then in the "Audio > Output" section under "Loopback Test", try the "server" setting and see if > you can hear yourself through the server. > > This would specifically be helpful in verifying firsthand if the newer > versions of CELT that ship with upstream Mumble will work with older > versions of mumble-server. The client tells the server which versions it supports. If it doesn't admit to supporting 0.7.1, the server will effectively assume that it does anyway, to retain a stable codec negotiation and to keep misbehaving clients from ruining things for everyone. That mechanism is supported by all 1.2 server versions (plus or minus a few details, but if you're on >= 1.2.3, you should be golden; using 1.2.2 as a server, especially without a few patches, may not give you the stable operation you'd hope for). In a further step, the server makes sure to negotiate a codec that's supported by all clients "within listening range". To my knowledge, that mechanism will work with all server versions that are not a stupid thing to use. The only thing new to the party is Opus, which requires further protocol support on the server side. So effectively, as long as your client advertises only codecs it really supports and has the baseline codec, server echo will work, as will communication with other people. > > In general, I had a few words with some mumble devs on IRC a few days > > back. Common thinking there was, removing celt is not a wise option, no > > real security exploits known yet, mumble will support celt for the > > foreseeable future (1 - 2 years). > > Do you know if CELT still the default codec? For the 1.2 series, it's supposed to be. Opus is going to be supported, it will be used if all clients support it, and there are knobs in place to make a server prefer it even at the disadvantage of older clients, but the baseline codec will be assumed for a long time to come. Hope that clears things up a bit, Nicos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
