Closed rse closed 3 years ago
Is this naming of the devices intended? If I start from scratch (all uninstalled), shouldn't the result be ALWAYS the numbering 0/1/2?
Yes, this is a known bug, when deleting the old devices, it's not deleting the files properly, that's the reason because it returns pseudo-random identifiers.
If the assignment of the device names and their numbers is expected to be not fully deterministic, would it be possible to allow the AkVCamManager commands to alternatively also accept the device description and automatically map to the device name? Perhaps if an extra option like -d (for "description") or -m for (for "mapping") is specified, the DEVICE argument is treated as a DESCRIPTION and automatically mapped?
Yes, If it's not much problematic and don't take much time I could add that feature before the final release.
The virtual camera numbering was fixed in the latest commit. I'll try to add a flag for setting the device id, and that's all, no more features for now.
And it's done, custom devices ID feature added and documented. Closing.
I would like to create a Windows application which (with the help of the following batch script
AkVCamAssistant.bat
and INI fileAkVCamAssistant.ini
) initially allows the creation of 3 virtual camera devices and later allows to destroy them again:Unfortunately, when running
AkVCamAssistant.bat install
I always get the three devices, but aAkVCamManager.exe devices
shows that the naming of the devices seems to be non-deterministic. Sometimes I get 0/1/2, sometimes 1/2/5, sometimes 1/2/3, etc. In my last attempt I received:This would be harmless if the other
AkVCamManger.exe
commands would not expect the device name and instead could also accept the device description (the logical name). As a result, my application first would have to map from the fixed device description to the assigned device names. Especially theAkVCamManager stream
command expects the underlying particular assigned device name.My questions are now:
AkVCamManager
commands to alternatively also accept the device description and automatically map to the device name? Perhaps if an extra option like-d
(for "description") or-m
for (for "mapping") is specified, the DEVICE argument is treated as a DESCRIPTION and automatically mapped?