Rendering of /Volumes/Small_HD/YouTube-Uploads/3.mp4 crashed Detected locale "C" with character encoding "US-ASCII", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. [mp4 @ 0x7fd01694ff40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0x7fd01694ff40] Encoder did not produce proper pts, making some up.
I am running Kdenlive version 24.08.2 on macOS 12.6.6 (Monterey) and in my case, the two errors are caused by different settings. 1. Detected locale "C" with character encoding "US-ASCII"... This error occurs when the typewriter effect is enabled on a title clip. By the way, I have no idea how to set the locale. No matter what I add to my BASH settings, it doesn't help. 2. Timestamps are unset in a packet for stream 1. This is deprecated... This error occurs if the rendering option labeled "Overlay" is left at its Default setting. Setting it to any other option let's the rendering process finish without this error.
That means we have 2 bugs here: 1. Title typewriter is not correctly set to UTF-8 2. Rendering: If "overlay" is let on default, then UTF-8 is not set correct. Is my understanding correct?
I have the same issue out of the box on 24.08.03 Kdenlive and the daily build I don't have any title clips in my video, tried setting the overlay options to anything else - no effect
(In reply to emohr from comment #2) > That means we have 2 bugs here: > > 1. Title typewriter is not correctly set to UTF-8 > 2. Rendering: If "overlay" is let on default, then UTF-8 is not set correct. > > Is my understanding correct? I think its the user's *systems* that are not configured to use (or able to use?) a UTF-8 locale. The typewriter shouldn't be messing with that at all, but there appears to be some conflict with Qt and the system using a non- UTF-8 locale. Which if that is a hard dependency for current Qt probably isn't something we can fix (or anything we are doing wrong). Users having this problem will need to ensure they have a UTF-8 locale available or (probably preferably in the modern multi-lingual world) set as the default on their system. The "Timestamps" warnings are just warnings and cause no problem, they are a red herring here.
(In reply to Ron from comment #4) > (In reply to emohr from comment #2) > > That means we have 2 bugs here: > > > > 1. Title typewriter is not correctly set to UTF-8 > > 2. Rendering: If "overlay" is let on default, then UTF-8 is not set correct. > > > > Is my understanding correct? > > I think its the user's *systems* that are not configured to use (or able to > use?) a UTF-8 locale. > > The typewriter shouldn't be messing with that at all, but there appears to > be some conflict with > Qt and the system using a non- UTF-8 locale. Which if that is a hard > dependency for current Qt > probably isn't something we can fix (or anything we are doing wrong). > > Users having this problem will need to ensure they have a UTF-8 locale > available or (probably > preferably in the modern multi-lingual world) set as the default on their > system. > > The "Timestamps" warnings are just warnings and cause no problem, they are a > red herring here. Linux user chiming in here. I am running Fedora 42 KDE, and am having the exact same issue. I checked my system locale by running: cat /etc/locale.conf and the output was LANG="en_US.UTF-8". Which seems to indicate that the crash it not caused by not having a UTF-8 locale set.