USB Audio driver for AmigaOS4

@balaton
It doesn't work on a real C-Media device when passed to QEMU PPC AOS4.
The result is the same as with the -device usb-audio option.
Someone with a real Pegasos II or AmigaOne needs to let us know if this driver works for them.
I haven't tested it on QEMU Linux PPC.

EDIT:
Yes, you're right, I checked on emaculation.com. USB audio doesn't work on macOS X, only on macOS 9 – my mistake, sorry for the incorrect information.
https://gitlab.com/qemu-project/qemu/-/work_items/446
https://www.emaculation.com/forum/viewtopic.php?p=81464#p81464

EDIT2:
I ran a little experiment based on what you wrote
I added your patch to QEMU (QEMU version 9)
https://lists.nongnu.org/archive/html/ ... vel/2026-02/msg02357.html

It looks like this in ‘qtree’


Debug output from AOS4 (the label ‘usb-audio’ comes from the QEMU driver debug output)


Something’s alive and kicking – it’s a bit of a nightmare, but I can see the driver is communicating with the USB audio and nothing’s freezing up. I don’t think I can hear any sound, though.
It’s just an experiment, of course

EDIT3:
‘device usb-audio’ works under QEMU Linux PPC (slight audio distortion)
screen - > https://ibb.co/JRxmbnp9
screen (ohci) -> https://ibb.co/0jXH2H7H
screen (so everything’s in one place) virtio net, that works too -> https://ibb.co/NdWWt0kb

EDIT4:
I passed the “0d8c:000c C-Media Electronics” USB pass-through device to QEMU.
On Linux, QEMU PPC works without any issues.
On OS4, it doesn't work.
The device has an LED that lights up when it's in use. There's no indication that it's working.

@smarkusg

It seems correct. The only problem seems:

Start: SET_CUR sample rate failed: -9

But this is not a qemu problem.
I will investigate

@afxgroup

UsbAudio 2.3 and Rubix, AHI prefs lists few usbaudio modes at least, but trying to play something it doesn't make any audio output (AmigaAmp). Output and input sliders can't be moved in the prefs.

Also the driver spits so much debug info out that it slows down the whole system.

@TSK

Can you send me the serial log? and which audio card you have (and maybe also the machine you are using)

have to dig up an old USB sound card I got a few years back trying to get Poseidon on my A4000 working with it to see if this driver works with it

@afxgroup

I'm trying to configure a SoundBlaster Extigy. I get this in the USB log :




I add this in my USBAudio.prefs :



But can't get the custom device name I've setup. What am i doing wrong?

BTW, the Extigy works great exept for FLAC audio in AmigaAmp, the sound still stutters.

I will try the record function and thanks again for this USB audio driver.

@afxgroup

I have noticed the machine will lock up on bootup if the USB card is not present.
Presumably when trying to play the startup tune.

Cheers

@afxgroup

Testing on my Sam460LE with driver's version 2.3 and the CSL card you've suggested in your post #2.

So far so good, the device is recognized by the OS on the fly, I can select one of the new modes. Played some games (Quake 2, Starfall Defenders and UBEK) and had a proper sound in all of these. Watching videos with Emotion worked good as well.

What didn't work quite well was playing music with AmigaAMP. It gets sound glitches from time to time, and if there's a concurrent operation happening in the OS like resizing Filer's or MultiViewer's window, the sound gets terribly sliced while window keeps getting rerendered.

Two more observations, that are not problems by themselves, but probably worth mentioning:
* the test sound in Sound Prefs is rather weird
* there is also weird sound playing for a while in the exact moment the AmigaOS 4.1 splash screen appears during OS loading.

Once again thank you for your awesome work!

@Djk83

Thank you for your reports. I can work on the drivers (and all other stuff i'm working on) in a few weeks.
Unfortunately my real work is filling up all my free time..

@afxgroup

That's totally fine! The driver in its current version is already good enough for me to consider freeing up a PCIe 1x slot if I'd need it.

@afxgroup

I am adding output from AudioClassID for Topping D10:



I hope, it helps a little.

Hi All,

-- Just installed latest USB audio driver for OS4.1.

-- Note: There was no readme file included, just the installer only.

-- The installer worked fine.

-- I went to sound prefs.

-- I see the new additional sound modes by Andrea Palmate.

-- I selected any of the modes and play a test sound.

-- I can now hear a long beep from my external USB speaker for the 1st time.

-- My external USB speaker is from Amazon

-- USB inspector shows its a USB 2.0 audio device serial number of 20130100ph0.

-- But when I try to play the OS4.1 system start up sound hirasawa in sound prefs.

-- Vu meter by Lyle Hazelwood is pulsing up and down while playing the sound.

-- But I still have no sound.

-- I tried testing each mode again and can hear beeps fine.

-- I am missing a step to get sound fully working in OS4.1?

-- Any advice is appreciated. Thank you.

@Boabster

You are running multiple audio drivers.

Open Prefs/AHI
Select "Music Unit" , then select the new USB Audio driver
Select "Unit 0", then select the new USB Audio Driver
Select "Unit 1", then select the new USB Audio Driver
Select "Unit 2", then select the new USB Audio Driver
Select "Unit 3", then select the new USB Audio Driver
Select "Save"

I never cared for the GUI design of AHI Prefs.
I think having tabs for each unit would be more visually clear.


Let us know how that works out,
Lyle

Hi @LyleHaze,

- Thank you for your reply.

- Strangely my AHI icon was not in prefs?

- Not sure what happened there?

- However, I managed to get a copy of AHI from my A1222 ISO.

- And paste AHI into my prefs drawer.

- I followed each of your instructions.

- Strange, each time, I select the new mono USB driver on each of the units.

- Play a test sound, the entire system locks up?

- And a reboot is required to restore normal operation.

- Once I have save all of the units, rebooted the system.

- Yes, I can now get the Amiga OS 4 startup chime loud and clear.

- Fantastic.

- But the thing is my system is now completely locked out upon start.

- Question to you: Is there a safe boot mode I can try to disable the new audio USB driver to allow the system to respond normally?

- New update: Actually, I think it a delay, my system is responsive now.

- Just tried TuneNet to play internet radio. Still no sound?

- Still doing further testing and checks........

- Be back with another update soon.

Hi All,

- Another update after further testing.

- I can confirm, I am getting audio output from my external USB speaker but with problems.

- I am not sure why TuneNet internet radio is not able to playback any audio output at all?

- I checked TuneNet settings, i tried setting the AHI audio 0, 1, 2, 3, or AHI user mode and specifying it to USB mono driver, there still no sound output?

- Aall internet radio stations, no sound playback at all?

- It can't be all of the stations are offline or is it?

- After rebooting the system.

- It seem to lock up my system entirely when playing the startup chime.

- If I leave the system alone for an extended period of time, say 10 mins.

- I get a response from the system, the mouse pointer moves, I can use the system.

- Or sometimes, after 10 mins, I have to reboot the system to get nromal operation again.

- After reboot, the audio output seem to go very quiet, I could hear something coming from the external USB speaker but very faintly.

- I tried adusting the USB mono driver volume in AHI prefs to maximum.

- I also notice in Sound prefs, it USB mono driver volume is set at the middle, so I push that volume to max.

- Each time I play a test sound either on AHI Prefs or Sound Prefs, the audio output can be still quite low sound output even at already set to maximum.

- Sometimes adjusting sound volume can also lock up my system, forcing another reboot.

- Despite all of this.

- If I power down the system, start again, setting AHI Prefs, 0,1,2, etc, set to maximum volume, including sound prefs and another reboot.

- I am getting a clear loud sound output when system boots into the Amiga OS 4.1 startup chime but I still have the problem of complete system lock up.

- To encourage continued development of the USB audio driver, I will contribute a donation soon and I look forward to future updates and enhancements to audio USB driver.

- It seems we heading on the right way, If you need debug logs, let me know how to gather them for you, I will provide them for you.

- If you have any other suggestions, please let me know, any advice and feedback is appreciated.

- Thank you

@boabster
I am not the author, but I THINK this new USB auidio driver is for Audio Class 1 devices only.

In past projects of my own, I had a lot of trouble explaining that Audio Class 1 and Audio Class 2 are not compatible.

So I recenly wrote "AudioClassID", to at least make it easy to TELL which is which. When you run it with no other arguments, the last line of each interface says "USB Audio Class Compliance: " followed by 01.xx or 02.xx

Since I'm digging into details, here's the back story:
Audio was the very first USB Class. When the Audio class was laid out, there were a few details that were not defined properly. So manufactuirers each decided how to fill in the blanks. This made the driver more complicated, and the worst part is that the "fancy" bits have no documentation.

Eventually they decided to re-design the standard. Part of the changes meant changing descriptors, structures, and sometimes even used the same names for changed parts. At least it's all documented now, but there's a LOT of class 1 devices already out in the wild.

So the driver has to check this "Class Compatibility" when they attach to a new device. The Class 2 drivers know to check. Older Class 1 drivers were not expecting a redesign, so they are often unaware of the need to check this.

And that's probably way more than you wanted to know. I THINK he said this driver is for class 1 devices only. I also recall you said your device said class 2. I think you might find the problem with that mismatch.

I do have a class 2 driver in the works, but like many of my projects it's not been worked on in a while, and I don't plan on connecting it to AHI. Most likely it will go directly to AudioLink.library instead. (AudioLink is another unfinished project, I have a lot of those)

Again, too much information, but it'll give the people just browsing something to read today.

I hope this answered some questions.

@LyleHaze
Quote:
I think this came up before and then those who understand it said only the Unit 0-4 should be set to the audio driver and the Music Unit should stay audio device (or whatever it was originally) because that's how multiple audio streams are supported by software mixing or something like that. Not that this would fix a non-working driver but that should be the correct way to configure this in my understanding.