FWIW, linear 10bit GPU/CPU processing mode, Rec.2020.
Another small glitch is that after deselecting a clip that has the filter added, and then selecting it again, previously selected preset is retained, but presets dropdown doesn’t show the selection anymore.
That is normal and by design. Once you change any little thing, the parameters no longer match the preset. Thus, it is incorrect to show it. So, Shotcut does not even bother to try to show it–again, by design.
I have not been able to reproduce the main bug with Linear 10-bit CPU or GPU. I tested with both full and limited color range video file. And tested on a clip in Source as well as Timeline. I suggest you to try it again and by itself, not in an existing project.
Hello @shotcut, sorry for slow response. After some research figured out that this happens if there are other filters added to the entire track. Adding the same filters to a specific clip doesn’t trigger such effect; also, not all filters cause that: among GPU-enabled LUT, crop and size/position don’t, all others do.
Thanks, I see it now. It occurs with all of the GPU filters except Crop: Source and Size & Position, but none of the CPU ones, added to the track as you noted. The problem is not limited to GPS Graphic on the clip either. It occurs with any non-GPU filter on the clip. This is likely related to a change in 25.12 to keep video from the GPU stage in linear color with a linear-to-gamma conversion at the end of the CPU stage for a full linear processing pipeline.
There is already a 26.1 BETA with a release by the end of the month, but it does not have this fix. I will post the link here tomorrow in case you or someone else wants to try it.