From owner-dev-commits-src-all@freebsd.org Sun Oct 3 19:08:46 2021 Return-Path: Delivered-To: dev-commits-src-all@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 5EFE566D0D3; Sun, 3 Oct 2021 19:08:46 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4HMtg21gMlz3tMw; Sun, 3 Oct 2021 19:08:46 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 1A83D2600F2; Sun, 3 Oct 2021 21:08:38 +0200 (CEST) Subject: Re: git: 903873ce1560 - main - Implement and use new mixer(3) library for FreeBSD. To: Mateusz Piotrowski <0mp@FreeBSD.org>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Cc: Christos Margiolis References: <202109221803.18MI3gdA013391@gitrepo.freebsd.org> <3d6a23c3-ad2c-4c5b-849e-1ef12dbf8955@FreeBSD.org> From: Hans Petter Selasky Message-ID: <487fa0f2-d845-438f-a035-8b7ccba4285a@selasky.org> Date: Sun, 3 Oct 2021 21:08:27 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <3d6a23c3-ad2c-4c5b-849e-1ef12dbf8955@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HMtg21gMlz3tMw X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: dev-commits-src-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the src repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2021 19:08:46 -0000 On 10/3/21 6:03 PM, Mateusz Piotrowski wrote: > On 22/09/2021 20:03, Hans Petter Selasky wrote: >> The branch main has been updated by hselasky: >> >> URL: >> https://cgit.FreeBSD.org/src/commit/?id=903873ce15600fc02a0ea42cbf888cff232b411d >> >> >> commit 903873ce15600fc02a0ea42cbf888cff232b411d >> Author:     Hans Petter Selasky >> AuthorDate: 2021-09-22 13:42:51 +0000 >> Commit:     Hans Petter Selasky >> CommitDate: 2021-09-22 17:43:56 +0000 >> >>      Implement and use new mixer(3) library for FreeBSD. >>      Wiki article: >> https://wiki.freebsd.org/SummerOfCode2021Projects/SoundMixerImprovements >>      This project was part of Google Summer of Code 2021. > > This may be a bit late to discuss but the new mixer has a completely > different > set of options and command-line arguments. In addition to that, > the output of the command is different. > > Shouldn't we keep supporting the previous way of interacting with mixer? > I know that people are scripting mixer and its output in production > in order to control soundcards. Are there any good reasons to keep the new > mixer(8) as it is now while keeping the old name? Perhaps we could change > the name of the new mixer to, e.g., newmixer. Users are going to have to > rewrite their scripts for mixer(8) anyway for 14.0. > Hi Mateusz, It depends what level of compatibility you need. If you have a script parsing mixer output, then it needs to be binary compatible so to speak. That means some new features like "mute" won't work. It looks like all BSDs have diverged in the mixer area. NetBSD calls it mixerctl: https://man.netbsd.org/mixerctl.1 During the GSoc there was no requirement for binary compatibility for the mixer utility. Only in the kernel APIs are backwards compatible. Would it help to make a port, like "oldmixer", under "audio" ? Christos, feel free to chime in. --HPS