In encoding settings I found is mbtree=0 Which shouldn't be by the way because I set SLOW Preset with High Profile while highest preset where mbtree is turned off is Superfast according to x264 vfw HELP information.
[img]http://clip2net.com/clip/m151930/1403620563-clip-58kb.png[/img] [img]http://clip2net.com/clip/m151930/1403620700-clip-68kb.png[/img]
I may give 2 videos.
MediaInfo from x264 vfw 2pass encoded directly from Vegas. BTW, to get this encoding information I remuxed avi file into mkv by mkvmerge.
[code]General
Unique ID : 172360418530296014871990821272703323155 (0x81AB68BC93CA7AC88CBF06EA555DCC13)
Complete name : E:\Documents\Desktop\111 x264_.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 7.06 MiB
Duration : 8s 66ms
Overall bit rate : 7 339 Kbps
Encoded date : UTC 2014-06-24 13:36:21
Writing application : mkvmerge v6.9.1 ('Blue Panther') 64bit built on Apr 18 2014 18:23:38
Writing library : libebml v1.3.0 + libmatroska v1.4.1
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Bit rate : 7 193 Kbps
Nominal bit rate : 8 000 Kbps
Width : 1 620 pixels
Height : 1 080 pixels
Display aspect ratio : 3:2
Frame rate mode : Variable
Original frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.152
Writing library : x264 core 130 r2274bm c832fe9
Encoding settings : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x113 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=4 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=300 / keyint_min=30 / scenecut=40 / intra_refresh=0 / rc=2pass / mbtree=0 / bitrate=8000 / ratetol=1.0 / qcomp=0.70 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / pb_ratio=1.30 / aq=1:1.00
Default : Yes
Forced : No[/code]
Anonymous
You have "Zero Latency" option enabled (read --tune zerolatency help) which also disables MBTree.
YEAP! I have just figured that myself after reading previous "bug" about sliced threads and then reading Diary Of An x264 Developer.
Huge Thank You for your instant reply anyway. Indeed.
P.S. Maybe that would be a great idea to set a notification in GUI that enabling zero latency will force to "that" and "that" and i some cases it may decrease quality of finished video. Because every youtube guides for noobies by "experts" tell that checking that box is Number1 thing to do.
Thank you again. Good bye!
Btw. You overwrites some options enabled by "Zero Latency" so it wouldn't be zero anyway. You can have audio desync and lost frames at the end with such config so I will recommend to use "Output mode" == File (or if you encode in VirtualDub than "VitrualDub Hack")
Yes, I had sudden end of the video while there should be another 0.5 sec or so.
I enabled those options because I found they were disabled and didn't know why:)
I use Sony Vegas and encode project from it using x264vfw codec. Should I use Virtualdub hack too in this case? I assume yes.
What else would you suggest then?
There is pop up notification when you move cursor to this option: "Tune options for minimal encoding latency (zero frame-buffering) at the cost of compression efficiency".
No. In this case only way is to use file output mode instead of VFW if you want to use all options (no quality sacrifice for zero latency). VirtualDub Hack option ONLY works in VirualDub or its forks. It will create non spec complaint stream if you enable it in not supported encoding app.
I'm really sorry for offtopic but doom9 doesn't let post for 5 days after register.
Could you tell me what settings can I disable in command line in last pass? I heard that analysis and other such stuff isn't needed due to all info is already in stats file. Is it?
I appreciate for help.
Short answer: nothing. Long answer: second (N-th) do not do slicetype decision but you don't need to disable anything because it is done by default. So don't mess with settings of last pass more than you want in general (not something specific to last pass). For first pass there are "Mutlipass - 1st pass (fast)" or --fast-firstpass so you also no need to mess a lot with other options.
P.S. If you want to ask questions than better do this in Discussion (not in Bug Tickets).