From owner-freebsd-multimedia@freebsd.org Fri Dec 4 13:45:25 2020 Return-Path: Delivered-To: freebsd-multimedia@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 160234A1086 for ; Fri, 4 Dec 2020 13:45:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CnYqm72ZHz4lFV for ; Fri, 4 Dec 2020 13:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id EFE1647FFEC; Fri, 4 Dec 2020 13:45:24 +0000 (UTC) Delivered-To: multimedia@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EE9194A1085 for ; Fri, 4 Dec 2020 13:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CnYqm68Llz4lFT for ; Fri, 4 Dec 2020 13:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B814E49B1 for ; Fri, 4 Dec 2020 13:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0B4DjOeS029643 for ; Fri, 4 Dec 2020 13:45:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0B4DjOhI029642 for multimedia@FreeBSD.org; Fri, 4 Dec 2020 13:45:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 251125] audio/jack: update to jack2 or add new port audio/jack2 Date: Fri, 04 Dec 2020 13:45:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: dev@submerge.ch X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: multimedia@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2020 13:45:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251125 --- Comment #45 from Florian Walpen --- (In reply to Hans Petter Selasky from comment #43) Thanks for the hint. Reading the fragment size is not a problem, we do that, but requesting one that is e.g. a multiple of 512 * 4 * 18. If you know of = any way to do this, please tell me. If I follow the code path from the IOCTLs to chn_resizebuf(...) in sys/dev/sound/pcm/channel.c: > /* > * The application has requested their own blksz/blkcnt. > * Just obey with it, and let them toast alone. We can > * clamp it to the nearest latency profile, but that would > * defeat the purpose of having custom control. The least > * we can do is round it to the nearest ^2 and align it. > */ And the code around it looks accordingly, which is why I see no way to requ= est a fragment size that matches the period cycle from jack. Not if the channel count or the sample size are non-2^N. Even if jack cannot obtain a matching fragment size, it's still possible to write and read arbitrary chunks, e.g. 512 * 4 * 18 bytes. That's what my pa= tch is for. In that case my question is: How does the fragment size affect performance and timing tolerance? Are single fragments only processed when = they are full, or more continuously like the scatter / gather buffers in read(..= .) and write(...)? --=20 You are receiving this mail because: You are the assignee for the bug.=