Need to reopen this thread or is there a Guthub issues list? The problem has returned.
What is your hardware, and what are the contents of /etc/modprobe.d/asl3-snd-usb-audio.conf?
Hardware is NucBox5 mini PC (N100 processor) running Proxmox. USB SC is Repeater Builder RIM Lite.
I have since restored a pre “recent update” backup so I don’t have access to THAT .conf file unless I restore the update backup. I do however have the asterisk log. If that conf file is critical, I can restore to grab the info for you
Yes, that file is critical to the audio issue. It should contain
options snd_usb_audio lowlatency=0
for your system.
I restored it and the conf file does contain that.
In fact, that’s the only line in it.
Have you then restarted the system to see if the issue remains?
No, I only temporarily restored that backup so I could check the file contents.
To clarify my comment in my OP in this thread, “has returned” means the newest ASL3 needs to run for a yet-undetermined amount of time before the problem manifests. That’s why I thought the log might be useful.
I can restart ASL (service asterisk restart) and the problem goes away for a while. Note I don’t reboot the entire VM.
What does the command
sudo modprobe -nv snd_usb_audio
show?
root@ChehalemASL:~# modprobe -nv snd_usb_audio
root@ChehalemASL:~#
You should see the module and its dependencies and config options listed. Perhaps the Proxmox VM does this differently, but I have no experience with it.
EDIT:
Example:
chuck@fruitjuice:/lib/modules/6.6.74+rpt-rpi-2712 $ sudo modprobe -nv snd_usb_audio
insmod /lib/modules/6.6.74+rpt-rpi-2712/kernel/sound/core/snd-rawmidi.ko.xz
insmod /lib/modules/6.6.74+rpt-rpi-2712/kernel/sound/usb/snd-usbmidi-lib.ko.xz
insmod /lib/modules/6.6.74+rpt-rpi-2712/kernel/sound/core/snd-hwdep.ko.xz
insmod /lib/modules/6.6.74+rpt-rpi-2712/kernel/sound/usb/snd-usb-audio.ko.xz lowlatency=1
chuck@fruitjuice:/lib/modules/6.6.74+rpt-rpi-2712 $
Note that the lowlatency option is set to 1 on this system, a Raspberry Pi 5. It should be 0 on all other known systems AFAIK.
So, to be clear, you are NOT having the same issue where the audio is persistently choppy from the start. You are having a new issue where, after some N period of minutes, the audio becomes choppy where it had not previously? Does it become more choppy over time - i.e. something is “overloading” and causing a continual issue.
1 Like
You will see something like that if the target VM has significantly less bandwidth than what is trying to use it; I inadvertently discovered that here.
If bandwidth is the issue (which I don’t believe it is), why is it only a problem with the latest build and not the previous ones?
If you’re saying you’ve changed nothing else in your setup, then it isn’t (or shouldn’t be).
For me, the update did resolve my “choppy” audio. I’m glad I read the post the other day. I had resigned to the position that my hardware wasn’t up to the task.
Mike / K5JR
Alpharetta GA
Nope, no hardware changes at all. Guess I’m relegated to stay at ASL 3.1.0-1.
I’ve attached the log from the update for whatever that’s worth…
messages_log.pdf (150.7 KB)
So, you see frame sync issue 9 hours after the system starts streaming? As Jason said, this is not the original audio issue. Given that all the Linux VMs I have here respond correctly to issuing modprobe -nv, and the one I assume you are running under Proxmox does not, I might start there.
FWIW - I do not have this issue. My Proxmox ASL3 VM returns:
root@peeter:~# modprobe -nv snd_usb_audio
insmod /lib/modules/6.1.0-32-amd64/kernel/drivers/media/mc/mc.ko
insmod /lib/modules/6.1.0-32-amd64/kernel/sound/core/snd-seq-device.ko
insmod /lib/modules/6.1.0-32-amd64/kernel/sound/core/snd-rawmidi.ko
insmod /lib/modules/6.1.0-32-amd64/kernel/sound/core/snd-hwdep.ko
insmod /lib/modules/6.1.0-32-amd64/kernel/sound/usb/snd-usbmidi-lib.ko
insmod /lib/modules/6.1.0-32-amd64/kernel/sound/usb/snd-usb-audio.ko lowlatency=0
Is that running the latest ASL3?
Proxmox 8.3.2 at both sites I run. And neither VM gives me any return to a modprobe -nv snd_usb_audio command yet ASL3 (previous version) works just fine in all regards. Go figure