x264: stat file error

nekostephan · 27th March 2007, 19:54

Hello there. I'm coding an anime release and get these messages:
avis [info] 640x480 @ 23.98 fps (34640 frames)
x264 [info] using CPU capabilities MMX MMXEXT SSE SSE2
x264 [warning] VBR maxrate specified, but no buffsize
x264 [error] ratecontron_init: can't open stats file
x264 [error] x264_encoder_open failed

CLI settings are:
--pass 2 --bitrate 950 --stats ".stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\c\l_115\115.mp4" "C:\c\l_115\115.avs"

AVS is like:
Avisource("BLEACH 115 (DivX6.25 640x480 120fps).avi").ChangeFPS(23.976)
sing1=avisource("s5_logo.avi")
trim(0,245)+trim(246,335).overlay(sing1,mask=sing1.showalpha())+trim(336,0)
textsub("bl_115_credits.ass")
textsub("OP_5_KARA.ass")
textsub("BLEACH_115_TS.ass")
textsub("ED_10_KARA.ass")
freezeframe(0,4,5)

What can i possibly do to avoid this?
Just in case, BLEACH is not licenced in Russia.

Theliel · 27th March 2007, 20:25

If you are using only a CLI version (no GUI) this setting are bad, because you need a first pass before apply a second pass. The first pass analyze and distribute bitrate for the second pass and create a .stats file where this datas are store. Your setting said --pass 2, so... where are --pass 1? you need make a first pass.

If you are using megui (for example) the most probable you don't choose automated 2pass, and select only second pass, so only second pass are make. Second pass need .stats for encode proccess.

Anyway, copy/paste entire logs

nekostephan · 27th March 2007, 21:22

I'm using meGUI, and I'm using Automated 2 pass. But it gets stuck at 100% of the 1st pass, still showing me some FPS data. So I just copy-pasted the command line parameters from the box to cmd. So there are no meGUI logs.

I'm pretty dumb, didn't notice --pass 2. Changed it to --pass 1. Then the 1st pass ran up to 100%, and I had this:
http://i4.photobucket.com/albums/y124/RazorAV/001-1.jpg
Windows has pretty dumb commandline with no possibility to select it, so I had to do a screenshot. It just stuck there for approx 30 min. Is this really ok? I had to CTRL-C it =__=

Theliel · 27th March 2007, 21:51

ok ok

all right

You use megui to generate the command line right? then you copy the command and paste in command pronts.

When you select automated 2 pass in megui, he send to the queue the two pass. in command line box in megui you only can view the second pass, the first pass only in logs.

the best options are using megui for all, but if you want use command pront, you need add before the first pass.

For your options, before use your options, you need the first pass.

First Pass: (for a normal and slow first pass)

Code:

--pass 1 --bitrate 950 --stats "1.stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output NULL "C:\c\l_115\115.avs"

Second pass, your pass:

Code:

--pass 2 --bitrate 950 --stats "1.stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\c\l_115\115.mp4" "C:\c\l_115\115.avs"

nekostephan · 28th March 2007, 06:13

Well.. I tried that. But it still halted at the same point for some reason. Then I stopped it with CTRL-C. Then I initiated the 2nd pass, which halted there as well. The resulting file was not playable, though the size seemed ok.

http://i4.photobucket.com/albums/y124/RazorAV/002-1.jpg -- that's what it looks like

And you know.. this preset did actually encode me a file named NULL after the 1st pass

Theliel · 28th March 2007, 10:49

ok, the only problems I can see its the stats name, I have edit my previous post, try again please.

yes, the first pass only output are a 1.stats file, that is specificate in --stats "1.stats" so the output file are NULL

nekostephan · 28th March 2007, 13:15

Well, it does pretty much the same >,>.. The output is still not playable.

Theliel · 28th March 2007, 13:45

then i cant help you much more, sorry

, for me work perfectly, I have done some test exactly with your same settings, and all work fine. I hope anyone can help you:

and video play fine.

I can't test all because i haven't your sample, subtitules, logo... if you can upload all them i can do more test

Only I can said more, sure you have the latest megui/x264/avisynth...

luck.

nekostephan · 28th March 2007, 14:01

Yep, I have the latest software.. =__=
Just wondered, can it possibly because I have a two-core CPU.. My friend told me to switch threads to 2, but still I had the same problem. This time I put it in the meGUI.
Looks kinda hopeless ) I've reinstalled windows three times, so this must not be the case.
I did render similar avs scripts on the older machine, and it all worked fine. The raws were the same, the logo was the same..
I'm kinda puzzled O_o

Code:

Looking for job processor for job...
Processor found!
Starting job job1-1 at 16:38:15
Starting preprocessing of job...
Preprocessing finished!
 encoder commandline:
--pass 1 --bitrate 950 --stats "C:\c\l_115\115.stats" --bframes 3 --b-pyramid --nf --subme 1 --analyse none --vbv-maxrate 25000 --me dia --threads 2 --thread-input --progress --no-psnr --no-ssim --output NUL "C:\c\l_115\115.avs" 
successfully started encoding
Job aborted, deleting output file...Deletion failed.
Processing ended at 16:54:19
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 640x480 @ 23.98 fps (34640 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 
x264 [warning]: VBV maxrate specified, but no bufsize.
x264 [info]: slice I:303   Avg QP:16.43  size: 28290
x264 [info]: slice P:19843 Avg QP:19.07  size:  7075
x264 [info]: slice B:14494 Avg QP:20.41  size:  1698
x264 [info]: mb I  I16..4: 31.9%  0.0% 68.1%
x264 [info]: mb P  I16..4: 13.2%  0.0%  0.0%  P16..4: 46.9%  0.0%  0.0%  0.0%  0.0%    skip:39.9%
x264 [info]: mb B  I16..4:  0.6%  0.0%  0.0%  B16..8: 13.5%  0.0%  0.0%  direct:13.5%  skip:72.4%
x264 [info]: final ratefactor: 23.33
x264 [info]: kb/s:961.1


----------------------------------------------------------------------------------------------------------
The current job was aborted. Stopping queue mode
The current job contains errors. Skipping chained jobs

Theliel · 28th March 2007, 14:17

I dont belive problems will be two core, I always use auto or 2-4 thread, and never i have had any problems.

Maybe other user can help you

foxyshadis · 28th March 2007, 19:39

Is it hanging with or without cpu usage? If you could use process explorer to look at the threads, you might be able to find what's hanging. Maybe it's avisynth.

btw, to copy from a command window, right click and choose "mark", then select what you want and right click again to copy. In the window's properties is a "quickedit" option that leaves this mark mode on all the time, quite handy.

nekostephan · 28th March 2007, 20:01

foxyshadis, it is not hanging. It just hovers on 100% for ages, as if it is doing something. Neither meGUI nor commandline hangs up.

foxyshadis · 28th March 2007, 20:20

Pegging the cpu without performing useful work is hanging, whether it's x264 or megui or the command window doing it. That's why I was asking you to look at the threads (of x264 specifically), you might get a clearer idea of what's causing the hang. For instance, vsfilter had a bug for a while that would cause this exact sort of hang, except for remaining in memory after being closed until terminated.

nekostephan · 29th March 2007, 04:49

At 100% of progress:
x264 - 132 mb, 98-99% of CPU.
megui - 38 mb, 0-1% of CPU
And no side processes are shown.. just exactly the programmes that are running.
meGUI is actually responding to all the commands. And strangely enough, it still has some FPS data showing, which is gradually slowing down.

nekostephan · 30th March 2007, 13:16

Wonder if anything changes if I try it out on my Ubuntu system instead.
Although Avisynth on *nix seems to be rather difficult to set up.

Warpman · 30th March 2007, 14:49

clear §6 violation ...

edit: i expected that at least foxyshadis know the rules...

Theliel · 30th March 2007, 15:46

6 -> No warez, cracks, serials or illegally obtained copyrighted content! Links to content of a questionable nature, asking for, offering, or asking for help/helping to process such content in any way or form is not tolerated??

I dont understand.

Warpman · 30th March 2007, 15:55

Quote:

AVS is like:
Avisource("BLEACH 115 (DivX6.25 640x480 120fps).avi").ChangeFPS(23.976)

bleach is an Anime broadcastet in japan and of cause the copyright is violatet here.

So what don't you understand?

nekostephan · 30th March 2007, 19:38

Bleach is aired in Japan, that is correct. But laws concerning intellectual property are territorial in nature. That is, if it is not licenced in Russia, it is not illegal to fansub it in Russia.

foxyshadis · 30th March 2007, 20:08

Doom9 decided that fansubs were off limits a long time ago, regardless of their licensing status in individual countries. This has been discussed here many times, you must have been aware of it. You'll have to PM him if you want the thread reopened and the strike revoked.

I obviously didn't read the script closely (probably half asleep), but now that I have I know exactly what the problem is. I guess I should have earlier. Oh well.

27th March 2007, 19:54	#1 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	x264: stat file error Hello there. I'm coding an anime release and get these messages: avis [info] 640x480 @ 23.98 fps (34640 frames) x264 [info] using CPU capabilities MMX MMXEXT SSE SSE2 x264 [warning] VBR maxrate specified, but no buffsize x264 [error] ratecontron_init: can't open stats file x264 [error] x264_encoder_open failed CLI settings are: --pass 2 --bitrate 950 --stats ".stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\c\l_115\115.mp4" "C:\c\l_115\115.avs" AVS is like: Avisource("BLEACH 115 (DivX6.25 640x480 120fps).avi").ChangeFPS(23.976) sing1=avisource("s5_logo.avi") trim(0,245)+trim(246,335).overlay(sing1,mask=sing1.showalpha())+trim(336,0) textsub("bl_115_credits.ass") textsub("OP_5_KARA.ass") textsub("BLEACH_115_TS.ass") textsub("ED_10_KARA.ass") freezeframe(0,4,5) What can i possibly do to avoid this? Just in case, BLEACH is not licenced in Russia.

27th March 2007, 21:51	#4 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	ok ok all right You use megui to generate the command line right? then you copy the command and paste in command pronts. When you select automated 2 pass in megui, he send to the queue the two pass. in command line box in megui you only can view the second pass, the first pass only in logs. the best options are using megui for all, but if you want use command pront, you need add before the first pass. For your options, before use your options, you need the first pass. First Pass: (for a normal and slow first pass) Code: --pass 1 --bitrate 950 --stats "1.stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output NULL "C:\c\l_115\115.avs" Second pass, your pass: Code: --pass 2 --bitrate 950 --stats "1.stats" --ref 3 --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --nf --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\c\l_115\115.mp4" "C:\c\l_115\115.avs" Last edited by Theliel; 28th March 2007 at 10:49.

28th March 2007, 06:13	#5 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	Well.. I tried that. But it still halted at the same point for some reason. Then I stopped it with CTRL-C. Then I initiated the 2nd pass, which halted there as well. The resulting file was not playable, though the size seemed ok. http://i4.photobucket.com/albums/y124/RazorAV/002-1.jpg -- that's what it looks like And you know.. this preset did actually encode me a file named NULL after the 1st pass Last edited by nekostephan; 28th March 2007 at 06:17.

28th March 2007, 10:49	#6 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	ok, the only problems I can see its the stats name, I have edit my previous post, try again please. yes, the first pass only output are a 1.stats file, that is specificate in --stats "1.stats" so the output file are NULL Last edited by Theliel; 28th March 2007 at 10:51.

27th March 2007, 20:25	#2 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	If you are using only a CLI version (no GUI) this setting are bad, because you need a first pass before apply a second pass. The first pass analyze and distribute bitrate for the second pass and create a .stats file where this datas are store. Your setting said --pass 2, so... where are --pass 1? you need make a first pass. If you are using megui (for example) the most probable you don't choose automated 2pass, and select only second pass, so only second pass are make. Second pass need .stats for encode proccess. Anyway, copy/paste entire logs

27th March 2007, 21:22	#3 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	I'm using meGUI, and I'm using Automated 2 pass. But it gets stuck at 100% of the 1st pass, still showing me some FPS data. So I just copy-pasted the command line parameters from the box to cmd. So there are no meGUI logs. I'm pretty dumb, didn't notice --pass 2. Changed it to --pass 1. Then the 1st pass ran up to 100%, and I had this: http://i4.photobucket.com/albums/y124/RazorAV/001-1.jpg Windows has pretty dumb commandline with no possibility to select it, so I had to do a screenshot. It just stuck there for approx 30 min. Is this really ok? I had to CTRL-C it =__=

28th March 2007, 13:15	#7 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	Well, it does pretty much the same >,>.. The output is still not playable.

28th March 2007, 13:45	#8 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	then i cant help you much more, sorry , for me work perfectly, I have done some test exactly with your same settings, and all work fine. I hope anyone can help you: and video play fine. I can't test all because i haven't your sample, subtitules, logo... if you can upload all them i can do more test Only I can said more, sure you have the latest megui/x264/avisynth... luck.

28th March 2007, 14:17	#10 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	I dont belive problems will be two core, I always use auto or 2-4 thread, and never i have had any problems. Maybe other user can help you

28th March 2007, 19:39	#11 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,549	Is it hanging with or without cpu usage? If you could use process explorer to look at the threads, you might be able to find what's hanging. Maybe it's avisynth. btw, to copy from a command window, right click and choose "mark", then select what you want and right click again to copy. In the window's properties is a "quickedit" option that leaves this mark mode on all the time, quite handy.

28th March 2007, 20:01	#12 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	foxyshadis, it is not hanging. It just hovers on 100% for ages, as if it is doing something. Neither meGUI nor commandline hangs up.

28th March 2007, 20:20	#13 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,549	Pegging the cpu without performing useful work is hanging, whether it's x264 or megui or the command window doing it. That's why I was asking you to look at the threads (of x264 specifically), you might get a clearer idea of what's causing the hang. For instance, vsfilter had a bug for a while that would cause this exact sort of hang, except for remaining in memory after being closed until terminated.

29th March 2007, 04:49	#14 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	At 100% of progress: x264 - 132 mb, 98-99% of CPU. megui - 38 mb, 0-1% of CPU And no side processes are shown.. just exactly the programmes that are running. meGUI is actually responding to all the commands. And strangely enough, it still has some FPS data showing, which is gradually slowing down.

30th March 2007, 13:16	#15 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	Wonder if anything changes if I try it out on my Ubuntu system instead. Although Avisynth on *nix seems to be rather difficult to set up.

30th March 2007, 14:49	#16 \| Link
Warpman Registered User Join Date: Oct 2005 Posts: 130	clear §6 violation ... edit: i expected that at least foxyshadis know the rules...

30th March 2007, 15:46	#17 \| Link
Theliel Registered User Join Date: May 2006 Posts: 162	6 -> No warez, cracks, serials or illegally obtained copyrighted content! Links to content of a questionable nature, asking for, offering, or asking for help/helping to process such content in any way or form is not tolerated?? I dont understand.

30th March 2007, 19:38	#19 \| Link
nekostephan Apprentice Join Date: Oct 2006 Posts: 30	Bleach is aired in Japan, that is correct. But laws concerning intellectual property are territorial in nature. That is, if it is not licenced in Russia, it is not illegal to fansub it in Russia.

30th March 2007, 20:08	#20 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,549	Doom9 decided that fansubs were off limits a long time ago, regardless of their licensing status in individual countries. This has been discussed here many times, you must have been aware of it. You'll have to PM him if you want the thread reopened and the strike revoked. I obviously didn't read the script closely (probably half asleep), but now that I have I know exactly what the problem is. I guess I should have earlier. Oh well.