Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×
Bug Input Devices Upgrades Windows

Ask Slashdot: Fixing UVC Camera Issues Under Windows? 148

Khyber writes: I bought some cheap Chinese camera glasses with built-in microphones. These are (supposedly) UVC cameras manufactured in 2015. Under Windows XP, these cameras are seen perfectly fine and work as web cameras; even the microphones work. Under Windows 7, the camera appears to install just fine, however I get the 'This device can perform faster if you connect to USB 2.0' (which it is connected to) and when I try to load it up with any camera viewer such as manycam or any chat program's built-in previewer, I cannot receive any video from the camera. I can get audio from the camera microphones under Windows 7, so I am wondering if the camera device is having problems enumerating as a USB 2.0 device due to some change in Windows 7 (which it doesn't seem to have issues doing under XP,) or if the UVC driver for Windows 7 is missing something in comparison to the one used for Windows XP. Anybody else had issues getting newer UVC cameras to work in newer operating systems?
This discussion has been archived. No new comments can be posted.

Ask Slashdot: Fixing UVC Camera Issues Under Windows?

Comments Filter:
  • by jfdavis668 ( 1414919 ) on Wednesday February 03, 2016 @04:47PM (#51434005)
    I don't think that technical support for your driver issue is a good reason to post on /.
    • While we're at it, my printer sharing seems to not be working properly.

      Which is this, "my crappy vendor has no current drivers", or "Microsoft hasn't written a driver for my crappy camera glasses"?

      Definitely a big "WTF" on that one.

      • Which is this, "my crappy vendor has no current drivers", or "Microsoft hasn't written a driver for my crappy camera glasses"?
        Definitely a big "WTF" on that one.

        Uhhh... You do know that UVC [wikipedia.org] is where you're not supposed to need a special driver for your webcam, right? Where anyone who's claiming full USB support is supposed to have a driver for those crappy camera glasses, and my very cheapest yard sale webcam, and many other devices besides?

        • Wow, you mean a cheap product someone bought off the interwebs doesn't adhere to a spec, or Microsoft has decided not to implement the standard?

          I'm shocked, shocked I tell 'ya ... nobody ever doesn't adhere to a standard. Because they're magic!!

          Sorry, ever since there were "Windows Modems", or any "standard" to ignore, people have been doing this shit. Most especially Microsoft and cheapo devices.

          "Supposed to" my ass. Companies have been doing a terrible job of implementing standards since forever. I've

          • Wow, you mean a cheap product someone bought off the interwebs doesn't adhere to a spec, or Microsoft has decided not to implement the standard?

            If you skim the thread, it works on x32, and not on x64. Did they decide, or just fail?

            • Does it matter? Someone failed to, or didn't bother doing some aspect of this ... we should be surprised at this why?

              At this point, I pretty much expect products are taking shortcuts and being pushed to market in a half assed way.

              Because that's how products are done these days; everything is apparently a continuous beta intended to be fixed later (if at all) but sold now. And as often as not, once they have the money, they immediately stop caring about any issues with it.

              • At this point, I pretty much expect products are taking shortcuts and being pushed to market in a half assed way.

                That's always been true. Most things have always sucked. Especially if they say "Microsoft" on them.

    • by Anonymous Coward

      obligatory T Shirt [thinkgeek.com]

    • by msauve ( 701917 )
      Apparently, timothy also has a pair of those glasses.
    • by Anonymous Coward

      Here we go with the blame-Microsoft bitch fest. Might as well get that in. We already got the "Beat our dicks off to Elon Musk" story in for the day. Next up: Graphene.

      • Well, they work under Windows XP (very old) but don't work under Windows 7 (much newer than XP). So it used to work on a Microsoft product and now it doesn't work anymore. I don't see why he can't blame Microsoft.

        • by Khyber ( 864651 )

          Also, these glasses were manufactured in 2015. You would expect the opposite - that they'd work with 7, and not XP. That they work with XP hints at UVC 1.0 support being subtly broken somehow between XP and 7, since UVC is a Microsoft thing.

          I also think UVC 1.0 support got broken somewhere, as 7 sees the device exactly as it should except for claiming it's not on a USB 2.0 port. USB Mass storage works, and when you switch over to camera mode, it does see the camera and microphone, the microphone works, but

          • My guess is that there is an embedded USB hub somewhere in the device which is USB1.1, XP ignores that and allows the traffic to go through, while 7 is throwing an error because the camera expects a USB2.0 path, which it apparently isn't getting. Without a link to what device it is though, I have no way to be able to troubleshoot.

            I would call the tech support for the glasses, but likely, as they are cheap chinese knockoffs, the poster got what they paid for.

        • by SQLGuru ( 980662 )

          So, Microsoft is expected to make everything that worked on Windows 3.1 continue to work on any and all future versions of their OS and gets blasted when they don't, but Apple gets a free pass any time they EOL support for anything.

          I wonder if the OP tried something similar to this: http://answers.microsoft.com/e... [microsoft.com]

    • Timothy's getting delirious after not sleeping for a week.
    • by Khyber ( 864651 ) <techkitsune@gmail.com> on Wednesday February 03, 2016 @07:10PM (#51435175) Homepage Journal

      You must be new here. :)

      Anyways, this is not a driver issue, per se. I believe this is a Windows issue. I have seen reprts of other UVC devices in laptops (their built-in webcams) having the exact same issue.

      Turns out, those devices are UVC 1.0, and Microsoft, in their infinite wisdom, changed something in their newer USB Video Camera driver that breaks devices following the UVC 1.0 spec, despite Microsoft claiming that Windows 7 has full support for UVC 1.0 devices.

      For those people with laptop issues, usually they could fix it by finding the (semi-rare) updated driver from the manufacturer website.

      This manufacturer has no driver. It is a claimed plug and play. And funnily enough, it works under Linux and OSX 10.4+ as advertised!

      This is what leads me to believe that this is not a driver issue on my end, but a MS driver issue.

      And I really, REALLY don't feel like having to constantly run in Test Mode to run a modified driver that's protected by WFP.

      • by Grog6 ( 85859 ) on Wednesday February 03, 2016 @08:02PM (#51435537)

        ...and will fail 64 bit versions.

        I have a couple of older video capture card that won't work under 64 bit, either xp or 7.

        Both work fine in 32 bit.

        The only other thing I could suggest is a utility to switch the usb mode, or force a different speed.

        Making a custom Linux or XP virtual session might be easier to do.
        Good luck!

        • by Khyber ( 864651 )

          Attempting this in a 32-bit Windows 7 environment was not something I had considered. I happen to have a 32-bit machine right here, I'll get 32-bit 7 installed and I will report back.

        • by Khyber ( 864651 )

          Your suggestion is 100% correct. I installed 32-bit 7 and the camera worked off the bat.

          Now, to find out why 64-bit 7 A. throws the "This device will perform faster if you connect it to a USB 2.0 port" error and B. does not get video yet gets audio just fine and then see if C. I can rig a driver hack to fix it and get it past WFP.

      • Looks like you are the poster. Sounds like you know a ton about it and still you are wasting slashdots time with your stupid tech support problem.

        Why dont you post your question to /r/techsupport? Even if I had the answer I wouldn't give it to you because the last thing I would want is for every idiot with a driver problem getting their own "ask slashdot". Sure. ask slashdots are normally stupid, but yours is particularly stupid, and can only really apply to your specific circumstances and so is not interes

        • Re: (Score:3, Interesting)

          by Khyber ( 864651 )

          "Why dont you post your question to /r/techsupport?"

          Because Reddit is a circlejerk shithouse reminiscent of most Linux 'help' forums?

          Because unlike Reddit, I atually expect /. people of my UID or lower to likely have the obviously low-level knowledge required, whereas the majority of Reddit users regurgitate things without bothering to think critically?

          Because Reddit is a shithole that went SJW?

          Need more reasons?

    • If the title was "How I diagnosed and fixed an obscure UVC camera issue" then it would be appropriate for slashdot.
      • by Khyber ( 864651 )

        You never know, such a story might come out of this very conversation IF PEOPLE WOULD STAY ON FUCKING TOPIC (I know, this is /.) and not bitch.

        Then Slashdot could possibly start becoming the tech hub it used to be - because people with actual knowledge used to be seen collaborating on this site, fixing weird issues like this, providing answers that are actually useful, discussing the deeper inherent issues of such things, instead of griping. Much like /. used to try to do, in the late 90s after it ceased be

    • by jtara ( 133429 )

      Did somebody wander in here thinking it was StackOverflow?

      Or did they already try over there and have "discussion closed" for any of a number of picayune reasons?

  • by Alain Williams ( 2972 ) <addw@phcomp.co.uk> on Wednesday February 03, 2016 @04:49PM (#51434017) Homepage

    You must be running Linux, why don't you just be safe and come back to Microsoft, all hardware vendors make sure that their kit works with Microsoft Windows. Oh, wait .....

    • by Anon-Admin ( 443764 ) on Wednesday February 03, 2016 @05:10PM (#51434237) Homepage Journal

      Ok, I laughed at this one.

      Because I have that same camera and it works perfect under Linux. LOL

      • by Anonymous Coward
        Same here. I also have an old scanner and a USB microscope that Windows shits on when trying to find drivers. Plug them into Linux and they work. Same with some steam games, windows BSODs with WHEA error and reboots. Run them on the Linux steam client and they run all day at full settings. The worst I had to do with hardware/peripherals on Linux was to search google, someone has already figured out a solution. Windows just sucks.
        • by Anonymous Coward

          Same here. I also have an old scanner and a USB microscope that Windows shits on when trying to find drivers. Plug them into Linux and they work. Same with some steam games, windows BSODs with WHEA error and reboots. Run them on the Linux steam client and they run all day at full settings. The worst I had to do with hardware/peripherals on Linux was to search google, someone has already figured out a solution. Windows just sucks.

          Windows doesn't suck you just need to:-

          • Upgrade to Windows 10
          • Use UAC half a dozen times
          • Reboot
          • Understand that their are a small number of device IDs available (for your convenience of course)
          • Recognise that device IDs are incrementally allocated and transient
          • Buy some more recent hardware
      • by Junta ( 36770 ) on Wednesday February 03, 2016 @05:56PM (#51434635)

        There's a crapton of stuff that works only well under Linux out of the box now.

        In our lab, there are like a bucket of USB serial adapters. All of them work with every linux device. But almost none of them work well with windows.

      • by Anonymous Coward

        So there is the solution for using these devices with a modern operating system - switch to linux.
        Apparently, windows support doesn't last. Works in one version, not in the next. Weird, but it is their choice. Linux made a different choice.

    • I have a scanner that I recently needed to get working again. It's a 15 year old scanner. First step I tried just plugging it in to my Windows 10 machine. It didn't work. Wasn't much surprised there. Then I remembered that I used to have it working on Linux. So I booted up a virtual machine with Ubuntu. The scanner was detected but trying to scan an image with XSane just caused it to crash. I might possibly be able to get it working, but didn't want to spend too much time messing around with it. I instal

      • It's hilarious that you mention scanners because basically every scanner I have ever owned (except the first one, and one other... out of about a dozen) has been used. In the only two cases in which I know of why they became available to be, it was because the user had upgraded to a newer version of Windows and the scanner manufacturer no longer provided a driver. In several cases, these were HP scanners which (having checked into the details via the SANE supported list) actually used the same protocols as

  • by Anonymous Coward

    Now with more tech support!

  • Welp... (Score:4, Insightful)

    by Lab Rat Jason ( 2495638 ) on Wednesday February 03, 2016 @04:50PM (#51434025)

    cheap Chinese

    there's your problem...

    • As opposed to what, expensive Chinese hardware?

    • by Khyber ( 864651 )

      Actually, now that I double-checked the company - it's a USA company and has been around since 2003.

      So no, not cheap Chinese crap. Cheap American crap.

      • Why not spit the model and manufacture out? The answer might be something unique to that model. This could be something as simple as a codec package to support H.264 or some USB video class extension which would require vidcap.h so it would need either a driver from the manufacturer or the Windows SDK installed.

        • by Khyber ( 864651 )

          Manufacture? ExcelVan. Model? No fucking clue.

          "This could be something as simple as a codec package to support H.264"

          Not being a UVC 1.0 device, no. That's MPEG/MJPEG. UVC 1.0 has no h.264 support.

          • It's almost as if you are saying the car doesn't start and when asked for details you insist it is red and other red cars start. Either way, it is likely a codec issue or you need a driver.

            But first, the UVC version doesn't necessarily limit the use of H.264 or any other codec. The class extension can enable the support and i picked the h.264 as an example not a diagnostic. It could be any native compression in the hardware and i will have very little clue without knowing manufacturer or model.

            Now on to so

            • http://www.amazon.com/Excelvan... [amazon.com]

              My assumption is that there is a USB1.1 hub built into the glasses, XP doesn't care, but 7 detects it and prevents features from working. Poor design is likely the issue, not actually Windows.

              • If you scroll down to the lower description, it lists "storm codec " under player. Interestingly, the storm codec is a codec package and when 64 bit Windows became available, codecs had issues (the 32bit versions didn't play well in the 64bit version ).

                I would give that a serious consideration. I think your usb error might be ancillary to this.

              • by Khyber ( 864651 )

                There is no USB 1.1 hub as the device transfers files at USB 2.0 speed. Only when switching to camera mode does the device throw up the "This device can perform faster if you connect it to a USB 2.0 port."

                • Inside the device, there could be a hub connected inside the camera to allow the microphone and camera to work, and the storage device could be on a different hub, or even directly connected.

                  Go to device manager, view, devices by connection.
                  Expand out ACPI... (usually), and expand out until you find the USB stuff, and expand those all the way out, then connect the glasses, check how many devices it adds, and how they are wired up.

    • cheap Chinese

      there's your problem...

      Exactly. What he needs is Expensive Chinese (one with a well-known US name on the badge).

  • by Todd Knarr ( 15451 ) on Wednesday February 03, 2016 @04:50PM (#51434031) Homepage

    I've gotten this a lot with devices besides cameras (eg. an LG G3 phone), even when plugged into a 3.0 port. It seems to be caused only by devices with a standard micro-USB connector, not a full-sized one. My thought is that the device's USB chip is 3.0-capable, but the connector and/or cable don't have the extra pins/wires for 3.0 so the device is reporting itself as 3.0 but can only run as 2.0 which makes Windows complain. I haven't seen any problems because of it, even under Windows (I normally connect the devices to Linux machines).

    • by Anonymous Coward

      He's getting the "USB 2.0 device plugged into USB 1.1 port" message, not the "3.0 device plugged into 2.0 port" message.

    • So the solution is to get a USB 2.0 ONLY add-in card.

      Or a USB 2.0 ONLY hub.

    • by AmiMoJo ( 196126 )

      This is almost certainly the OPs problem. On XP the timing requirements for USB 2.0 devices were a bit more relaxed and out of spec devices worked. USB 3.0 drivers are even stricter.

      I can only suggest trying a few USB 2 cards, but it's a long shot.

  • by celeb8 ( 682138 ) <`moc.liamg' `ta' `8belec'> on Wednesday February 03, 2016 @04:54PM (#51434083)
    yes this forum is totally windows tech support I just hope your post feels welcome
    • by Khyber ( 864651 )

      Actually, turning it on and off again because of USB enumeration issues was one method of fixing UVC camera issues that was mentioned in my searches for the cause of the issue.

      Sadly, it did not work.

  • by Anonymous Coward

    have you tried running the consumption (camera) apps in XP compatibility mode?

    • by wjcofkc ( 964165 )
      Not helping.
    • by Khyber ( 864651 ) <techkitsune@gmail.com> on Wednesday February 03, 2016 @06:24PM (#51434817) Homepage Journal

      There are no consumption applications for the camera. If there were, I'd have mentioned trying them and them not working.

      Don't you find it the least fucking bit odd that a camera made in 2015 will work with XP, works under Linux, Even works in OSX 10.4 or higher (I checked) yet it won't work in Windows 7?

      I suspect the UVC driver has changed between XP and 7.

      • > Don't you find it the least fucking bit odd that a camera made in 2015 will work with XP, works under Linux, Even works in OSX 10.4 or higher (I checked) yet it won't work in Windows 7?

        After a decade plus of supporting Windows PCs, I ceased to find any Windows behavior odd. Windows is a humongous, amorphous, poorly documented, blob of code, trying to be all things to all people. I can't see any evidence that anybody inside or outside Microsoft understands it, and I can't think why anybody with a choi

  • by OzPeter ( 195038 ) on Wednesday February 03, 2016 @05:09PM (#51434223)

    Once you get the right cable [arstechnica.com] you won't have to worry about your camera issues anymore!

  • get the hardware id's from device manager, and check www.pcidatabase.com
  • by abelenky17 ( 548645 ) on Wednesday February 03, 2016 @05:16PM (#51434289)

    By not posting stupid tech-support questions... some random guy's hare-brained scheme... or pseudo-science that isn't backed up by common sense.

  • by Billly Gates ( 198444 ) on Wednesday February 03, 2016 @05:25PM (#51434365) Journal

    Dude in 2015 you bought a device that only works on an unsupported 15 year old obsolete and now dangerous OS for internet streaming??! Seriously

    If the camera was from the XP era I could understand. If you want to keep it then get an ancient XP box and DMZ the LAN behind a firewall to prevent internet access. But if you purchased this to use over the internet then the manufacturer gave you a shoddy and liable product that is negligent.

  • Actually no, not welcome. I'll bet there are some great Windows tech support related sites out there. Maybe start here:

    https://technet.microsoft.com/... [microsoft.com]

    Or more likely here:

    https://www.google.com/ [google.com]

    So there's your advice.

    I was going to take the opportunity to launch into a full tech-support monologue but it brought back too many old and bad memories.
  • by dstyle5 ( 702493 ) on Wednesday February 03, 2016 @05:30PM (#51434419)
    By using let me google that for you.

    http://lmgtfy.com/?q=let+me+google+that+for+you

    If that doesn't work maybe someone has a GeoCities site about this issue.
  • In these parts, 'Khyber' is CRS for 'arse'. Also on /. it would seem.

  • Just ask this nice lady:

    https://www.youtube.com/watch?... [youtube.com]
  • I wonder if there's an inverse version of shibboleet [xkcd.com] that would be helpful when newbies ask for support in knowledgeable forums.

  • by Anonymous Coward

    Can anyone help me get this WinModem working under linux?

    • by Khyber ( 864651 )

      You don't know the Modem AT commands by heart? Who needs drivers when you can talk directly to the hardware, like one would do in DOS?

      • You can't talk to a Winmodem with AT commands - it's basically just a DAC/DSP where the driver itself implements all the modulating, and demodulating. The hardware can basically just open or close the PSTN connection and make/receive sounds. Everything else is software.

  • 32bit Windows version might have a bit better luck, you might try running an XP driver under 7 32bit although playing with the USB stack or an on-board USB controller in that way may be ugly or bork things horribly.

  • by Barlo_Mung_42 ( 411228 ) on Wednesday February 03, 2016 @06:25PM (#51434821) Homepage

    Windows 10 probably fixes this.
    I'd just go ahead and upgrade if I were you.
    Couldn't hurt...

    • by Khyber ( 864651 )

      Guess what?

      32-bit Win10, works flawlessly.
      64-bit Win10, 66% functional (mass storage and microphone work.)


  • I went back through the archives to read Roland Piquepalle's last 50 posts to cleanse my brain from this level of Zika virus induced retardedness.
    • by Khyber ( 864651 )

      So, you just admitted that you couldn't understand an implied low-level technical question for what is likely involving one of the lower-level Windows subsystems (and not a driver issue) and had to read RP garbage to clean it out?

  • I've had similar issues with flash drives. I'm one of those nerds who like to load external hubs with older flash drives and thrash them until they die. Thing is, they all need power. USB2 spec is 0.5A per port, but if you're running a passive hub off one port, each port on that hub has to share the power available. Eight hub ports splitting that half an amp can get a bit tricky, especially on USB2. Usually what happens is it hits a low threshold and drops to USB1.1 which requires less power to run.

    On the s

  • You actually did a decent job. I hadn't had much coffee when I wrote that.

  • User Grog6 noted that it would likely work in 32-bit Windows 7 and fail to work entirely under 64-bit Windows 7.

    This ends up being correct. There is something off between the 32-bit and 64-bit usbvideo files that makes this particular set of camera glasses not function 100% under 64-bit Windows.

    Now for the fun part: figuring out whether or not the difference is so drastic that I can't hack in the missing code, and whether or not I can fake the Microsoft driver signature so WFP doesn't flip its lid (and I'm not going to turn WFP off, sorry!)

  • ..not buying Chinese crapware?
  • ...who are complaining that Khyber's question/post is stupid, etc -- YOU ARE THE PROBLEM,
    *NOT* KHYBER. Slashdot used to be a valuable resource for questions like this. Try and Contribute something useful to the discussion IF you have any knowledge worth sharing, or feel free to go elsewhere and post your useless whinging somewhere else. This falls under "Stuff that matters."

    --Even tho I don't have any skin in this game, I learned something useful reading the responses that actually tried to help the guy

"I shall expect a chemical cure for psychopathic behavior by 10 A.M. tomorrow, or I'll have your guts for spaghetti." -- a comic panel by Cotham

Working...