Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bars completely maxxed out without touching config #447

Closed
ChadFacts opened this issue Apr 16, 2022 · 10 comments
Closed

Bars completely maxxed out without touching config #447

ChadFacts opened this issue Apr 16, 2022 · 10 comments

Comments

@ChadFacts
Copy link

When/where was the bug introduced?

  • Are you using cava from a package repository, like AUR?
    I followed the from source installation instructions

Describe the bug
The bars are permanently maxed out regardless of sensitivity

To Reproduce
Steps to reproduce the behavior:

  1. install
  2. run

Expected behavior
I expected bars the same as I see within videos I saw on YT and on the README.md

Screenshots
image
image

Desktop (please complete the following information):

  • OS: Archcraft
  • Version 5.17.3-arch1-1

Terminal emulator

  • Kitty
  • 0.25.0
  • Alacritty
  • 0.10.1
  • (Tried both, same results on both. Screenshots from kitty.)

Additional context
I've tried adjusting sensitivity both in config and via keybind. I've set sensitivity in the config to 1, 10, 100, 150, 200. No change.

@karlstav
Copy link
Owner

Hi @ChadFacts

Does it make any difference if you disable autosens? Also try adjusting sensitivity after disabling autosens.

@ChadFacts
Copy link
Author

Autosens was already disabled in the config file and I also tried it with autosens enabled

@karlstav
Copy link
Owner

I can see that there is some movement in the top of those screenshots. Where autosens disabled when those where taken? Does it make a difference when enabling or disabling autosens?

@ChadFacts
Copy link
Author

Yeah that's the only movement that happens, just a little bit at the top but in most things it seems to be over the limit. With it enabled it has the same result. It was disabled in the screenshots, but I tried it again just to see so I uncommented autosens and made sure it was = 1. It still performed the same. I also tried changing it to 0, still same results. I made sure to restart cava after every change in config.

@karlstav
Copy link
Owner

hmm i am having a hard time trying to reproduce. I did a lot of changes in 0.8.0 can you check out the 0.7.5 tag and see it you have the same issue there? just do:

git checkout 0.7.5
make clean
sudo make uninstall
make
sudo make install

@vaskark
Copy link

vaskark commented Apr 16, 2022

This is happening for me, too. Latest git on Ubuntu 21.10.
0.7.5 works fine.

@karlstav
Copy link
Owner

found the issue, my bad!

should be fixed now.

@ionenwks
Copy link

Thanks that fixed it for me, ran into this too and was about to bisect but guess no need anymore 👍

@vaskark
Copy link

vaskark commented Apr 17, 2022

Fixed. Many thanks. And thanks for all your effort.

@ChadFacts
Copy link
Author

Fixed, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants