Hi,
OK, so first implementation will work via --spice-disable-effects option. As far as I understand, this user-provided option flags should already be available at the agent, need to handle appropriate message as in Windows vdagent, correct?
Anyway, I still don't understand how we can control these
effects on Linux desktops correctly - supporting only Gnome and not
providing any means for other DEs to catch up seems to be bad design
(I'm using KDE, for example; and even supporting both Gnome&KDE
isn't solving this as there are a few more, fairly popular - Unity,
XFce...). Also how interaction with this Gnome settings should be
implemented? If via function call from some shared API, this adds on
vdagent dependency (probably undesired by any other DE users) - so usage
of dload() is expected?OK, so first implementation will work via --spice-disable-effects option. As far as I understand, this user-provided option flags should already be available at the agent, need to handle appropriate message as in Windows vdagent, correct?
On Mon, Jun 24, 2013 at 9:41 PM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
Hi,Yes, and when we decide to render everything on the server side, then having shared memory becomes really
On 06/24/2013 05:32 PM, Yonit Halperin wrote:
Hi,
For the purpose of disabling guest desktop effects, we already have a spice-gtk option which we use for Windows guests, and can be used for Linux guests as well. The Linux agent should support VD_AGENT_DISPLAY_CONFIG for this.
However, for local usage, we would also like to disable bitmap/audio compression, and video compression on the server side (I believe there is already an opened bug for decoupling lipsync from video compression). In addition, when using spice for local usage, you also have the overhead of redundant rendering on both server side (when required), and client side. We also need to consider rendering everything on the server side.
useful... :)Hans
IMHO, as a first stage, we can start by adding an explicit option to spice-gtk for "local", or more specific options for disabling compression (e.g., --disable-compression=audio/video/bitmaps/all). We can then send the settings to the server upon connection. As a second stage, I would continue with an automatic detection, something like hans suggested.
Regards,
--
Best regards,
Fedor
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel