Feature Request — Allow the D200 Window Button to Be Customized as a Normal Key
The D200 Window button is currently limited to clock/system information displays. It would be very useful if Ulanzi Studio allowed users to switch this button between “Window Mode” and “Custom Key Mode”, allowing Hotkeys, Multi-Actions, OBS actions, plugins, etc. to be dragged onto it just like the other LCD keys.
I’m developing a Windows plugin for the Ulanzi D200X using the official UlanziDeck Plugin SDK and Ulanzi Studio 3.1.9.
The plugin controls Windows volume through the three rotary encoders. It works correctly when using the built-in $UA1 encoder layout. However, $UA1 limits the artwork to a 100×100 icon area with margins and a separate title strip.
I attempted to use a custom 126×140 encoder layout to make better use of the available display area. The custom layout appears correctly in Ulanzi Studio, and the plugin continues receiving encoder events, but the corresponding area on the physical D200X remains completely blank.
I tested the following:
A manifest-declared custom layout.json
A 126×140 full-canvas pixmap
Explicit setFeedbackLayout("layout.json") calls
Complete data:image/svg+xml;base64,... image data
A square 144×144 transport image, matching the format used by Ulanzi’s clock example
Image updates with and without a separate text/title layer
Removing and re-adding the action after restarting Ulanzi Studio
The custom layout consistently works in the Studio preview but not on the physical device. Switching the same plugin back to $UA1 makes it display normally.
Could you please clarify:
Does the D200X firmware currently support custom 126×140 layouts from third-party encoder plugins?
Is setFeedbackLayout supported for Node-based main-service plugins?
Is there a required image format, layout structure, firmware version, or API call that is not documented?
Is the larger Clock display using a private or device-specific API unavailable to third-party plugins?
Is the 100×100 $UA1 icon region currently the maximum supported area for third-party encoder artwork?
I can provide the experimental plugin package, source code, screenshots, logs, device firmware version, and a minimal reproduction project if needed.
Hello, sorry for the oversight. Thank you for the feedback. This requirement has been submitted to the product team. It will be evaluated in the upcoming major version planning.
I’m developing a Windows plugin for the Ulanzi D200X using the official Ulan ...
Hi,
We encountered a similar issue on the D200X. As a workaround, please keep an additional empty text element alongside the pixmap, using a custom key rather than "title":
{
"type": "text",
"key": "empty-label",
"enabled": false,
"rect": [0, 105, 126, 35],
"zOrder": 1,
"text": ""
}
复制代码
In our testing, retaining this element allowed the image to display on the physical device. Please try this first and let us know whether it works on your setup.