Is there an equivalent to v4l2loopback's "video_nr" driver parameter? about akvcam HOT 11 CLOSED

You could resolve this by creating a fixed symlink using udev matching the camera\#\description with ENV{ID_V4L_PRODUCT}

from akvcam.

@fangfufu

How comes?

I need the devices to be predictable so I can simplify my waitForDevices function, instead of waiting for all v4l2 devices created by all drivers and then waiting for the same number of devices to appear, I can wait for the specific devices to appear. I did not figured out at beginning 😅

from akvcam.

No, I prefer to let the kernel decide which number corresponds to each device, this way it avoids collisions with other drivers.

from akvcam.

But that way it messes up the order of my webcams. :(

from akvcam.

Not sure if I want to do that way, I think it will cause more problems than solutions, let me think it.

from akvcam.

Personally, I think it is would be a nice to give users the option to specify things. You can leave the default behaviour as it is.

The only reason I opened this ticket is because I hardcoded the webcam path in some of my scripts... lol.

from akvcam.

At the end I'll have to implement this, this could be useful in the future.

from akvcam.

At the end I'll have to implement this, this could be useful in the future.

How comes?

from akvcam.

I've implemented this in the latest commit.

from akvcam.

Cool! I will close the issue for now. :)

from akvcam.

instead of polling for the devices, you should listen to the relevant udev "ADD" events.

from akvcam.