XDD modules as "dynamic" device modules

We are currently using Duet (jar) modules via the "dynamic" device mapping that's available within the web interface of the masters to make it easier to switch to different display/switcher/etc. modules (no code change / reboot).

Wondering if it is possible to use XDD modules in the same fashion? Has anyone done this?

For reference, here is an example of how we are defining these in code:

STATIC_PORT_BINDING (
vdvDISPLAY_1,
dvNI_232_2,
DUET_DEV_TYPE_DISPLAY_DEVICE,
wm_RMS_NAME_PREFIX_VIDEO_DISPLAY,
DUET_DEV_NOT_POLLED)
Sign In or Register to comment.