You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a bug where changing the Compositor plugin resolution using the web UI would not work for e.g. changing to resolution "720p50Hz".
I found the reason for this is the compositor resolution strings listed in the dropdown menu in the web UI still use the "Hz" suffix. However, the compositor resolutions (specifically the enum to string conversion) defined in Thunder Interfaces (Definitions.cpp) had the "Hz" suffix removed in rdkcentral/ThunderInterfaces@9d15587
To fix this bug, I removed the "Hz" prefix from Compositor resolutions in ThunderUI sources: dist/bundle.js and src/js/plugins/compositor.js.
The text was updated successfully, but these errors were encountered:
laurence-ejraee
changed the title
R4.3 Compositor resolutions do not match other Thunder packages
[R4.3] Compositor resolutions do not match other Thunder packages
Aug 8, 2023
laurence-ejraee
changed the title
[R4.3] Compositor resolutions do not match other Thunder packages
[R4.3] [UI] [Interfaces] Compositor resolutions do not match other Thunder packages
Aug 8, 2023
I have encountered a bug where changing the Compositor plugin resolution using the web UI would not work for e.g. changing to resolution "720p50Hz".
I found the reason for this is the compositor resolution strings listed in the dropdown menu in the web UI still use the "Hz" suffix. However, the compositor resolutions (specifically the enum to string conversion) defined in Thunder Interfaces (Definitions.cpp) had the "Hz" suffix removed in rdkcentral/ThunderInterfaces@9d15587
To fix this bug, I removed the "Hz" prefix from Compositor resolutions in ThunderUI sources: dist/bundle.js and src/js/plugins/compositor.js.
The text was updated successfully, but these errors were encountered: