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 1st September 2010, 13:37   #81  |  Link
shon3i
BluRay Maniac
 
shon3i's Avatar
 
Join Date: Dec 2005
Posts: 2,419
Quote:
Originally Posted by A.Fenderson View Post
I see --mvrange 511 set on a lot of blu-ray profiles: is this strictly necessary, or does it just seem to improve compatibility on some players?
That is because earler version of x264 are not limit mvrange to 511.75, which is now default value, and it's fine for Blu-Ray.
shon3i is offline   Reply With Quote
Old 1st September 2010, 18:16   #82  |  Link
MasterNobody
Registered User
 
Join Date: Jul 2007
Posts: 552
Quote:
Originally Posted by shon3i View Post
That is because earler version of x264 are not limit mvrange to 511.75, which is now default value, and it's fine for Blu-Ray.
This was changed almost 3 years ago in revision 697 which anyway wasn't Blu-Ray compatible so I don't see the reason why it still appears in Blu-Ray profiles.
MasterNobody is offline   Reply With Quote
Old 16th September 2010, 21:39   #83  |  Link
Ulf
Registered User
 
Join Date: Sep 2008
Location: Sweden
Posts: 66
Encoding 720p25 or 720p29.97 with "--pulldown double" and 480p23.976 with "--pulldown 32 --fake-interlaced --pic-struct" will yield Bly-ray compatible streams (assuming the rest of the settings are OK). The question is what the maximum setting for "--keyint" would be in these cases for a 1s GOP? Is "--keyint" referring to the original frame rate or the pulldown framerate, i.e. to 25 or to 50 in the case of 720p25?
Ulf is offline   Reply With Quote
Old 16th September 2010, 22:01   #84  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by Ulf View Post
Encoding 720p25 or 720p29.97 with "--pulldown double" .....
Have you been successful with 720p25 --pulldown double? I get jerky playback on my BD standalone unless I encode without b frames.
Sharc is offline   Reply With Quote
Old 17th September 2010, 09:09   #85  |  Link
Ulf
Registered User
 
Join Date: Sep 2008
Location: Sweden
Posts: 66
Quote:
Originally Posted by Sharc View Post
I get jerky playback on my BD standalone unless I encode without b frames.
Have you seen a significant difference in playback of a 720p25 clip encoded with "--pulldown double" and the same clip with frame duplication done before encoding, i.e. AssumeFrameBased().ComplementParity().SelectEvery(1,0,0) ?
Ulf is offline   Reply With Quote
Old 17th September 2010, 12:45   #86  |  Link
kieranrk
Registered User
 
Join Date: Jun 2009
Location: London, United Kingdom
Posts: 707
Quote:
Originally Posted by Ulf View Post
Encoding 720p25 or 720p29.97 with "--pulldown double" and 480p23.976 with "--pulldown 32 --fake-interlaced --pic-struct" will yield Bly-ray compatible streams (assuming the rest of the settings are OK). The question is what the maximum setting for "--keyint" would be in these cases for a 1s GOP? Is "--keyint" referring to the original frame rate or the pulldown framerate, i.e. to 25 or to 50 in the case of 720p25?
I'm not actually 100% sure. I always thought a GOP had to have actual frames in it so --keyint 50 would be correct for 720p25.
kieranrk is offline   Reply With Quote
Old 17th September 2010, 23:54   #87  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by Ulf View Post
Have you seen a significant difference in playback of a 720p25 clip encoded with "--pulldown double" and the same clip with frame duplication done before encoding, i.e. AssumeFrameBased().ComplementParity().SelectEvery(1,0,0) ?
I did frame duplication like:
AssumeFieldBased().AssumeTFF()
FieldDeinterlace().ChangeFPS(50)
which was ok.
I believe that the problem with b-frames and --pulldown double in my case is that the re-ordering of the b-frames for playback is not done. Maybe a problem of the decoder.

Added:
I tried your script. It works as well. No jerkiness.
Unfortunately the file size for same crf becomes 50% larger with the frame-doubling.

I still have problems with '--pulldown double' and b-frames. It works with MPC-HC but fails (i.e. jerky playback) with VLC and with my standalone - unless I encode without b-frames.

Last edited by Sharc; 18th September 2010 at 10:09. Reason: Added
Sharc is offline   Reply With Quote
Old 18th September 2010, 14:42   #88  |  Link
Midzuki
Unavailable
 
Midzuki's Avatar
 
Join Date: Mar 2009
Location: offline
Posts: 1,480
Quote:
Originally Posted by Sharc View Post
I still have problems with '--pulldown double' and b-frames. It works with MPC-HC but fails (i.e. jerky playback) with VLC and with my standalone - unless I encode without b-frames.
Does it make a difference if you set --bframes to 2 or to 1
Or if you use --b-adapt 0

Last edited by Midzuki; 18th September 2010 at 14:48.
Midzuki is offline   Reply With Quote
Old 18th September 2010, 17:24   #89  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by Midzuki View Post
Does it make a difference if you set --bframes to 2 or to 1
Or if you use --b-adapt 0
Yes, it makes a difference.
--bframes 2 removes the backward-and-forward jerkiness. The playback is however still choppy in VLC. I didn't test on the standalone yet.
--bframes 1 is about the same
--b-adapt 0 does not make a difference.
Sharc is offline   Reply With Quote
Old 18th September 2010, 18:23   #90  |  Link
Midzuki
Unavailable
 
Midzuki's Avatar
 
Join Date: Mar 2009
Location: offline
Posts: 1,480
Thanks for the clarification.
Now, what about:

Code:
for n b-frames, --keyint = integer multiple of n+1 ;
N.B., 25 is not an integer multiple of 4, 3, or 2.

Quote:
--b-adapt 0 does not make a difference.
OK, but it won't hurt (much) if you use it, I guess.

Last edited by Midzuki; 18th September 2010 at 18:38.
Midzuki is offline   Reply With Quote
Old 18th September 2010, 23:06   #91  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by Midzuki View Post
Thanks for the clarification.
Now, what about:

Code:
for n b-frames, --keyint = integer multiple of n+1 ;
N.B., 25 is not an integer multiple of 4, 3, or 2.



OK, but it won't hurt (much) if you use it, I guess.
I normally use --bframes 3 and --keyint 24, which actually does comply with your proposal: 3+1=4 6x4=24. Similar for --bframes 2: 2+1=3 8x3=24. So --keyint 24 should be ok.

Removing --b-pyramid strict seems to help. No backward/forward jerkyness, but still choppy (means progressive, but not very fluent).

Last edited by Sharc; 18th September 2010 at 23:39.
Sharc is offline   Reply With Quote
Old 19th September 2010, 12:11   #92  |  Link
Ulf
Registered User
 
Join Date: Sep 2008
Location: Sweden
Posts: 66
Quote:
Originally Posted by kieranrk View Post
I'm not actually 100% sure. I always thought a GOP had to have actual frames in it so --keyint 50 would be correct for 720p25.
If --keyint refers to actual encoded frames, wouldn't --keyint 25 be correct for 720p25 even when applying soft telecine (for a 1s GOP)? Is any x264 programmer around to enlighten us?

Last edited by Ulf; 19th September 2010 at 12:24.
Ulf is offline   Reply With Quote
Old 19th September 2010, 12:19   #93  |  Link
nm
Registered User
 
Join Date: Mar 2005
Location: Finland
Posts: 2,641
Quote:
Originally Posted by Ulf View Post
Is any x264 programmers around to enlighten us?
IIRC, kieranrk is responsible for x264's pulldown support.
nm is offline   Reply With Quote
Old 19th September 2010, 20:45   #94  |  Link
mp3dom
Registered User
 
Join Date: Jul 2003
Location: Italy
Posts: 1,135
I have a question for people that have the BD specs on their hands:
I need to encode to BD with (relatively) low max bitrate (about 21 Mbps, but surely not over 24 Mbps) because I've a lot of lossless/PCM audio tracks to use. To gain a little, my idea is to encode as L4.0 to have the possibility to use 1 slice only. The specs says that L4.0 allow a maxrate of 24 Mbps which is perfectly fine for my job. The question is: the BD allows me with a L4.0 video to have a total BD bitrate of 48 Mbps (21 Mbps video + 27 Mbps audio) or with L4.0 my max BD bitrate is more limited?
mp3dom is offline   Reply With Quote
Old 19th September 2010, 21:17   #95  |  Link
shon3i
BluRay Maniac
 
shon3i's Avatar
 
Join Date: Dec 2005
Posts: 2,419
Video level bitrate restriction has nothing with overall bitrate which always stay to 48mbps if data rate is least 54mbps. Data rate dictates maximum allowed bitrate for disc. In normal case you always have 48mbps, and lowering video or audio max rate will not change that, only will make more space for other streams.

Last edited by shon3i; 19th September 2010 at 21:41.
shon3i is offline   Reply With Quote
Old 19th September 2010, 21:29   #96  |  Link
mp3dom
Registered User
 
Join Date: Jul 2003
Location: Italy
Posts: 1,135
Thank you very much!
mp3dom is offline   Reply With Quote
Old 21st September 2010, 20:18   #97  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
Quote:
Originally Posted by nm View Post
IIRC, kieranrk is responsible for x264's pulldown support.
His guides are here
(I still have no luck with --pulldown double and b-frames, but this is perhaps just me ....)
Sharc is offline   Reply With Quote
Old 21st September 2010, 20:31   #98  |  Link
shon3i
BluRay Maniac
 
shon3i's Avatar
 
Join Date: Dec 2005
Posts: 2,419
Quote:
Originally Posted by Sharc View Post
His guides are here
(I still have no luck with --pulldown double and b-frames, but this is perhaps just me ....)
What you use as BD muxer?

EDIT: btw max keyint must be on real fps not pulldowned, so for 720p25 is 25 not 50, 50 is valid for 2 sec GOP

Last edited by shon3i; 21st September 2010 at 20:41.
shon3i is offline   Reply With Quote
Old 21st September 2010, 21:54   #99  |  Link
Sharc
Registered User
 
Join Date: May 2006
Posts: 3,997
ok, I may have found my problem:
I have to delete '--b-adapt x' from the command line.
I tried
'--b-adapt 0' => jerky
'--b-adapt 1' => jerky
'--b-adapt 2' => jerky
removing '--b-adapt ... ' helped. Playback ok with MPC-HC and with VLC.
Now I still have to test with my standalone. I will report back.

And thanks shon3i for the clarification about the --keyint with pulldown.
Sharc is offline   Reply With Quote
Old 21st September 2010, 22:05   #100  |  Link
shon3i
BluRay Maniac
 
shon3i's Avatar
 
Join Date: Dec 2005
Posts: 2,419
@Sharc it's Tsmuxer problem. Obviously has a problem with pulldown streams.

I do a simple test, i encode video with pulldown, i muxed it with scenarist and tsmuxer. tsmuxer's stream show jerky playback, while scenarist play smooth.
shon3i is offline   Reply With Quote
Reply

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 18:39.


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