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
Describe the bug
When dealing with raw RGB files and choosing Custom... RGB Format, it sometimes locks the list on that option.
To Reproduce
Steps to reproduce the behavior:
Open a new instance of YUView
Import a RGB sequence
Choose RGB Format from the list as Custom..., then change bit depth from (default) 1 to 8 and press OK
The RGB Format list is showing Custom... (not RGB 8bit)
After that, sometimes the list does not want to open at all. Or if it opens, the "Custom RGB Format" window is not opening, when choosing Custom... from the list.
It is not the only way to reproduce this, it also happens when steps 1-3 are different. Especially when dealing with more items on the playlist.
Expected behavior
The RGB Format should not lock on Custom....
Workaround
Choosing a different RGB format before retrying with Custom... works from time to time (if the list is still opening).
Screenshots
Version
OS: Windows Server 2022 (OS Build 20348.1726), Windows 11 (OS Build 22621.3007) - happens regardless
Version: v2.14 (an MSI installer from Releases)
The text was updated successfully, but these errors were encountered:
Describe the bug
When dealing with raw RGB files and choosing
Custom...
RGB Format, it sometimes locks the list on that option.To Reproduce
Steps to reproduce the behavior:
Custom...
, then change bit depth from (default) 1 to 8 and press OKCustom...
(notRGB 8bit
)Custom...
from the list.It is not the only way to reproduce this, it also happens when steps 1-3 are different. Especially when dealing with more items on the playlist.
Expected behavior
The RGB Format should not lock on
Custom...
.Workaround
Choosing a different RGB format before retrying with
Custom...
works from time to time (if the list is still opening).Screenshots
Version
The text was updated successfully, but these errors were encountered: