Make sure HDMI is selected as default output in Sound & Video -> PulseAudio Volume Control settings. You have to click on the green checkmark with "set as fallback" tooltip in the screenshot below:
If that doesn't help, or you don't want to keep Pulse at all, remove pulseaudio, reboot, and your system should be back to plain ALSA. You can ...
When your custom user fails to play the audio, are you also logged to the system as the pi user? audio group is tricky, it allows users in that group to get exclusive access to audio HW, preventing other users from using it:
Adding users to the audio group allows direct access to devices. Keep in mind, that this allows applications to exclusively reserve ...
No its a 4 channel i2s dumb board whilst the pi has a single i2s channel for a single l/r pair.
Also there is a myth that an array on its own is somehow good but without the DSP simple summing creates some pretty bad high pass filters.
adafruit have a tutorial on how you ...
Start by checking the PulseAudio settings (pavucontrol) and VLC audio output preferences. First, set everything as on the screenshots and see if that gets HDMI audio going.
If that doesn't help, force VLC audio output to PulseAudio instead of "automatic", play a file with it, and open pavucontrol again. Check the "Configuration" tab (you ...
There is a g_audio driver which allows Linux systems with USB OTG support to show up as audio devices on the USB host.
You won't be able to do it on a Pi 3 though, you'll need a Pi 4 or a Zero which support OTG.
I had similar problems with a USB speaker connected to a Pi 3 Model B - the speaker would click when I attempted to play a sound and then go very quiet as though it had been powered off.
I checked dmesg and it seemed like the over-current protection had been doing exactly that.
[ 127.114267] usb 1-1-port2: over-current change
[ 127.346880] usb 1-1.4: USB ...
What sort of frequencies are you talking about?
pigpio can do this with waves (hardware timing).
My new lg library can do this using software timed PWM.
E.g. Python http://abyz.me.uk/lg/py_lgpio.html#tx_pwm
pigpio example using pigs (command line)
In my case the problem was that raspberrypi-ui-mods had been held back and it needed to be force updated. You can confirm this by checking if there is a message about it being held back when you run sudo apt upgrade.
Upgrade raspberrypi-ui-mods by running sudo apt-get upgrade raspberrypi-ui-mods.
If you remove pulseaudio, apart from this not being ...
People have reported the successful use of fluidsynth, amsynth and qsynth on a Pi 2 B with Raspbian. Even a more complex zynaddsubfx works, even though it seems to require some tweaking.
Sound via HDMI is possible. Some seem to prefer an additional hat for sound though.
If you don't have your Pi yet, buy a Pi 4; then you should not have to worry at all.
Caveat: I know nothing about aplay or espeak. However, I can sometimes read & comprehend a man page. Simon's answer may be generally correct in that your "other-user" needs to be added to the group audio, but I don't believe you can add a user to a group with the command he's given: sudo useradd -G audio. To be completely fair, group and user ...
amixer sset 'Capture' cap
amixer sset 'Capture' nocap
You may have to find out the control name for the microphone in your setup if you use additional hardware. amixer scontrols will list the controls you have.
There's also pactl command which should work on PulseAudio level. Identify the mic in the output of pactl list sources and then mute / ...
What you erroneously refer to as a "RJ11 cable" is in fact a 8P8C modular connector and CAT5/6 cable.
The 8P8C connector on many Pi models is used for Ethernet over twisted pair. This uses a low voltage differential signalling system.
RJ11 uses a similar six-position modular connector but only 2 pins are used for a 50V analog telephony interface.
Alsa may be attempting to access the config file for the user (usually www-data) at ~/.asound. Make sure that the user has a home directory, and that it's accessible.
# mkdir ~www-data
# chown www-data.www-data ~www-data
Of course there are probably good reasons not to solve the problem this way specifically ... Usually it's a better idea to ...
Are you sure you are still using ALSA only? The Pi OS has recently switched to PulseAudio, so if you're using an up-to-date system you may want to poke around Pulse settings.
Checking the kernel log (sudo dmesg) and the list of loaded modules (lsmod) might also help. Personally I would start by unloading the driver sudo rmmod <driver-name>, loading it ...
The answer to this issue can be found here:
The solution presented worked for me to get sound while running a python program from system.
What one has to do is to add defaults to the asound.conf file at /etc/asound.conf. I did sudo nano on file and found nothing in it, so I added
See if you can set the default audio sink device in Pulse Audio Volume Control settings, as described in this answer. Pulse settings are user-specific, so this has to be done for every user you create.
The suggestion by Andyroo works: for headless raspberry pi, you can remove the file that triggers this on every reboot.
Assuming you can ssh into the device or plug a keyboard:
sudo rm /etc/xdg/autostart/piwiz.desktop
Yet another option is to use Pulseaudio (especially if you already have it on your PC), configuring the Pi as a network sink. In the simplest case, you set up module-native-protocol-tcp on the Pulse server on your Pi, and set the $PULSE_SERVER variable on your PC to the IP address of the Pi.
If everything is set up correctly, you'll have another output ...
There is a standard UPnP/DLNA that makes it easy to setup what you want, including bonus points for controlling it with your Android smartphone.
You can install a media server on your PC and a media renderer on the Raspberry Pi. Before doing it you must have the audio working on the RasPi, means you should be able to play local stored test songs with simple ...
Glad to hear that you solved it with a fresh install of the OS. Yeah, I've had similar issues where flashing the SD card with the latest OS was the solution as well. This is why I use raspiBackup to make sure I'm always backed up (and I keep an extra SD card or two laying around just for these situations).
APTX is a proprietary codec so I think it is unlikely. I would just mention that unless you are using it as a source for bluetooth headphones you would be much better off using it as a wifi/ethernet streamer as opposed to bluetooth. Even the best bluetooth codecs are extremely lossy, whereas LAN based transports like DLNA/RAAT/Squeezelite/chromecast/airplay ...
I just installed the same HAT on my Pi. Incidentally I had the same "issue".
Is your user part of the audio group? Try:
sudo aplay -l
If that works, add your user to the audio group:
sudo adduser username audio