<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> On 05/12/2010 03:48 AM, Antoine Martin wrote: <blockquote cite="mid:4BE9C298.6040905@nagafix.co.uk" type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> On 05/11/2010 11:29 PM, Tanu Kaskinen wrote: <blockquote cite="mid:1273595379.28655.1433.camel@jarl" type="cite"> <pre wrap="">On Tue, 2010-05-11 at 12:21 +0700, Antoine Martin wrote: </pre> <blockquote type="cite"> <pre wrap="">Add-to-wishlist: ability to use codecs here would be nice. I doesn't look like I can use ladspa plugins over the tunnel, or can I? If so, how? 1.4Mbit/s is a little high when most modern cpus can compress audio to 192Kbit/s on the fly without consuming any significant amount of CPU. </pre> </blockquote> <pre wrap="">The lack of compression is a known bug :) AFAIK nobody is currently working on the feature, though. </pre> </blockquote> That's a shame. Especially since it consumes the whole bandwidth allocation whether actual sound is being played or not! Ouch. Well, at least when using an ssh tunnel with CompressionLevel=9 you can reduce that down to around 220Kbit/s when idle. (from 1.4Mbit/s) I haven't tried with single-channel 22KHz yet. </blockquote> Correction, that's ~56Kbit/s idle. (~25 times less, decent saving) (and no noticeable change when playing real audio) <blockquote cite="mid:4BE9C298.6040905@nagafix.co.uk" type="cite"> The SSH transport is not the best place to be doing this sort of compression! Aren't there any open-source codec frameworks that could easily be plugged into the tcp transport? </blockquote> [snip] </body> </html>