Bad video-quality on Webcam (Slow USB?)

[ronnys]

VB-Host: OpenSUSE 13.2 64bits KDE (HP Elitebook: Intel i7 vPro and 8GB RAM, AMD Radeon HD 7500M w/1GB Video-RAM)
VB-Guest: Windows 10 Edu 64bits(1 core, 2GB RAM + 256MB Video-memory and 3D enabled)
VB: ver.5.0.10

I have connected a Microsoft LifeCam Studio 720p to an USB and enablet it in Win10. It detected the camera and everything seems to work fine. The problem is the video is broken. It takes a long time before some picture shows up and its out of sync.
My tought is that the USB-speed is very slow.

Anyone manage to get a USB-webcam to work fine in Linux/Win-setup?

I need this to work since i'm required to use Skype for Business.

[unixabg]

Greetings,

I can confirm similar issue on multiple hardware configurations and two VBox versions:

VB Host: Debian Jessie
VB Guest: Win7
VB Version: 5.0.14 and 5.0.4

On 5.0.4 video was just garbled colors and on 5.0.14 video is garbled but you can see blocks of the image jumbled/garbled.

Hope this helps.

[mpack]

Minimum information needed for assistance.

Start by posting a VM log file: with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[unixabg]

Greetings,

Thank you for pointing out the Minimum information needed for assistance.

1. VBox version 5.0.14 and yes the Guest Additions is installed in the guest.
2. Host Debian Jessie with 8gb mem and Host Win7HomePremium 32bit with 1536mb
3. Attaching VBox-5-0-14.zip log file.

Thanks and any ideas welcome. Also fwiw, the camera worked before on VBox 4.3.6 with the same setup.

[mpack]

I don't see anything obvious in the log.

You have allocated 2 CPU cores to the guest, which leaves nothing for your host, which could affect the performance of the host. I would reduce the guest vCPU count to 1.

RAM and VRAM looks ok.

Next, I see that you're using the Debian fork of VirtualBox. We can only support you here on the VirtualBox forums if you are using VirtualBox, not someone else's respin on it. You should either install the offical version from the Downloads area here, or go to the Debian forums for any further support you need.

[michaln]

Thanks and any ideas welcome. Also fwiw, the camera worked before on VBox 4.3.6 with the same setup.

That's miles away from 5.0.14. Can you find out more precisely when this use case started misbehaving? Please start with the latest 4.3.x update, or check 4.3.14.

[unixabg]

Greetings,

I don't see anything obvious in the log.

You have allocated 2 CPU cores to the guest, which leaves nothing for your host, which could affect the performance of the host. I would reduce the guest vCPU count to 1.


RAM and VRAM looks ok.

I show 4 CPUs in settings and 2 to the VM. But I do not think this is the issue.

Next, I see that you're using the Debian fork of VirtualBox. We can only support you here on the VirtualBox forums if you are using VirtualBox, not someone else's respin on it. You should either install the offical version from the Downloads area here, or go to the Debian forums for any further support you need.

I do understand and I do appreciate the support here. Hence I will submit some logs of official VirtualBox on the next response. And it is my intent to switch to official VirtualBox from here forward.

[unixabg]

Greetings,

Thanks and any ideas welcome. Also fwiw, the camera worked before on VBox 4.3.6 with the same setup.

That's miles away from 5.0.14. Can you find out more precisely when this use case started misbehaving? Please start with the latest 4.3.x update, or check 4.3.14.

Please know I really appreciate the help and I am more than glad to help on finding the issue. So I worked backwards today and VBox version 4.3.12r93733 everything works perfect. The next version of VBox version 4.3.14r95030 it stops working. I am attaching the logs from both version on this post.

fwiw: On version 4.3.14r95030 the image is garbled but there (sort of). However on a later version like say 4.3.36-r105129 you can not see any part of the image, just garbled colors.

Again I really appreciate the help on the forums and I have switched to official VirtualBox for tracking down the issue.

Please advise.

[michaln]

Thanks. There were pretty significant changes to USB in 4.3.14... although they were meant to improve things, not make them worse. But it's good to know that that's where things stopped working.

Alternate suggestion: Have you tried USB 3.0 (xHCI) emulation with VirtualBox 5.0? It might work better.

[ronnys]

Hi!
I testet now with USB 3.0 activated. Yes it works for me

RS

Thanks. There were pretty significant changes to USB in 4.3.14... although they were meant to improve things, not make them worse. But it's good to know that that's where things stopped working.

Alternate suggestion: Have you tried USB 3.0 (xHCI) emulation with VirtualBox 5.0? It might work better.

[unixabg]

Greetings,

Thanks. There were pretty significant changes to USB in 4.3.14... although they were meant to improve things, not make them worse. But it's good to know that that's where things stopped working.

Alternate suggestion: Have you tried USB 3.0 (xHCI) emulation with VirtualBox 5.0? It might work better.

I tested on my development system with Oracle VirtualBox 5.0.14 and it does work fine. I will try to test on some other hardware setups to see if all well on that. Will do my best to report back.

Do you think this worthy of a bug report or do you believe there to be a report already submitted? Maybe related to https://www.virtualbox.org/ticket/13728

Also please know that I really appreciate the support provided by the forum.

[michaln]

At the moment I'd say a bug report isn't necessary. The code is being worked on already.

[ronnys]

After enabling USB3.0 the video fra web-cam is working greate, men the whole system is slow as h.....
It seems like networking is affected. Skype4B is dropping in and out. Remote Desktop is crap. This happens after enabling USB3.

Maybe som more/new bugs?

RS

At the moment I'd say a bug report isn't necessary. The code is being worked on already.