[winswitch] minimum bandwidth where xpra still stays usable?

Antoine Martin antoine at nagafix.co.uk
Thu Jul 11 12:02:53 BST 2013

On 11/07/13 17:59, Timo Juhani Lindfors wrote:
> Hi,
> Antoine Martin <antoine at nagafix.co.uk> writes:
>> Which encoding were you testing?
> x264
This should have worked fine, certainly better than jpeg!

>> If it was a lossy one, have you tried increasing the auto-refresh delay
>> so lossless frames don't fire too often?
> Thanks for the advice. It seems that
> xpra attach --encoding jpeg --quality 5 --auto-refresh-delay=1000 ssh:example.org:7
> is usable even after I have limited the bandwidth on the server using
> tc qdisc add dev eth0 root tbf rate 512kbit latency 20ms burst 60kbit
>> How so? jpeg encoding is still supported and so is the quality setting.
>> That said, jpeg encoding is terrible, you should be using x264
>> instead.
> Even with
> xpra attach --encoding jpeg --quality 5 --auto-refresh-delay=1000 ssh:example.org:7
> I see only very minimal artifacts, I'm sure I used to see much worse
> quality in the past. Is it maybe ignoring --quality 5 and assuming
> --quality 70 or something?
That's probably the auto-refresh kicking in before you realize.
jpeg at quality=5 is unusable otherwise


> -Timo
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users

More information about the shifter-users mailing list