Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: audio device on Beelink u59 / AZW U59 (U3E1) (Read 4618 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

audio device on Beelink u59 / AZW U59 (U3E1)

Hi there. I realize the device i have is probably not expected to produce high-quality audio, and it doesn't, but at least it has worked, and i know it works but its subject to not working after software changes, primarily windows updates. I initially experienced the problem for a while when I participated in the Windows early releases, but encountering this problem back in Oct 2022, I unenrolled from that and eventually my problem was solved. The audio device has been shown as "KT USB (Headphones)" when it's recognized.

The point is: with the latest Win 11 upgrade, my audio device stopped working altogether (Img of Device Mgr - i don't really get why it's a USB device but that motherboard is tiny, so... ). I've had issues with this device before (the very same issue), and i'm 99% sure it's a device driver issue, and is related to the Windows Update.

Trying to stay away from those one-size-fits-all driver update utilities (although I have scanned the system, and there were some reports w/ the Audio device), the last time I encountered this problem, the only thing I could find to restore the audio was actually reinstalling Windows 11 altogether. I have resorted to trying a couple of allegedly trusted "Driver Updater" utilities. One detected the driver issue, but most of them don't even pick it up.

Does anyone have any advice on this? I've Communicated to to both manufacturers (links to OEM forum post RE drivers). Maybe you know of a best resource for finding drivers, and a trusted resource? I've read that Win 11 shouldn't have these kind of problems, or that you at least don't want to use a third-party/ non-OEM driver.  I found very little information about it. Mine's not officially an AZW product (seems identical) but I reached out to them as well (might have received an email come to think of it. i need to look)

Thanks for reading!

Not trying to bash them, because I liked the product otherwise, but... I guess i wouldn't call it good support.
Lastfm as PSU_Strummer. i used to play guitar on stage. that was fun. now i enjoy listening to it on foobar2000

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #1
Right-click on the "Unknown USB device" in Device Manager and select "Properties".
On the "Details" tab, set "Property" box to "Hardware IDs".
Right-click copy that value and Google it; sometimes this will lead to a usable driver.

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #2
Unknown USB Device (Device Descriptor Request Failed)
This specific error usually indicates a problem with one of the upstream devices, such as the "USB Root Hub (USB 3.0)" device. It can be caused by outdated firmware, a bad driver, incompatible power management settings, or even faulty hardware.

I didn't see any firmware updates, so let's skip that one.

The only trustworthy sources of drivers are the manufacturer's website and Windows Update. Here's the U59 driver page on the manufacturer's website. The problem may be caused by a driver that seems unrelated to audio, so try installing all of the drivers offered by the manufacturer.

If installing the manufacturer's drivers doesn't fix the problem, check Windows Update for optional driver updates. Sometimes Microsoft will offer newer (or older!) drivers that way.

For power management settings, type "Unknown USB Device (Device Descriptor Request Failed)" into your favorite search engine and look for instructions to disable fast startup and USB selective suspend. The default settings are ideal for most users, so if this doesn't help, you should put these settings back the way you found them. (You'll also find instructions to download various shady tools, but I'm sure you already know you shouldn't download anything.)

If it's a hardware problem, there isn't a whole lot you can do other than check your warranty and get a replacement, repair, or refund.

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #3
It isn't obvious to me whether this computer has more than one USB bus, but you have a chance at that, given that it has four A ports and one C port. But sometimes that has solved similar problems for me.

I have sometimes had use for Ghostbuster (portable version, requires administrator privileges). Description and link to official page here: https://www.neowin.net/news/ghostbuster-1080/
Uninstall device in device manager, disconnect it, open Ghostbuster, search for "ghosts", remove them, and insert device in a different port. Not the neighbour! The one on the other side. Maybe even if you have a C to A adapter cable try that too.

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #4
It occurs to me - there's also a "U59 Pro" with a different set of drivers. Are you sure yours isn't the Pro version?

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #5
Hi there. My sincere apologies for never revisiting. I'll have to verify my contact settings for topic replies.

This problem still plagues me. Yes, @Octocontrabass , mine is the "Pro" model. I just pulled up the Amazon invoice from 2022, which still links to the product that i purchased. That's it, but I did upgrade to 32GB RAM.

I annotated a screencap to attempt demonstrating. This device isn't working again, so I tried a bluetooth speaker I have but it's not functioning either.

I've downloaded and installed the drivers from the Beelink website in the past (pretty sure it's that same file). Why it's listed for Windows 10, when the product ships with Windows 11, who knows! Got 'em again just now and will install.

But I did not realize there's a different set. I can't believe what a pain in the @$# this thing has been with the audio. Cracks like digital distortion. Like a bad cable or something. Turn the output way down, and the amp way up maybe it's a little better. That sucks anyway.

@Porcus that's some interesting and insightful news! I knew I'd come across the best information here. I'm always doing something else and forget to follow-up on the things that are "for me". Or, I got it working. Seems like I go through it every quarter year or so.

Sorry. I'm really excited to see all of the replies to little old me's post here. I feel like a jerk for letting it sit here.

I'll come back to report my findings if i'm allowed!
:)
 
Best regards.


Installing a software, FxSound -- much to my surprise, i assure you -- has fixed this problem in the past. That's some weird software. I don't understand what it does. It makes it seem like there's a new device, vs just being some kind of DSP. That's not where my genius lies. I've plugged guitars into rack-mount DSP's n stuff like that, been in recording studios and used really high-end gear. I know enough about it all to have a basic idea of what it probably is, but then I fail. And with this driver situation being needle and haystack (perhaps you recall if you checked on it at all). Its enough to drive me more nuts than I am.

The true solution lies in a new purchase. It's fine if I don't have to be irritated by that garbage audio device.

I'm all ears if anyone knows of something similar for under (or around) $500
(e.g. out of my current price range, but this seems nice for 2024? I might be afraid to even look inside. One of those peanut brittle cans gag. Open it up, and interfaces and wires and components just fly out all over the room... fun for the whole family! i hate bein' old.)

Lastfm as PSU_Strummer. i used to play guitar on stage. that was fun. now i enjoy listening to it on foobar2000

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #6
It's so unnerving I always forget. The audio device actually works "fine" when I boot into Linux. There's still issues. I hesitate to ever buy a product from that manufacurer again. I hate to say that because I'm just not the type of person to go around trying to dis' on someone. I'm from way back when you could fit 6 hard drives in the case! the old IDE kind. but stuff worked back then somehow.  my fingers can barely get the screws out to swap the SSD on occasion. haha. We made some pretty bad-ash recordings with this Event Electronics GINA though. I think it was 16bit 44.1k?

From my professional experience, albeit twenty years ago by now, you're always going to get a better sound from outboard gear, even if the processor isn't being taxed because it's simply what it's made for. quality outboard gear (e.g. ad/da conversion processes) makes for night and day of course! Cables etc. When Windows tries to use it, it sounds like there's broken wires on the INSide! Obviously, it comes down to not being able to afford the proper gear at this time. So, I'm writing as much to hear myself say it.

I would say Linux powers it in fairly high fidelity. I personally never liked the way any audio sounds on Linux. Never studied it.

Thank you, cordially!
Lastfm as PSU_Strummer. i used to play guitar on stage. that was fun. now i enjoy listening to it on foobar2000

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #7
From my professional experience, albeit twenty years ago by now, you're always going to get a better sound from outboard gear, even if the processor isn't being taxed because it's simply what it's made for. quality outboard gear (e.g. ad/da conversion processes) makes for night and day of course!
Twenty years ago the difference was night and day. Today, onboard audio is good enough that most people will never notice anything wrong with it.

You may be better off getting a laptop instead of another one of those mini-PCs.

Re: audio device on Beelink u59 / AZW U59 (U3E1)

Reply #8
Quote
you're always going to get a better sound from outboard gear, even if the processor isn't being taxed because it's simply what it's made for. quality outboard gear (e.g. ad/da conversion processes) makes for night and day of course! Cables etc. When Windows tries to use it, it sounds like there's broken wires on the INSide! Obviously, it comes down to not being able to afford the proper gear at this time. So, I'm writing as much to hear myself say it.
For listening, a regular soundcard or motherboard audio is often fine.   If there is a weakness/defect it's usually noise (hum, hiss, or whine in the background).  

Recording is a different story.   The microphone preamp in a soundcard is often low quality (noisy) and stage/studio microphones (XLR balanced connections) don't work properly with a soundcard, and you need an audio interface (or special internal hardware) for multitrack recording.    If you are recording line-level stereo, your soundcard may be OK.

Usually "bits are bits" so there should be no difference in the digital domain (assuming no intentional effects, etc.).   If you have problems it's usually related to multitasking.    The operating system is ALWAYS multitasking and interrupting the audio, even if you're only running one application.    

For that reason there are buffers to keep the audio flowing in-and-out smoothly.  But if something interrupts and hogs the system for few milliseconds too long you get buffer overflow (recording) or buffer underflow (playback) and a glitch or dropouts in the audio.  And whatever is interrupting doesn't have to be using a lot of CPU power, it just has to hog the system for a little too long.

A Windows computer is likely to have more "crapware" running in the background than Linux.

Buffers are also delays and that can be a problem if you are recording and monitoring yourself through the computer.   For playback, a few milliseconds of latency isn't a problem and it's not a problem with recording as long as you are not monitoring through the computer.

Another issue when recording with Linux can be that some higher-end audio interfaces don't come with Linux drivers.