Closed BlueprintBen closed 2 years ago
Hmm interesting.....I'm not sure if this is a bug or not but we'll investigate...
Yeah was a weird one. Maybe it's mis-handling a null response for GUID and ends up reusing the last ID or causing the indexes for GUIDs be off or something. I'd obviously much rather if we don't know a GUID that it just returned empty or the name instead of introducing a weird interaction with other HW. Thanks!
Hmm that's strange.. Which version of OBS etc are you using? I'm using OBS Studio 25.0.1 and OBS Virtual Cam 2.0.4 and XSplit Vcam 1.0.2003.301
I tested with those and the GUID enumeration worked for me....
I had just updated Vcam to latest. OBS Virtual Cam probably a bit older. But from memory this was not an issue until I plugged in my Decklink 8K Pro card (even when I had a Decklink 4K Mini installed). I've been testing the AVProDecklink plugin in conjuction; I should have mentioned that the plugin is actually imported in the project I've been testing with, but not activated with a DecklinkManager in the scene. I suppose that could factor in somehow.
I should have time this week to try out the same test in other HW configurations (no Decklink, other Decklink) and in a clean project rather than my working one. My apologies for firing this up before having collected that data as well!
The issue I'm seeing is around the ability for AVProLiveCamera to report a GUID for a device, specifically some software devices. Rather than an
@device:sw:
style GUID, the plugin reports one of the Decklink profile names, and in the other, the device name was a DecklinkTo Reproduce
Note the enumerated device information in the Unity Console Log.