Reply to Message

View discussion in a popup

Replying to:
peterbrown05
VMware Employee
VMware Employee

Hi,

so we have tested with this device many times, so I am quite familiar with it. but, if you look in the view client DEBUG logs when you click on the usb device menu you will see something like the following in the logs:

Filter Result: [UsbDeviceId: 4000001b0911149a] On enumeration of device: 2/4. Name: Philips USB Composite Device

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] IdentifyDeviceFamily(): Not implemented on Windows

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] Device Speed from backend: 02

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Device Speed = Full

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] LookupDeducedFamily(): Called for non vendor specific

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Device Filter got device:

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Device id: Vid-0911_Pid-149a

2013-06-20T09:34:32.443+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Path: bus-1/1/0_port-06

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Config count: 1

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Config num: 0

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface count: 5

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [0] - Family(s): audio

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [1] - Family(s): audio,audio-in

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [2] - Family(s): audio,audio-out

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [3] - Family(s): mouse

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [4] - Family(s): hid

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Starting 1(a)

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Finished 1(a)

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] AutoDeviceSplitting blocked. Skipping 1(b)

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Starting 2

2013-06-20T09:34:32.453+02:00 DEBUG (0D34-0D4C) <vmware-usbd> [vmware-view-usbd] DevFltr: audio-out is blocked using AutoFilter setting. The setting is ignored as there are multiple audio interfaces which shouldnt be split


the key being the Interface[0]...interface[4] and you can see that the interface 3 is the mouse. Note; you should *never* split audio in and audio out - they should either both be on the client or both on the guest.


I'm actually busy writing a deep dive paper on all of this, but not sure when it will be available - soon hopefully!.



As for your observation that the device name changes, then this I believe is a known issue, which I think there is a fix coming out for in a future client release. It doesnt affect operation though - just the UI.


hope this helps,

cheers

peterB