Github messages for voidlinux
 help / color / mirror / Atom feed
From: djenkins93 <djenkins93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] cli-visualizer not providing any audio/visual output (seems to hang when opened) 
Date: Fri, 17 Sep 2021 10:16:53 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32989@inbox.vuxu.org> (raw)

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

New issue by djenkins93 on void-packages repository

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

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.13.15_1 x86_64-musl AuthenticAMD/VM uptodate rFF
* package:  
  cli-visualizer-1.8_2

### Expected behavior
Should display visual representation of audio output based up which audio util I have setup on my system (i.e.: pulseaudio, alsa, pipwire etc.)

### Actual behavior
The program seems to potentially hang or is pulling audio from the wrong device. Something else I have also notliced, is that when running cli-visualizer with my web-browser, I completely loose audio almost as if cli-visualizer is interfferring with the output. However once I close cli-visualizer, the audio returns to my web-browser. 

### Steps to reproduce the behavior
(run cmd in terminal) 
cli-visualizer 

PS. I assumed that this could potentially be a misconfig issue on my end, but again I'm able to get audio from my web-browser and the repo seems to only supply  a binary executable (no extyra config files). Additionally, "cli-visualizer" seemed to be working fine with my system until I performed an update but this was unfortunately some time ago. 


             reply	other threads:[~2021-09-17  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  8:16 djenkins93 [this message]
2022-06-05  2:14 ` github-actions
2022-06-19  2:15 ` [ISSUE] [CLOSED] " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32989@inbox.vuxu.org \
    --to=djenkins93@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).