Quote:
Originally Posted by cartman0208
Tried it but no success... error message is the same
BUT ... when I delete "--bframes 3" from the string, it works ...
The failed signature message is still there but no malloc error ... and I see progress
Is there anything more I can do to localize the issue?
|
The signature thing is no big deal -- it just bothers me that they do it without asking or being told to do so.
The weird thing is that adding the "--bframes 3" is actually redundant. The default value is 3. I only use it in the command line because I like to be explicit on values that are outlined in the standard.
While it is running, can you open up Task Manager, click on "Details", and then on CPU (so it orders by CPU usage) and see how much memory X264.exe is using?