The fewer issues I have to read, the more new features I will have time to implement, so I ask that you please try these things first
Operating System
MacOS 15
Steps to reproduce
I actually don't know how I got into this issue but maybe figured a way out.
Seen issue:
- I daily use Lossless Cut in advance mode, and I create new segments, type in via keyboard the in and out timecodes, and do it over and over. Either I clicked something or did something, and when I entered the IN time code number, when I taped or clicked out of that field, it would revert to 00:00:00:00.
a. Know issues: The OUT time code has to be later than the in or similar behavior can be seen BUT this was not the case as the OUT Time code was always at the end 00:18:00:01
b. Fixes I tried.
- Deleted all segments, but then I was in "maker" mode which I never could escape.
- Deleted all Lossless preferences at OS level.
- Re downloaded software both from Mac Store and Github
- Re-Downloaded software all the way back to 3.61.1 - Same issues
- 3.59 which was on my computer never had this issue.
Fixes that worked:
- I pressed the Yin-Tang symbol twice and things seems to return to normal.
Expected behavior
Type in the time code for the IN field.
Tab or click out of the field.
Cursor jumps to the in Time Code.
Actual behavior
Time code reverts back to 00:00:00:00
Share log from developer tools
No response
The fewer issues I have to read, the more new features I will have time to implement, so I ask that you please try these things first
Operating System
MacOS 15
Steps to reproduce
I actually don't know how I got into this issue but maybe figured a way out.
Seen issue:
a. Know issues: The OUT time code has to be later than the in or similar behavior can be seen BUT this was not the case as the OUT Time code was always at the end 00:18:00:01
b. Fixes I tried.
Fixes that worked:
Expected behavior
Type in the time code for the IN field.
Tab or click out of the field.
Cursor jumps to the in Time Code.
Actual behavior
Time code reverts back to 00:00:00:00
Share log from developer tools
No response