Log in

View Full Version : x264 v.375B ?


guada 2
26th November 2005, 12:35
Hello, :)

While testing the last version of the codec x264 v.375B, I have a this information:
" Dub: I/O thread has not cycled for ten second, possible livelock (thread location: à68FAB95) " in beginning and at the end of treatment of VDM.
What can it mean precisely?


A small note:
With this codec, I tested a script manufactured of all pieces uncluding three types of scripts: the one of SOCIO (fftw3..), Didée (limitedsharpen),and Didée (iip) on ultra low bitrate (50 kbps).

The order have its importance in the treatment because it exploits final quality .
Hang yourselves, my file has been divided by 5. for 1,45 mo, I obtained 293 ko, of course without the sound.
The picture is incredible of precision.
However, my codec x264 works between 0 and 2 fps. and without the script (basic script) I turn between 8 and 13.

Bye.

Doom9
26th November 2005, 13:24
asked and answered before. Unfortunately the search engine doesn't pick it up properly but it just mean encoding is really slow, and since you posted your FPS, you're bound to get that message every now and then. If you want to get rid of it, simplify your scripts, lower your x264 settings to something more CPU friendly or simply get a more powerful CPU. And perhaps you should look for a French forum? Half your posts make no sense at all since online translators cannot handle complex technical texts properly.

guada 2
27th November 2005, 23:07
Doom9,

" asked and answered before. Unfortunately the search engine doesn't pick it up properly but it just mean encoding is really slow, and since you posted your FPS, you're bound to get that message every now and then. If you want to get rid of it, simplify your scripts, lower your x264 settings to something more CPU friendly or simply get a more powerful CPU ".

Excuse me, I didn't think it.

" Half your posts make no sense at all since online translators cannot handle complex technical texts properly ".

Sorry, for my bad translations....

Bye.

guada 2
28th November 2005, 22:07
Hey Doom9,

Apparently, after analysis my problem came from Nuendo 3.1.1.
Now, it functions.

Thank you for your suggestions. ;)