I realize that the ULTRA has been a pain in the neck to configure because the drivers for the WM8960 are never included in the new releases. Could it be due to the fact that Raspberry Pi is now making their own sound card and trying to favor their brand?
So, I will stop making the ULTRA and instead replace it with the Pi Audio Drive that uses a driver included in every distribution and has an EEPROM to automatically load the drivers, while having the same audio input and output capabilities.
Whatās the latest and greatest installation guide for raspberry pi 2W 32 bit Bookworm and ultra+? I tried multiple ones,ā¦ nothing worked. Or should I install/ switch to 64bin? Best regards
For those arriving at this post in 2024, Iāve found a set of instructions that get the on-board mics and speakers working on a Raspberry Pi 5 (headless in my case). I tried every method in this thread with no luck, but came across this post here that uses the same chipset:
NOTE: Your āplughw:0,0ā numbering for both those scripts might be different from mine. The first 0 is the index of the sound card. You can find this number out for your mic by running āaplay -lā and for your speaker by running āarecord -lā and looking for where it says ācard X:ā where X is the number you should use instead of that first 0.
Thank you to user āanonymous_meā ā i was able install the ultra++ with;
PI4 hardware, version bookworm desktop 64-bit release july 4, 2024
NOTE: I needed to run the ./install.sh a second time after reboot.
NOTE: the index was āplughw:3,0ā
NOTE: the gain was very low, alsamixer is in the distro, so I used that to adjust gain
Hey Raspiaudio, thanks for your product.
Iām using ULTRA++ and working on a project where I can use a raspi as portable recording device with external binarual microphone.
It might not be heard with low volume but you can here this contant tick sound when you make it louder. Are you familiar with this noise? I assme that itās not an issue from your module but could be noise from processing sound from raspi itself? Iām not sureā¦ I wonder if you have faced this issue when you develop this module and would be appreciated if you have any solutions.
The microphone itself has no issue because it has no noise issue on other handy-recorder.
For those who have been struggling with this module installing on your Raspi 4B bullseye,
I did a bit of workaround and confirm that ULTRA++ is working well on my Pi.
hostnamectl from my machine returns:
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64
Basically you can follow @Raspiaudioās Method 2 full control instruction but here is what I have done.
After you git clone https://github.com/waveshareteam/WM8960-Audio-HAT and cd WM8960-Audio-HAT, you need to change a commit version to the old one because the recent one seems to be coded for bookworm (which is not working on both bullseye and bookworm on Rasp 4B).
To change the working commit version, you can command: git checkout 8141dad26281d661de4be2a823662f5510ec98da inside of the WM8960 directory. Once it is changed, you can start sudo ./install.sh
Having problems with Ultra++ on PiZero v1 which was installed with an image about two weeks ago and updated.
Have installed the hat and drivers according to the new instructions on page 1. The soundcard appears in raspi-config. It appears on aplay -l and checking in /etc/asound.conf shows the card as the default deviceā¦ however dmsg givesā¦ wm8960 1-001a: No MCLK configured
ā¦ and trying to aplay a wav file givesā¦
Playing WAVE 'LTT Theme.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1416: Unable to install hw params:
Iām guessing that the primary problem is going to be the MCLK but being a newbie at this, thatās a guess.
I am also running MPD on this board, to act as a receiver for audio from Home Asisstant, so my ultimate goal is to use the headphone out for MPD, although I havenāt heard the quality of the on board speakers yet, so Iād like to be able to try MPD through both.
Last version of Pi OS introduced some modifications on the audio management system and we have not tried it on the zero since. We need to put one engineer on the task and try it in your exact setup, it canāt be done overnight because every body is assigned on something else now, but we will do it by the end of next week and post an answer here.