XDD modules as "dynamic" device modules
marting
Junior Member
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)
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)
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums