https://bugs.kde.org/show_bug.cgi?id=407778
--- Comment #2 from Robert <rob...@robertelder.org> --- (In reply to alcinos from comment #1) > Disclaimer: I haven't looked deep into that yet. > I just want to point out that if showing a red producer with melt doesn't > work for you, there is a stream of things that may break, since your melt > installation seems broken. We need to make sure the simple things work > before attempting more complex ones. > > Maybe you can try to build melt from source, and install it with sudo make > install (make sure to uninstall any previously installed version / package), > and report what happens when you try to output the red consumer. Hi alcinos, thanks for your response. I did (on at least one occasion), build melt from source and actually sudo make install it. I think I did that with v6.16? Same result when playing video/color:red. Having said, that, there are a lot of dependencies that the 'melt' executable relies on and I'm not 100% sure I uninstalled all its dependencies. Therefore, I did what I figured would be a stronger test which is build melt in a directory in /tmp/, and then do '. setenv' to let the mlt package do whatever it does to set paths, and then test the local melt executable that way without install. Same result. Here is the bug I filed for melt: https://github.com/mltframework/mlt/issues/445 Dan Dennedy suggested that perhaps there is an issue with my SDL2 (a dependency of mlt?). Even if that's the case, I would argue that kdenlive should be smart enough to detect this subtle corruption condition and at least issue warnings to the user for this situation where, clearly, an unmodified project file will have its track lengths changed without any modifications to the project. In such a case, regular warnings that say something like 'Warning: track length changed' might arouse suspicion and make it a bit faster to track down bugs. As of this time, I am not aware of any action item I can take to further assist in fixing this issue. The mlt bug I filed has been closed, and I don't know enough about SDL2 or how it interacts with mlt to know what to investigate there. Please suggest further courses of action. -- You are receiving this mail because: You are watching all bug changes.
