Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] separate package for tools in pulseaudio which are useful for pipewire
Date: Thu, 29 Apr 2021 17:24:02 +0200	[thread overview]
Message-ID: <20210429152402.oCWJ9R4js9WgFuZLzRnP26ON9FaJCVHKjQ3OtaYQkoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29576@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]

Closed issue by gt7-void on void-packages repository

https://github.com/void-linux/void-packages/issues/29576

Description:
For instance: my setup depends on `pactl` which works with `pipewire`. I couldn't find another tool which can replace some of the functionality of `pactl` (e.g. I use `pactl info`, `pactl list short sinks`, `pactl set-default-sink`, `pactl list short sink-inputs`, `pactl move sink-input`, etc. I guess some or all of those can be replaced combining `pw-dump`, `jq` and `pw-cli`, but it's a chore)

Installing pulseaudio is a pain because it's sometimes difficult to avoid having it autolaunch, etc.

As an example, debian has a `pulseaudio-utils` package (https://packages.debian.org/sid/pulseaudio-utils) which contains:
```
  paplay - Playback a WAV file via a PulseAudio sink.
  pacat - Cat raw audio data to a PulseAudio sink.
  parec - Cat raw audio data from a PulseAudio source.
  pacmd - Connect to PulseAudio's built-in command line control interface.
  pactl - Send a control command to a PulseAudio server.
  padsp - /dev/dsp wrapper to transparently support OSS applications.
  pax11publish - Store/retrieve PulseAudio default server/sink/source
                 settings in the X11 root window.
```

I would be content with `pactl`, the others (`paplay`, `pacat`, `parec`) seem to have equivalent included with pipewire (`pw-play`, `pw-cat`, `pw-record`). I don't know about `padsp` or what `pax11publish` is supposed to do. I know `pacmd` does _not_ work with `pipewire`.


      parent reply	other threads:[~2021-04-29 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  0:12 [ISSUE] " gt7-void
2021-03-19 14:51 ` FollieHiyuki
2021-03-19 16:57 ` gt7-void
2021-03-19 17:14 ` ericonr
2021-03-19 21:29 ` gt7-void
2021-03-29 22:18 ` CameronNemo
2021-04-09 15:55 ` st3r4g
2021-04-26  6:13 ` noarchwastaken
2021-04-26  9:24 ` st3r4g
2021-04-29 15:24 ` ericonr [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210429152402.oCWJ9R4js9WgFuZLzRnP26ON9FaJCVHKjQ3OtaYQkoY@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).