The Trim Section Left shortcut (Ctrl+,) is not functioning properly, and once modified, cannot be reset to (Ctrl+,).
The Trim Section Right shortcut (Ctrl+.) works correctly, but after being modified, it also cannot be reset to (Ctrl+.).
1.You can quickly create two sequencers, drag Sequence B into Sequence A, and then test the shortcuts mentioned above. Only (Ctrl+.) works, while (Ctrl+,) does not. Using relevant tools to check, it was confirmed that these two shortcuts are not occupied by the system.
2.Open the editor settings and try to modify the key bindings for the two shortcuts above. You will find that they cannot be changed back to the original shortcuts (i.e., Ctrl+, and Ctrl+.).
Thanks for the report. I tested this in a blank project using UE 5.7.1 (Launcher) on Windows. With the default key bindings, both Trim Section Left (Ctrl + ,) and Trim Section Right (Ctrl + .) work as expected when nesting one sequence inside another in Sequencer.
[Image Removed]Regarding your second point, I was also able to change the key bindings for both actions to different shortcuts, confirm that the new bindings worked correctly, and then restore them back to the default values (Ctrl + , and Ctrl + .) without any issues. After resetting them, the shortcuts continued to behave as expected.
Based on these results, I was unable to reproduce any of the issues you mentioned with the Trim Section shortcuts.
Have you been able to reproduce this in a blank project as well? If so, could you share any extra details that might help reproduce this on my end?
After reinstalling the system, I found the situation had improved. Only Ctrl+Period was still working, but I couldn’t reset it. Then I noticed that other software also couldn’t be set back. As a result, I discovered that this was caused by the default shortcut key of Microsoft Pinyin Input Method. I set it to “none” and everything is working fine now. Thank you for your help.
Thanks for the update, [mention removed]. Glad to hear the issue was resolved on your end and that it turned out to be an OS-level shortcut conflict rather than an engine issue.