These are two screenshots from the same clip. The original clip is completely consistent in terms of luminance. This is the unedited clip, with no color grading / luminance adjustments.
The luminance just abruptly changes for no reason mid-clip. I’ve had this happen before, but deleting and re-importing the clip, and/or restarting Shotcut has always fixed it. But not this time. I even converted the native .MTS file to .MKV, then .MP4, with no luck. I edit .MTS files all the time with no issues and in this video project, for whatever reason, this clip is having this issue and I can’t seem to fix it no matter what I do.
I’ve included snapshots of the RGB parades to further clarify this change in luminance. This is with no color grading or any filters applied at all. What’s also weird is splitting the track just before the luminance change causes the luminance change to just take place earlier, like chasing a bump in the rug.
Tried uninstalling and reinstalling Shotcut, updated to the newest version, deleted and reimported the original .MTS file, but no cigar.
So, interesting development: blank project with the same .MTS file didn’t have any issues. For some reason, deleting a couple unused video tracks seemed to get rid of the problem. There was nothing at all on the tracks.
But there was another oddity: I tried re-importing the .MTS file, and it worked for a little while without issues. But then when I moved it over the corresponding voiceover .WAV file I recorded (on the audio track below it), it started developing the bug again, and would just change luminance out of nowhere. By moving it, I simply mean moving it left on the timeline. No cross fading, no interaction with any other clips, just moved it time-wise. And that triggered the issue again.
So far, for now, it seems to have been fixed by deleting the unused video tracks. There was one unused audio track as well.
So it appears the original .MTS file is fine. I wonder if it’s the complexity of the project that just resulted in a bug, though I do find it very odd that the bug didn’t go away upon reinstalling Shotcut and even restarting my computer. Usually these little glitches go away with a refresh.
For reference, this is the video project in its current entirety. Nothing too crazy. But there is a lot of footage. It’s all 1080p by the way, no 4k, and I am not using Proxy editing.
But again, happy to report that the issue seems to have been solved by deleting a couple unused video tracks, which I may have inadvertently created by dragging clips onto the timeline above the tracks I had already made.
Still, it shouldn’t cause an issue like that, but for some reason, deleting those extra tracks seems to have fixed the problem.
