Yeah, that was Alan
Apparently Alan found where the issue came from, it requires a PulseAudio server to run:
I have not tried it but @mithundotdas could you try it if you have a Jetson already setup with balena OS?
version: '2'
services:
audio:
image: balenablocks/audio
privileged: true
ports:
- 4317:4317
ei:
restart: always
build: .
privileged: true
ports:
- "80:80"
- "4912:4912"
environment:
PULSE_SERVER: tcp:audio:4317
UDEV: 1
labels:
io.balena.features.dbus: '1'
io.balena.features.kernel-modules: '1'
devices:
- "/dev:/dev"
Regards,
Louis
Looks like audio block does not work for Jetson. It says no such image balenablocks/audio:latest built on arm04. I am not able to paste the full log from my virtual box.
There is currently an issue with the Nano using the Audio Block that we haven’t looked into: https://github.com/balenablocks/audio/issues/35
I guess a bigger question is, why do we need Pulse Audio running? I don’t recall it being required in the past? (But could be forgetting). Of course, a workaround is to just install it in the same container with EI, and spawn it as a daemon / background process during a start script.
I vaguely remember that some of the asla libraries were removed from debin/rasbian … wondering if that has anything to do with pulse audio. I will manually install on the container and see what happens