This message was deleted.
# helpdesk
s
This message was deleted.
c
Maybe the comment in the code isn't an accurate description of what it is doing.
I'm trying to understand why livekit consistently acquires a device that isn't the top-listed device, since the device enumeration list order is significant.
For now I can just grab the first item in the list and use its device id to constrain the initial video choices, but I don't entirely understand why it has to be this way.
p
hi @colossal-midnight-90599, a previous approach taken by the js-sdk was to try to filter out the duplicate
default
device. We removed that filtering logic and are now also returning the default device that chrome displays by appending
(Default)
to the device label. Does this also happen to you on example.livekit.io?
c
@polite-kilobyte-67570 Yes, it's identical behavior.
I haven't dug into the livekit code enough to figure out how it's picking but maybe I'll try to do that next. In this particular case, there's no entry for "default" for video on my system being returned by the browser.
(not sure if that's ordinary or not, but it has nothing to do with livekit in any case)