![alsa vs pulseaudio alsa vs pulseaudio](https://www.sequencer.de/synthesizer/proxy.php?image=http%3A%2F%2Fwww.tedfelix.com%2Flinux%2Flinux-midi.png)
- #Alsa vs pulseaudio install
- #Alsa vs pulseaudio software
- #Alsa vs pulseaudio series
- #Alsa vs pulseaudio windows
Let's have a look on his trophies, the five "bugs" he posted: Regardless what I think about Jeffrey and his behaviour on Planet Gnome, And maybe doing it for days is not particularly nice.Īnd maybe flaming sucks in the first place anyway.
#Alsa vs pulseaudio software
Is very much part of the Free Software community I guess. Only to continue flaming and bashing in more blog posts shortly after. Particularly interesting in this case is theįact that he apologized to me privately on IRC for this behaviour shortlyĪfter his first posting when he was critizised on #gnome-hackers.
#Alsa vs pulseaudio series
In a series of very negative blog postings he flamed my software and hence me Not just those two frequencies however - other hive activity not in this sample will be at other frequencies in those two general areas.Jeffrey Stedfast seems to have made it his new hobby to bash PulseAudio. The two main peaks are where the activity will be happening. The above image is an fft taken over an entire 5 minute sample using audacity. Something more like 10hz per bin at that frequency would be a problem. A little narrower around the 200-400 range would have been nice but a 3-5hz wide bin will be usable for a first approximation. The last displayed range was for 128.534912->131.388443 which tells me that the separation is ballpark for what I'm looking for. (I'm mostly interested in values around 400hz and 1200hz roughly) The display appears to have been clipped to 44 lines of in as that is the largest size I can make my text screen, so I can't get the frequency info for all 200 bars. Scraping the cursor addressing out of the redirected output gives the data below. I turned on debug - it runs in ncurses mode but crashes if set to raw mode. Do you have a preferred forum for cava discussions? (I'll close this as an issue after you reply.) I'm sure a github issues log is not the best place to ask general questions but I couldn't find anywhere else. One final question I should have asked earlier. How do I know what frequency range each bin represents? Is it just intervals of (2000-50)/200 starting at 50, or is there something else going on?
#Alsa vs pulseaudio windows
I did read your caveat about it being more for display than science, but of the various packages I looked at, it seemed the easiest to get started since it didn't require X windows (we don't run X inside the beehive - just bash :-) ) Would I be right in assuming that the raw data doesn't have any filtering applied, except for log range compression? It did occur to me that I might need to run cava under 'sudo' but doing so showed nothing on the display (no output at all, just the cursor underneath the command line, until I typed ^C, at which point it cleared the display and reported "CTRL-C pressed - goodbye".) I did run 'script' to capture what was sent to the screen on ^C and the message "setterm: terminal screen does not support -blank" had been printed between the ^C and the clear screen. There are some messages in syslog like the one below but I get them all the time anyway - I don't think they're caused by cava: Is there anything else I need to do to get cava to process the input to the mic? It plays back on the headphone jack using: Sudo arecord -D hw:1 -f S16_LE -d 10 -r 48000 test.wav I have a USB soundcard installed and it listens to the mic OK - I can record using: $ emacs -nw ~/.config/cava/config # uncomment method = pulse
#Alsa vs pulseaudio install
$ sudo apt-get install autoconf libtool libpulse-dev libfftw3-dev libncurses5-dev libncursesw5-dev There are a few more apt-get installs needed than are listed in the github doc. First - here's what's needed to compile cava on a pi.