Hi,
On Thu, Aug 03, 2017 at 01:06:08PM +0430, Armin Ranjbar wrote:
> well, as far as i can the whole spicy process uses one core when
> streaming, any ideas how to debug this?
>
> ---
> Armin ranjbar
- Can you paste your qemu command line so we can know for sure you have
streaming enabled? e.g [0].
- Can you paste your client's debug log with --spice-debug?
e.g ./spicy --spice-debug ?
If you are using gstreamer, you should see a lot of the following:
(...)
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 391
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 387
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 387
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 390
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 386
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 389
(spicy:14506): GSpice-DEBUG: channel-display.c:1499 display-2:0: video latency: 389
(...)
[0] It should contain streaming-video...
-spice port=5900,addr=127.0.0.1,disable-ticketing,
image-compression=off,streaming-video=all,
seamless-migration=on
I've built my spice-gtk with --disable-builtin-mjpeg so it uses
GStreamer even with mjpeg streams.
Cheers,
toso
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel