Hi . Brand new member… This thread covers all the problems I’ve had since I bought a UCA222 off ebay. But doesn’'t solve them . I would have even taken a chance on the 2.8.40 driver linked to in a previous reply but that driver does not seem to be available for download any more.
Win10 recognises it as a “USB audio Codec” - as does Audacity. If I import a wav file it plays back ok through the UCA222 headphone jack if it is set as the playback device.
But absolutely nothing heard/seen when selected as the input.
I tried it on another win10 pc with the same result… I actually got it to try using a decent mic + preamp with Skype or Zoom but they don’t recognise it either…
I’ve had to give up but will keep an eye open here in case a solution comes along…
What is plugged into the input of the UCA222?
From a reputable vendor?
Did you buy it new or second hand?
Ok… First the answers ! The input to the uca222 is an Audio Buddy pre, which is working. And No, the UCA222 did not come from a reputable vendor.
In my hours of searching tintenet this morning I came across the dire warnings on eBay chat of the “flood” of fakes. Mine doesn’t have the clues shown there defining it as a definite fake - but it maybe.
However, as it played back, and sometimes the clones do work anyway, I persisted
Since I posted earlier, I’ve got it to work… Somewhere along the way the audio cord between UCA222 and the Buddy had gone O/C…
So I’ve retraced my steps with a good cable. Now, win10 sees the “USB audio Codec” as before but it does not appear in the Audacity Ins OR outs.
That’s computers ! However I persisted with the idea of the 2.8.40 third party driver and actually found a download (without installing PUPs etc.
The install process was not successful because the final “box” gives : Install, uninstall and cancel" options. I pressed install and nothing happened…
I tried several times with the same result >
Then I noticed that the file originated from a company called Ploytech GmbH (https://www.usb-audio.com/) and went to investigate.
They look to me like a legitimate software company. 2.8.40 is no longer listed as a download BUT 2…8.45 is… I downloaded a trial version because it looks like you now have to pay for it now. It stated that the trial will beep every 30 seconds. It did.
However, I had exactly the same trouble with the “install” button… But while bashing it repeatedly, suddenly nirvana. And it installed and worked in Audacity.
I uninstalled and went back to the 2.8.40 version download from earlier and after repeatedly hitting the “install” button , that installed OK. perhaps it just needs thinking time
Anyway I will try it out properly later but for now I’m happy… BTW, the internet is awash with hits on the 2.8.40 driver - all from Driver companies with a zillion misleading download buttons to give you something you don’t want… I think the link in an earlier post is the only clean source out there for the older free version…
I may be wrong… but that’s my experience today… Roger
Ah Ha!
The device needs to be connected before launching Audacity. If you don’t do that, then you will need to “Rescan audio devices” (near the bottom of the “Transport” menu) to allow Audacity to see the device.
The Behringer UCA222 “should” work with standard Windows USB audio drivers.
Yes, it’s a minefield.
Thanks Steve… I’m old and got a headache now after chasing this all day… I’ve been re-booting, re-running Audacity (and malwarebites 3 times) and I can’t swear that I always had UCA22 plugged in when I ran Audacity.
So I uninstalled 2.8.40 driver … But windows seems to have lost its generic driver… It can’t find it and so possibly I deleted it. I cannot find how to replace it and try again… So back to 2.8.40 (after the usual described difficulty) and it’s working again.
I’m not convinced there is not a win 10 issue somewhere - as Skype and FB vid messenger couldn’t see it either. But I’ve now tested it in Skype with the 3rd party software and it works.
I need to clear up something I said earlier… The link I referred to was to the YouTube video which showed “drivers.informer” as the source. In fact although still listed there, they state no driver available : upload one if you have one !!
SO…I think I actually got it from DriverGuide by carefully stepping through the maze… It’s been a long day !
And Malwarebytes is Still happy… I’m leaving well alone for the time being
When required, Behringer provide drivers for their interfaces on their website.
They do not offer a driver for the UCA-222 because it shouldn’t need one.
I have checked on the Behringer website and they do not provide a driver version 2.8.40 for anything. As far as I can tell, it appears that the “2.8.40 driver” is not genuine Behringer software.
Perhaps this page will help: Update drivers manually in Windows - Microsoft Support
Thanks for you patience Steve.
Feel free to delete previous posts in case they confuse.
Window10 generic USB driver is reinstalled and working.
The problem may have been a combination of my incompetence and the broken patch lead feeding the UCA222.
There may have been issues with Windows in the past (the YouTube video nolen011 mentioned might be evidence of that)
The third party driver 2.8.40 all over the net (by plytech GmbH) is dated 2011. The latest version appears to be 2.8.45 and is not free.
They claim a performance advantage, which may no longer be true -if it ever was.
Once it is installed it is not easy to get rid of." Uninstall device" and it pops up somewhere else in device managed, including as a Burr Brown entry and an unrecognised something (sorry to be vague)
Until all have been “uninstalled”, Windows update simply says the best driver is already installed and puts back the 2.8.40 driver called “Behringer USB WDM audio”.
Super. Glad to hear you fixed it.
Hi Everyone,
I’m having the same problem and I tried everything.
I plugged the device in and i can hear the sound from my mixer thru the headphones that are connected to the UCA222 device, but when i open Audacity i cant record.
When I plug usb into pc it shows up in Setting/Sound/Recording as “Microphone 3-USB Audio Codec”.
Any suggestions?
Thanks in advance