Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 AVC / H.264

Reply
 
Thread Tools Search this Thread Display Modes
Old 19th April 2011, 22:37   #1461  |  Link
J_Darnley
Registered User
 
J_Darnley's Avatar
 
Join Date: May 2006
Posts: 959
You should be able to open the stats file in any text editor. Perhaps it is too large for notepad, use something better. You won't be able to see much in the mbtree file because it is a binary file.
__________________
x264 log explained || x264 deblocking how-to
preset -> tune -> user set options -> fast first pass -> profile -> level
Doom10 - Of course it's better, it's one more.
J_Darnley is offline   Reply With Quote
Old 20th April 2011, 23:39   #1462  |  Link
ajp_anton
Registered User
 
ajp_anton's Avatar
 
Join Date: Aug 2006
Location: Stockholm/Helsinki
Posts: 775
Quote:
Originally Posted by Mug Funky View Post
i just tried out the recent MBAFF changes that were committed.

preliminary tests show positive results.
How recent? Can't find any MBAFF-related in the x264.nl changelog.
ajp_anton is offline   Reply With Quote
Old 20th April 2011, 23:51   #1463  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,339
Quote:
Originally Posted by ajp_anton View Post
How recent? Can't find any MBAFF-related in the x264.nl changelog.
He's probably talking about the dev git, but it looks like the mbaff additions got removed again.
sneaker_ger is offline   Reply With Quote
Old 5th May 2011, 03:21   #1464  |  Link
upyzl
zj262144
 
upyzl's Avatar
 
Join Date: Sep 2010
Posts: 105
About r1944

why not turn off psy-rd <RD:Trellis> when set subme<6 or trellis=0 as before?
I think that's the right info for users... even I want to advise deleting deadzone info when used trellis=2 at the same time...

and also about merange on umh/esa/tesa
maybe 4~256 is a good valid range
__________________
MPC-HC 1.7.8 / LAV Filters 0.64+ (tMod) / XySubFilter 3.1.0.705 / madVR 0.87.14

Direct264 Mod (src & win32 builds): code.google.com/p/direct264umod (maybe outdated)

Last edited by upyzl; 5th May 2011 at 03:38.
upyzl is offline   Reply With Quote
Old 5th May 2011, 05:33   #1465  |  Link
MasterNobody
Registered User
 
Join Date: Jul 2007
Posts: 514
Quote:
Originally Posted by upyzl View Post
About r1944

why not turn off psy-rd <RD:Trellis> when set subme<6 or trellis=0 as before?
I think that's the right info for users... even I want to advise deleting deadzone info when used trellis=2 at the same time...
Did you read the commit message (this part "Also avoid encoder_reconfig turning off psy_rd/trellis.")? That was made because --subme and --trellis can be changed later by reconfiguration (for example --zones) and so if user explicitly didn't disabled them they should be enabled. Btw internally they of course disabled with subme<6 or trellis=0 but parameters not reseted. As for deadzone they still have effect even with --trellis 2 also again reconfiguration allow changing trellis.
Quote:
Originally Posted by upyzl View Post
and also about merange on umh/esa/tesa
maybe 4~256 is a good valid range
It would be 4..1024 range
MasterNobody is offline   Reply With Quote
Old 5th May 2011, 10:00   #1466  |  Link
upyzl
zj262144
 
upyzl's Avatar
 
Join Date: Sep 2010
Posts: 105
@MasterNobody

Thanks very much for the explanation
Now I understand...
__________________
MPC-HC 1.7.8 / LAV Filters 0.64+ (tMod) / XySubFilter 3.1.0.705 / madVR 0.87.14

Direct264 Mod (src & win32 builds): code.google.com/p/direct264umod (maybe outdated)
upyzl is offline   Reply With Quote
Old 6th May 2011, 17:02   #1467  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,529
Quote:
Originally Posted by Selur View Post
  • renders '--open-gop' parameters obsolete:
It makes them a little more than obsolete. It causes x264 to fail with an error that it can't open the option. Because --open-gop no longer has options, the very next word in the line is considered the file to open because it doesn't start with --.

I got caught with that and couldn't figure out why it couldn't open "none" when it was an option for --open-gop. I removed "none" as a test and discovered that it now worked.

It would have been nice if x264 still looked for a potential option and if so, spit out a warning that it is now obsolete and reference --bluray-compat in the warning.

After the failure, I started digging and a posting over on Doom10 pointed to this thread. That resulted in my changing some more stuff in my CLI (adding the --bluray-compat option and removing two others).
MrVideo is offline   Reply With Quote
Old 7th May 2011, 02:08   #1468  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,529
Question about the recent changes

Below is the CLI I use for encoding video so that I can edit it with VRD:

Code:
x264 --pass 2 --profile high --level $LEVEL --bitrate $BITRATE --ref $REF \
        --deblock 1:-1:-1 --me umh --subme 10 --psy-rd 1.00:0.15 --merange 24 \
        --trellis 2 --deadzone-inter 21 --deadzone-intra 11 --fast-pskip \
        --threads 12 --slices 4 --nr 0 --bframes 3 --b-pyramid strict \
        --b-adapt 2 --b-bias 0 --direct auto --weightp 0 --keyint $KEYINT \
        --min-keyint 1 --scenecut 40 --rc-lookahead 60 --ratetol 1.0 \
        --qcomp 0.60 --qpmin 10 --qpmax 51 --qpstep 4 --cplxblur 20.0 \
        --qblur 0.5 --vbv-maxrate $MAXBITRATE --vbv-bufsize $BUFSIZE \
        --ipratio 1.40 --aud --nal-hrd vbr --open-gop $INTERLACED \
        --sar $SAR --qpfile "${DIRNAME}/${NAME}_qpfile.txt" \
        --input-res $RES --stats "${DIRNAME}/${NAME}.stats" \
        --output "${DIRNAME}/${NAME}.264" \
        "tmp.fifo.yuv"
If the video is interlaced, the $INTERLACED variable will be set to --tff.

Before the recent changes, the --open-gop had none as its option.

What the above did for me is create IDR frames at the locations where I frames are normally placed and at locations set in the qpfile.

But now, instead of IDR frames, it is only I frames.

How do I get IDR frames back? Why was the functionality of IDR frame generation removed, or was it an error in the first place and I stumbled upon it?
MrVideo is offline   Reply With Quote
Old 7th May 2011, 02:16   #1469  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,339
If you use "K" it will depend on your open-gop setting - you can still force "I" or "i". Or does this not work for you?

/edit:
To make sure I get you straight:
1.) Before, you had open-gop deactivated ("--open-gop none")
2.) Now you have open-gop activated ("--open-gop")

and you're wondering why x264 behaves differently?

Last edited by sneaker_ger; 7th May 2011 at 03:09.
sneaker_ger is offline   Reply With Quote
Old 7th May 2011, 05:32   #1470  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,529
Quote:
Originally Posted by sneaker_ger View Post
If you use "K" it will depend on your open-gop setting - you can still force "I" or "i". Or does this not work for you?

/edit:
To make sure I get you straight:
1.) Before, you had open-gop deactivated ("--open-gop none")
2.) Now you have open-gop activated ("--open-gop")

and you're wondering why x264 behaves differently?
Yes. Why, because the rules of the game have changed in the middle of the game. There isn't a changelog with the source distribution. Is there a place that lists major operational changes like this and explains what the changes affect and what the CLI settings should be? Maybe a separate thread, that doesn't allow discussion, that lists functional changes to the options and fully explains the previous setting combinations and what the new settings are to match the old.

Doing a little digging, a posting over on Doom10 (think it is a page back here as well) indicates that without --bluray-compat the --open-gop acts as it was --open-gop cbrHD under the old code. But, cbrHD was not an option, as they were none, normal and bluray. Because the posting didn't make sense, it was shoved aside.

While the developers understand what is going on with the changes, we poor users are sorta left out in the cold. I'd like to see a dedicated thread, as described above, as that would really help us users.
MrVideo is offline   Reply With Quote
Old 7th May 2011, 05:44   #1471  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,339
Yeah, such a place does not exist.
The only thing you can do is to watch the changelog every time a new version gets released.
sneaker_ger is offline   Reply With Quote
Old 8th May 2011, 03:24   #1472  |  Link
Astrophizz
Registered User
 
Join Date: Jul 2008
Posts: 184
The mailing list sends out batch changelogs with commentary.
Astrophizz is offline   Reply With Quote
Old 8th May 2011, 07:12   #1473  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,529
Quote:
Originally Posted by Astrophizz View Post
The mailing list sends out batch changelogs with commentary.
Thanks. Where does one sign up?
MrVideo is offline   Reply With Quote
Old 8th May 2011, 07:38   #1474  |  Link
Astrophizz
Registered User
 
Join Date: Jul 2008
Posts: 184
Quote:
Originally Posted by MrVideo View Post
Thanks. Where does one sign up?
http://mailman.videolan.org/listinfo/x264-devel
A small warning though. When a new update batch is pushed out every couple of weeks, you'll get an email with a newsletter summarizing what changed plus and email for each change.
Astrophizz is offline   Reply With Quote
Old 8th May 2011, 11:14   #1475  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,529
Quote:
Originally Posted by Astrophizz View Post
A small warning though. When a new update batch is pushed out every couple of weeks, you'll get an email with a newsletter summarizing what changed plus and email for each change.
That's OK. It will be a drop in the bucket, compared to the rest of what I get on a daily basis.

Thanks for the info.
MrVideo is offline   Reply With Quote
Old 11th May 2011, 07:56   #1476  |  Link
3ds
Registered User
 
Join Date: Oct 2008
Posts: 10
If i see it right, the minimal encoding arguments for 1080p23.976 / 1080p24 bluray compatibility are :
Code:
--bluray-compat --vbv-maxrate 40000 --vbv-bufsize 30000 --keyint 24 --slices 4
But why must i add vbv-maxrate, vbv-bufsize, keyint and slices? x264 can calculate them from the given resolution/fps, isn't it?

Btw. the --fullhelp about --bluray-compat should list the parameters that would be set (e.g.: http://forum.doom9.org/showthread.ph...13#post1493513 )
3ds is offline   Reply With Quote
Old 11th May 2011, 08:08   #1477  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 5,827
Quote:
Originally Posted by 3ds View Post
Btw. the --fullhelp about --bluray-compat should list the parameters that would be set (e.g.: http://forum.doom9.org/showthread.ph...13#post1493513 )
I agree.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 11th May 2011, 08:13   #1478  |  Link
nurbs
Registered User
 
Join Date: Dec 2005
Posts: 1,457
Even knowing that your target is Blu Ray there are two possible vbv values for 1080p. This also affects the number of slices. Depending on that there are also two different keyint parameters that are valid. Just by that commandline x264 can't know which of the two you want. See the Blu Ray encoding sticky.
nurbs is offline   Reply With Quote
Old 11th May 2011, 08:48   #1479  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,339
Is there any reason to use --b-pyramid strict outside of Blu-Ray? I'm asking because its parameters didn't got removed, unlike with --open-gop.
sneaker_ger is offline   Reply With Quote
Old 11th May 2011, 08:59   #1480  |  Link
3ds
Registered User
 
Join Date: Oct 2008
Posts: 10
Quote:
Originally Posted by nurbs View Post
Even knowing that your target is Blu Ray there are two possible vbv values for 1080p. This also affects the number of slices. Depending on that there are also two different keyint parameters that are valid. Just by that commandline x264 can't know which of the two you want. See the Blu Ray encoding sticky.
We have two choices for level 4.1 and level 4.0, if i look to Primary Video Rules from: http://forum.doom9.org/showthread.php?t=154533

So x264 must know witch level should be used. Idea: --bluray-compat used highest level (--level 4.1) as default, but the user can add --level 4.0

So there are any information to calculate all needed restrictions values (e.g. max bitrate, buffer size etc.)

btw. is there ever a reason to use a smaller level than 4.1? All bluray players should play level 4.1, isn't it?
3ds is offline   Reply With Quote
Reply

Tags
coding, development, x264 dev

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 01:07.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.