From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id CF4E01FF0EC for ; Sat, 24 Oct 2026 12:16:15 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 0E722209C2; Sat, 24 Oct 2026 12:16:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=taktcycles.com; s=takt1; t=1792836657; bh=aRfkiVh51NaZZDAEXliYslVOyJztAWcbZ0br+0CTf54=; h=From:Reply-To:To:Cc:Subject:In-Reply-To:References:Date:From; b=NYFS+kQAxMAKPZR5+VMDXLm9n6u8pWXlWACGTboRu0mmWZQZuqbqr42t+XsOn64Po 1+GiuV0pYKrYnPx1wL7S99NdXyXIhrMrUgFhos3BstreeWNFKJ/+1CDMPUCaaJ/+3v pZLcSlbipXzKvqXlTimT4AnpbdYNxsuj8trGBKN/18F8Vx11sSKKp6HbSzvBkb4MVW 47mNLFEnyb4ajAGMrJ2lGyi6SRs6p0LT4eEaeWoBwwTcWxl8rS1zZ0OjCPYul6ukfy mSzl9O7pQq1RvPd/mE4vzZJEcLTWo2bG/zKKu9Ms56goBI/t7atecwDwZWicjQB9tE M06EG1AIGlJDg== From: Dmitry R To: pve-devel@lists.proxmox.com Subject: Re: [RFC] WebRTC console for VMs via QEMU's D-Bus display In-Reply-To: References: Date: Sat, 24 Oct 2026 10:10:34 +0000 Message-ID: <179283663410.2345286.10377571210474311317.qsm-stock4.3-update@taktcycles.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 1 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FORGED_REPLYTO 1 Freemail in Reply-To, but not From FREEMAIL_REPLYTO_END_DIGIT 0.25 Reply-To freemail username ends in digit FROM_FMBLA_NEWDOM28 0.799 From domain was registered in last 14-28 days SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EE7OSTHPWGOTHILBJC6GKIAU4EQKFFJV X-Message-ID-Hash: EE7OSTHPWGOTHILBJC6GKIAU4EQKFFJV X-MailFrom: rdmitry@taktcycles.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Reply-To: Dmitry R List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hi Alexandre, hi all, A follow-up to the standalone/APT update: stock4.3 now includes the reference-detail fix and a completed-action input mode for both VM and LXC. Genuine bitrate changes could still reset hardware rate control and replace unchanged reference detail, producing changing sharpness or horizontal bands. The worker now keeps the encoder settings and budgets raw pictures before encoding. Under constraint it reduces motion cadence; media timestamps preserve playback time. An abrupt capacity drop can still cause recovery pauses. NVENC H.264/HEVC and browser H.264 checks are included; Intel/AMD hardware and interaction latency were not remeasured for this change. For input, reliable delivery alone was insufficient: a delayed key release could cross the guest's native repeat threshold. Read-only QEMU/guest observations found complete press/release pairs but stretched holds. Exact typing is now the default. Each press or actual client repeat is one complete key action with its modifiers, executed locally by the worker. The first character is immediate. Physical holds/Raw remain available for applications which require a key to stay down. In Firefox with a real Sway/Qt LXC desktop, a 900-ms control-delivery gap gave 8 characters from one short source press in the old mode and 1 with exact typing. A heartbeat-only guard still gave 5 after a recent confirmation; exact typing gave 1. Six confirmed source events produced six characters. Stock4.3 applies the same approach to short mouse/trackpad/touch clicks, including their coordinates. A short click is sent on release; movement of 4 CSS pixels or a 250-ms hold starts a drag/hold. Drag motion and release stay ordered through acknowledgement, with a per-viewer coordinate filter shared by both channels. Normal idle motion retains the fast pointer path. Fractional trackpad deltas and horizontal scrolling are supported. The same injected gap gave two activations of a Qt auto-repeat button with physical edges plus watchdog, versus one with the complete click. Double click, right click, holds, dragging and two-axis scroll passed. These are browser-event tests, not physical trackpad or end-to-end latency benchmarks. Native double-click timing can still change with delivery jitter. A 200-ms confirmation timeout can end a drag early; stale snapshots never re-press it. Source, five matching debs, guides and detailed qualification: https://github.com/rdmitry0911/qsm-rd/releases/tag/v0.4.0-qsm-direct-20261024-stock4.3 Signed APT repository: https://rdmitry0911.github.io/qsm-rd/ Update installed QSM profiles together, then reload PVE with cache bypass and reopen consoles. No guest reboot or agent update is needed. This release has 73 bridge tests, 22 CTest gates and worker/fake-QEMU E2E coverage. The standalone release remains separate from the native shared-bus/API/UI proposal. It does not change the proposed upstream interface or establish maintainer agreement. Feedback on bus ownership/lifetime, configuration and the service/API boundary would still be welcome. Thanks, Dmitry