https://bugs.kde.org/show_bug.cgi?id=508759
--- Comment #5 from Uwe Dippel <[email protected]> --- Thanks for your reply! Now the matter becomes clearer, I hope. I should start by saying that I rendered a good thousand files during the last 7 years with kdenlive, out of which several dozen didn't render properly due to reception errors resulting in encoding issues. Until here, they became visible by a rendering speed of 1 fps and even lower. In all cases graceful degradation. This actual clip, however, behaves differently. I have by now tried the same .ts sources with 23.08.5 on ubuntu 24.04 instead of fedora 42. And the result is identical. While the file loads in the project bin, shows the content of the video track which can be edited, together with the audio track, without problem, it stops at some moment at rendering. It plays a resulting file including audio, but with video completely in white. When reloading kdenlive and the project, identical to what I observed in 25.08.0 on fedora, everything loads properly, except of the video track in the timeline. It likewise loads, but all white. You are right, of course, that it is an encoding error of the source file. Though it is the first time, that certain items, defects of the source data, taken together, produce this outcome. I would still consider it a tiny-tiny bug, pointing to a weak point of kdenlive, since the saved, and reloaded, project file (foo.kdenlive) doesn't reconstruct the same state when saving it. Because when saving, the video track was visually okay, with visible video content. Saved and reloaded, the video track is all white. On the screen, the Clip Monitor shows, and plays, the file in the project, allows scrolling it, everything. While the Project Monitor, different from the moment when creating the project, shows an all white track. (I'll attach a screen shot of the reloaded project, to hopefully make things easier to understand.) (Could it be that the second part of your reply refers to my other report, on audio dropouts when loading individual sequences of longer clips as 0000.ts, 0001.ts, 002.ts one by one into the timeline? That is completely different and has nothing to do with this report. Here the source is a singlular .ts file of around 8 GB. And while those audio drop outs have occurred in all my previous renditions of this data source at merge points - therefore easily reproducible - here it is a singular, comprehensive source file that sends kdenlive into nirwana.) -- You are receiving this mail because: You are watching all bug changes.
