Visualizer fails to work if started at 30fps in mono mode. about cli-visualizer

[dpayne]

I can't seem to reproduce this issue. Would you mind posting your full config, as well as what setup you are using (i.e. linux, osx)?

[d3adb5]

Sure, here:

visualizer.fps=30

audio.sources=mpd

# Defaults to "/tmp/mpd.fifo"
mpd.fifo.path=/tmp/mpd.fifo

audio.stereo.enabled=false

# Defaults to spectrum,ellipse,lorenz
visualizers=spectrum,ellipse,lorenz

visualizer.spectrum.character=█
visualizer.spectrum.bar.width=1
visualizer.spectrum.bar.spacing=1

# Available smoothing options are monstercat, sgs, none.
visualizer.spectrum.smoothing.mode=monstercat

visualizer.ellipse.character=#
visualizer.lorenz.character=#

colors.scheme=default

I'm using Arch Linux, installed cli-visualizer through the cli-visualizer package on the AUR. Terminal's rxvt-unicode, if it helps in any way.

EDIT: I don't really get why, but it happens if i set visualizer.fps to any value from 30 to 41. At 25, 26, [...], 29, it works fine. Then it starts working again when I set it to 42.

Note: again, if I start it with the config file specifying an fps outside that [30,41] range, I can just edit the config file to set it to [30,41] and reload with r that it'll work. If started with fps at [30,41], changing the config file to a value that'd work and pressing r for it to reload its config has no impact: it will remain with a flat spectrum.

EDIT 2: I just changed the fps from 42 to 25 and pressed r. It segfault'ed. New issue?

[dpayne]

Monstercat does work for me at 30 fps, but it's possible it's broken on your screen demensions. I am still debugging it to figure it out. In the mean time could you try a different smoothing mode. Depending on the song sgs usually looks a lot smoother than monstercat.

visualizer.spectrum.smoothing.mode=sgs

[d3adb5]

I've been using it at 25fps without an issue, it just seemed like the right thing to do to report the bug.

That said, at 30fps, sgs also doesn't work when the program starts. As for screen dimensions: you mean the terminal's? I ran it on windows of different sizes and the result was the same. ☹️

[dpayne]

I've gone tried a lot of different things to reproduce this and still haven't been able to figure it out. Does it still happen on the latest build?

[d3adb5]

Whoa, seems to have been fixed in the latest build...?

Sorry I neglected this issue for a long while. I was doing just fine with 25fps. Just reinstalled cli-visualizer from the AUR to get the latest sources and it seems to work just fine with 30 set as the framerate.