[X2Go-User] Nightly Build Badly Broke

[Robert Dinse]

      No it was me, in .profile, just was looking at wrong account.

      Right now setting it back to jpeg-16m which I formerly had working well
isn't working good, but also Youtube isn't even loading video properly, some
network issue but it doesn't seem to be between me and my co-lo but rather
somewhere between co-lo and youtube, yet I can ping google's name servers
and get just a few ms time.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 5 Feb 2016, Mihai Moldovan wrote:

> Date: Fri, 5 Feb 2016 02:20:09 +0100
> From: Mihai Moldovan <ionic at ionic.de>
> To: Robert Dinse <nanook at eskimo.com>
> Cc: "x2go-user at lists.x2go.org" <x2go-user at lists.x2go.org>
> Subject: Re: [X2Go-User] Nightly Build Badly Broke
> 
> On 05.02.2016 02:03 AM, Robert Dinse wrote:
>> I was logged into the wrong account.  Found it, got it working,
>
> Please tell me where. :)
>
> I want to know whether the default files Ubuntu ship are broken or that's
> something you added not knowing better.
>
> If it's the former, I'll need to make a downstream bug report. In the latter
> case, change that to "tty -s && mesg ..."
>
>
>> but tried adaptive with 7 worked horribly for me, 1080p stuttered horridly
>> even on a small window and a big window was 2-3 frames per second.  But
>> something appears terribly wrong with my network connection right now,
>> youtube is buffering forever. So need to troubleshoot that before I can make
>> any good comparisons.
>
> Adaptive isn't an all-new option, it's been around in NX for a long time, X2Go
> Client just never supported it. It seems to be defaulting to JPEG, with a
> fallback to lossless encoding (PNG, maybe?) if there are at most 10 unique pixel
> values in the image.
>
> I'd estimate it to have similar behavior to JPEG, especially for videos (after
> all the video screen is one big image and it's very unlikely to have only 10
> distinct pixel values.)
>
>
>
> Mihai
>
>