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

Cava configuration issues with konsole #194

Closed
Stephr1 opened this issue Jan 15, 2018 · 12 comments
Closed

Cava configuration issues with konsole #194

Stephr1 opened this issue Jan 15, 2018 · 12 comments

Comments

@Stephr1
Copy link

Stephr1 commented Jan 15, 2018

I am running Fedora 27 with kde 5 and have finally been able to put cava in my background. I have only been able to make transparency and desktop configurations work with konsole, however now cava only creates brick like bars and gradiant as shown:

screenshot

It works normally in gnome-terminal on the right, even though the cava configurations are the same.

This happened before when the user define gradients were not real colour codes, but when gradient is disabled the bars are still brick shaped.

Any ideas? Thanks.

@karlstav
Copy link
Owner

If i remember correctly konsole doesn't support chaining the color definitions, I thought it should throw an error if you try to define a color with hex color codes, but I can see now that it doesn't (bug).

@karlstav
Copy link
Owner

the function that checks this is part of curses.h. I am not sure why it doesn't work, I know that it has worked before, as I tested this with konsole when this was implemented.

@Scrumplex
Copy link

It probably has to do with fonts in part. Try changing the Konsole font to Monospace. It is the best performing for CAVA.

@karlstav
Copy link
Owner

karlstav commented Feb 8, 2018

@Stephr1, I was finally able to test this with konsole on something else then fedora (Mint 18.3) and there cava exits and throws the error:

Your terminal can not change color definitions, please use one of the predefined colors.

when trying to change color definitions (gradient needs to change color definitions to work).

Konsole is Version 15.12.3 and ncursesw 6.0.20160213

@karlstav
Copy link
Owner

karlstav commented Feb 9, 2018

On fedora 27 I have konsole Version 17.08.1 and ncursesw 6.0.20170722. And yes, instead of throwing the error it runs cava without changing the colors.

My guess is that for some reason Konsole 17 thinks it can change the color definitions, but obviously it can't. Maybe report to konsole forum?

@bunder2015
Copy link

bunder2015 commented Jun 26, 2022

Hi, I recently upgraded to kde and it appears this still messed up, it seems this is a konsole thing from reading this issue, but I thought I'd let you know.

https://i.imgur.com/GHEMsUL.png (konsole on the left, mate-terminal on the right)

Cheers

@Faithxull
Copy link

I Also have the same problem on konsole

@enderprism
Copy link

fixed by changing the output method to noncurses

@enderprism
Copy link

Hi, I recently upgraded to kde and it appears this still messed up, it seems this is a konsole thing from reading this issue, but I thought I'd let you know.

i.imgur.com/GHEMsUL.png (konsole on the left, mate-terminal on the right)

Cheers

it's also a thing with QTerminal, so i guess all qt-based terminals are affected if they use ncurses as their output method

@karlstav
Copy link
Owner

karlstav commented Jan 8, 2024

did custom (hex code defined) colors also work with noncurses? If so i am surprised, i thought it was impossible to change color definitions in konsole.

@enderprism
Copy link

by affected i meant 'use the wrong colors'. both QTerminal and Konsole display the wrong colors if the output method is set to ncurses (tested with catppuccin/cava, which uses custom gradients), and konsole works fine with noncurses (haven't tested QTerminal.
sorry if i was unclear.

PS.
shortcuts (q to quit, r to refresh, etc.) seem to stop working with noncurses but i don't know if it's intentional or not

@karlstav
Copy link
Owner

karlstav commented Jan 9, 2024

ok, shortcuts should work in the most recent version

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

6 participants