This forum has been archived. All content is frozen. Please use KDE Discuss instead.

libx264 aborts with unable to parse option value "0.6"

Tags: None
(comma "," separated)
DiveO
Registered Member
Posts
182
Karma
0
My setup: kdenlive 0.9.3+git from sunab's svn repository+mlt+libav
Kubuntu 12.04 64bit

Rendering of a clip is aborted using the H264 codec:

[libx264 @ 0x7f49589ae9e0] [Eval @ 0x7f495dffb490] Invalid chars '.6' at the end of expression '0.6' [libx264 @ 0x7f49589ae9e0] Unable to parse option value "0.6"

Happens only a single project that I recently changed from 720p/25Hz to 1080p/25Hz. Checking the transitions I could not find any problem indication.

Any suggestions?
DiveO
Registered Member
Posts
182
Karma
0

[SOLVED]

Tue Oct 02, 2012 3:15 pm
Trimmed down the project file until I found the problem: somehow kdenlive generates some invalid parameters when handing over the job to rendering to mlt. I could track down the problem to a particular effect on a certain clip. Disabling and then reenabling seemed to have caused parameter regeneration and since then my project can be rendered without problems again. Strange...
barnadaniel
Registered Member
Posts
6
Karma
0
Hi,
I guess I have the same problem. My project rendered without any problems, but after some modifications (added some transitions) it crashes with
[NULL @ 0xafe11400] [Eval @ 0xb0742a5c] Invalid chars '.6' at the end of expression '0.6' [NULL @ 0xafe11400] Unable to parse option value "0.6"
[libx264 @ 0xafe11400] interlace + weightp is not implemented [libx264 @ 0xafe11400] interlaced (1) > level limit (0)
WARNING: QApplication was not created in the main() thread.
[swscaler @ 0x96628680] Warning: data is not aligned! This can lead to a speedloss
[swscaler @ 0xbb90eb80] bad dst image pointers

How did you trace the problem? How did you find out which transition caused it? Removing and adding the transition is the way to go?
Thank you
Daniel
TheDiveO
Registered Member
Posts
595
Karma
3
OS
Had such issues sometimes with some older projects. In order to track down the transition that is causing the mayhem for whatever reason I've developed this rescue habbit: first, make a copy of your project, then work on this copy. Delete except maybe the first minute, do NOT save, render. If this succeeds, then undo, delete everything except the first two minutes, repeat ... when you hit a crash, undo and narrow down. Remember, undo is a real friend here! I've managed to salvage several projects this way.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot]