Ever since the update to 0.9.10 I've been having a problem with some clips I'd made in previous versions crashing the render with the error "Wild Timestamp". I temporarily worked around the issue by rerendering the offending clip with the new version and a standard rendering profile (h264/aac high profile).

However, I've run into the same problem again with a different clip, but rerendering the offending clip this time does NOT fix the problem.

Here's the error message:

Code: Select all

Rendering of /home/crono141/LP Videos/LPs/Speed Runners/SpeedRunners#1.mp4 crashed
[mp3 @ 0xd69620] max_analyze_duration 5000000 reached at 5015510 microseconds [mp3 @ 0xd69620] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0xd6d680] max_analyze_duration 5000000 reached at 5015510 microseconds [mp3 @ 0xd6d680] Estimating duration from bitrate, this may be inaccurate
medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ]
[mp3 @ 0x7f1fa0004a60] max_analyze_duration 5000000 reached at 5015510 microseconds [mp3 @ 0x7f1fa0004a60] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x7f1fa0006160] max_analyze_duration 5000000 reached at 5015510 microseconds [mp3 @ 0x7f1fa0006160] Estimating duration from bitrate, this may be inaccurate
[mp4 @ 0x7f1fb00c6da0] Encoder did not produce proper pts, making some up.
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4
WILD TIMESTAMP! Current Frame: 61644, percentage: 99
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!
[producer avformat] /home/crono141/LP Videos/LPs/Outtro/Specter Outro.mp4 WILD TIMESTAMP!




Any thoughts on a solution?

Well, after taking a few weeks off, I started rendering 5 clips today. Each one had the same outro clip at the end. On the last render, it failed with the same wild timestamp error. But it makes me think that wild timestamp is a result of the render process, not the clips being used.

I can't believe that no one else is experiencing this issue.

could be a kdenlive/melt incompatibility issue. Try a daily build version https://userbase.kde.org/Kdenlive/Manua ... ily_builds

Dear KDL users, 20 June in Brisbane.
I have received the Timestamp and other messages a few days ago. I have PC1 where I edit "real" movies for three or four years with no such error messages.
The other PC2 I have used to make my own movie camera movies for a few years still with NO error messages, BUTTTTTTTTT,
a few days ago I decided to do a job as I do on PC1, on PC2 and I received the Timestamp error and anther error message.
To boil it down both PCs are big towers about 8 years old, PC1 HP XW 9300, PC2 HP XW 4600. Both have about 2 GB RAM, MINT V17+, Kdenlive V0.9 xx.
I won't give details of mother board and BIOS until later.
Sooooooo, I suspect the differences in hardware of the PCs is the problem!
Cheerio, Juan.
=================================