View Full Version : x264 v.347 ????
guada 2
30th October 2005, 18:30
Hello,
After a small test of encoding with x264 v347, I noted this:
first window.
Cannot start video compression
An unknow error occured (may be corrut data) error code - 100.
second window.
2nd pass has more frames thn first pass (105819 vs 180)
Where can this problem come?
Thank you to clarify.
NOTE: Xvid, Divx, Vp7, Canopus lossless, 3ivx fonctions perfectly.
guada 2
30th October 2005, 19:36
I confirm the problem persists. :confused:
Does someone can help me to understand where would the problem come? :(
If it can be you useful:
VDM 1.1012 + x264 v.347 + Didée script or AVI Vfapi 1.05
guada 2
30th October 2005, 20:38
I noticed that it concern only the multipass mode and no the others modes(single pass quantizer or single pass bitrate).
Very strange......
DryFire
30th October 2005, 21:40
I"m afraid I cannot reproduce that problem.
DarkZell666
30th October 2005, 22:01
I've just completed ~1000 frame encode using 2pass and VdubMOD 1.5.10.1 and x264 rev.347 : no problem spotted.
Could be that you messed with the script, or that eventually a set of options got broken (I doubt that though). Give us your complete x264 settings please (bframes/inloop/profile/resolution/etc.)
And btw what is that version of VdubMOD ? looks wierd :/
Try using the last one :
http://puzzle.dl.sourceforge.net/sourceforge/virtualdubmod/VirtualDubMod_1_5_10_2_All_inclusive.zip (right click + save as ...)
CEC
30th October 2005, 22:51
Start to use virtualdub! It is the best choice! :) :)
I think that Virtualdubmod stop development.
Manao
30th October 2005, 22:53
Start using MeGUI and stop using VFW for h264 then. It'll be even better
smok3
30th October 2005, 22:59
i get similar error with megui, allready reported in another thread,
Log for job job1-2
avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
mp4 [info]: initial delay 0 (scale 25)
x264 [error]: More input frames than in the 1st pass
so i guess thats x264 problem of some kind...
--- the machine is:
CPU Type - AMD Athlon 64, 1800 MHz (9 x 200) 3000+
Motherboard Chipset - nVIDIA nForce4, AMD Hammer
System Memory - 1024 MB (DDR SDRAM)
guada 2
30th October 2005, 23:14
Hello,
- DVD MUSICAL: Bob marley & the Wailers
- DURATION : 1H10..
- RIP DVDDECRYPTER 3.5.4.0 / FILE D2V DGINDEX 1.4.3
- This is my script:
#
LoadPlugin("C:\Program Files\GordianKnot\DGMPGDec\DGDecode.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\UnDot.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\MaskTools.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\WarpSharp.dll)
#LoadPlugin("C:\PROGRA~1\GORDIA~1\aSharp.dll)
#LoadPlugin("C:\PROGRA~1\GORDIA~1\aWarpSharp.dll)
#LoadPlugin("C:\PROGRA~1\GORDIA~1\LoadPluginEx.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\dustv5.dll")
#
mpeg2source("C:\Documents and Settings\desbonne\Mes documents\Bob marley\dgindex\film.d2v")
#iip( dest_x= 1024, dest_y= 576,
# ss1_x = 1.414, ss1_y = 1.414,
# duststr = 0, dustweight = 0, antiflicker1= true, antiflicker2= true,
# detailcontr1=127, detailcontr2 = 255, contr_radius = 3, PixSharp=0.25,
# ss2_x = 3.5, ss2_y = 3.5,
# Xstren = 255, Xlimit = 255,
# subpelstren= 1.0, flatweight = 64,
# protect_floor= 4, protect_bias = 16,
# dering = -60, dering_weight= 1.0, dering_floor = 16, dering_bias=8,
# detail_floor= 1, EQ = 2,
# warp_Y = false, warp_UV = false,
# debug= "showall | compareH/V | protect | dering",
# cropx=32, cropy=16
# )
- ENCODING : VDM of GK 0.35 (the last version 1.5.10.2) + x264 V.347
- SETTINGS OF x264 V.347:
Target bitrate: 1235 kBPS;
Activated:
- 8*8, 8*16.. (P frame), 8*16.. (B frame), 4*8.. (P frame), 8*8 & 4*4 Intra
- adaptative, Weighted bipred;
- chroma ME;
- cabac, Deblocking filter :Strength/Threshold (-2/-2);
Partition decision: 6 (RDO - Slowest);
Method: Exhaustive search;
Max Ref.frames: 5
Max Consécutive: 2
Here, it is all.
NOTE:
I tried of others script it doesn't function.
I tried of other tools VDM 1.5.10.2, the last DGindex or even DVDAVI, other ripper the same report.
I tested also the mode by default of the codec x264, same report.
I don't know what thought.. :( :( :confused:
Thank you for your opinion: DarkZell666 & DryFire
Bye.
guada 2
30th October 2005, 23:21
The features of my PC:
- Asus P4G8X Deluxe;
- P4 2.4 Ghz;
- 1024 DDR 266 dual Channel;
- Ati radeon 9800 pro;
- 2 SATA 150 160 GB;
- 1 SOUND CARD Presonus Firepod...
akupenguin
30th October 2005, 23:25
@guada:
Look in 'x264.stats', does it really contain 105819 frames, or 180?
x264 [error]: More input frames than in the 1st pass
Are you sure? the message should be (as reported by guada):
"x264 [error]: 2nd pass has more frames than 1st pass (%d vs %d)"
smok3
31st October 2005, 00:21
akuapenguin: yes, that is meguis log thought.
guada 2
31st October 2005, 01:02
Hello akupenguin,
I found the cause of my problem.
That will appear strange to you.
I noted 2 report:
- that I use MeGui or VDM, the encoding functions (while taking into account the totality of the movie).
Strange, I am say.
- But when I voluntarily stop the encoding with MeGui or VDM on part of film.
MeGui or VDM causes an error.
The error which I mentioned all at the beginning.
My question:
- is it normal or not?
akupenguin
31st October 2005, 01:15
What is "voluntarily stop"? Do you put a trim() in the avs, or select a range in Vdub, or a "--frames" on the megui generated commandline?
guada 2
31st October 2005, 02:03
no, no,no,
very classic..
I have just abort the encoding on the first pass (after some minutes), as I often make with xvid or other codecs..
guada 2
31st October 2005, 02:05
Aapparently this version of x264 doesn't support it.
Why?
akupenguin
31st October 2005, 02:35
That's exactly what this feature was designed to detect and forbid.
You're asking 2pass ratecontrol to encode a 105819 frame movie using only 180 frames worth of stats. If you're not going to encode the whole thing, you have to tell it that to begin with, otherwise it tries to allocate bits over all 105819 frames.
You can abort the 1st pass whenever you like, but you must use trim() or --frames or vdub to set the same (or smaller) range for the 2nd pass.
MeteorRain
31st October 2005, 11:29
Log for job job1-2
avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
mp4 [info]: initial delay 0 (scale 25)
x264 [error]: More input frames than in the 1st pass
see the problem again...
bond
31st October 2005, 12:46
see the problem again...mp4 [info]: initial delay 0 (scale 25) is normal
guada 2
31st October 2005, 17:36
Thank you very much for this clarification akupenguin. :)
Two small question: :)
- Does it have a big difference between the time of encoding and the final quality of the movie between these 2 options?
x264: 6 (RDO - Slowest) and x264: 7 (RDO Level 2 (Slower)).
Something else:
- Why the mode (partition decision): x264 7 (RDO Level 2 (Slower)) is not present in the configuration with VDM / x264?
Randall
31st October 2005, 18:28
Hello,
After a small test of encoding with x264 v347, I noted this:
first window.
Cannot start video compression
An unknow error occured (may be corrut data) error code - 100.
second window.
2nd pass has more frames thn first pass (105819 vs 180)
Where can this problem come?
Thank you to clarify.
NOTE: Xvid, Divx, Vp7, Canopus lossless, 3ivx fonctions perfectly.
I've gotten the same errors that you did with that version of the codec. Solution for me was to make sure that the framerate was set properly. I was encoding something that was IVTC (3:2 pulldown) with a framerate of 23.967 FPS, while x264 thought I was using a regular NTSC framerate of 29.970 FPS. That was where the descripency was for "more frames then first pass". I dunno if this helps you or not.
smok3
2nd November 2005, 08:54
ok, adding assumefps(25) at the end of avisynth fixed it, weird, the framerate seems to be correctly reported thought, at least vdub thinks so.
p.s. original file was premiere DV exported thingy.
Sharktooth
4th November 2005, 16:06
You can safely add NiceFPS() filter (without parameters) to all your .avs files. It should fix everything without adding AssumeFPS and without caring about the FPS.
:search: to find it.
bond
4th November 2005, 16:19
strange again a framerate related problem! this time with vfw and virtualdub?
there must be a bug sitting somewhere in x264 being triggered by some framerate issues!
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.