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. |
23rd October 2009, 20:46 | #44 | Link |
Registered User
Join Date: Nov 2002
Location: San Diego, CA
Posts: 936
|
Hi shon3i and detmek,
You shouldn't use --nal-hrd when targetting DivX Plus HD profile because this patch is still under development. The bitstreams will still play on DivX Plus devices. When this feature becomes integrated into the mainline builds we'll check its behavior and possibly make further recommendations. --aud is informational only and is optional. Hope that helps
__________________
DivX Plus Web Player 2.0 (MKV & AVI) (Embed generator) DivX H.264 Decoder with DXVA support Developer portal Last edited by DigitAl56K; 23rd October 2009 at 21:13. |
23rd October 2009, 20:49 | #45 | Link | ||
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
720p @ 59.94 fps : keyint 120 525i @ 29.97fps: keyint 60 (120 fields) 625i @ 25fps: keyint 50 (100 fields) 1080i @ 29.97fps: keyint 60 (120 fields) 1080i @ 25fps: keyint 50 (100 fields) Your made-up numbers: Quote:
|
||
23rd October 2009, 20:53 | #46 | Link |
BluRay Maniac
Join Date: Dec 2005
Posts: 2,419
|
You obviously not read table correctly, i clearly notice what is for 1 second GOP and 2 seconds GOP and depend from max bitrate.
long gop (2 sec) <=15mbps > short gop (1 sec) so read my post again http://forum.doom9.org/showthread.ph...75#post1337275 Last edited by shon3i; 23rd October 2009 at 20:56. |
23rd October 2009, 20:55 | #47 | Link | ||
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
I'm going to quote it again now: Quote:
Stop trolling, now. |
||
23rd October 2009, 22:47 | #49 | Link | |
Registered User
Join Date: Aug 2009
Posts: 463
|
Quote:
About BD and max --keyint: If I understand correctly, for maxbitrate <=15000kbs, max. keyint must be every 2 seconds or less. Now, 1080i50 (1080i/25) has 50 fields, or 25 frames. Since, --keyint is always expressed in number of frames (right?), 2 seconds GOP for 1080i50 (1080i/25) is 50 (25 frames * 2). For 15000< max. bitrate <=40000 kbs, GOP must be on every 1 second or less, so max. keyint must be 25 since 1080i50 has 25 frames per second. Or, I misunderstood something? Last edited by detmek; 23rd October 2009 at 23:29. |
|
24th October 2009, 00:16 | #50 | Link | ||
Registered User
Join Date: Mar 2005
Location: Finland
Posts: 2,641
|
Quote:
Quote:
|
||
24th October 2009, 08:23 | #51 | Link | |
Registered User
Join Date: Mar 2004
Posts: 51
|
Quote:
__________________
Jedes Herz ist eine revolutionäre Zelle Last edited by klinika; 24th October 2009 at 11:30. |
|
24th October 2009, 11:56 | #52 | Link |
Registered User
Join Date: Mar 2005
Location: Finland
Posts: 2,641
|
There are no widespread interlaced sources shot at 50 or 60 frames/s, only 25 or 30 frames/s. All the broadcast and SD/HD disc standards that define framerates only support interlaced video at 25 or 30 (actually 30000/1001) frames/s.
|
24th October 2009, 12:35 | #53 | Link |
Registered User
Join Date: Mar 2004
Posts: 51
|
Aye, it's just a bit surprising to me that in 1080iN notation the N can represent either field or frame rate. Unless there's an authoritative source, I believe it to be a bastardization of the ITU/EBU standard notation serving just to obfuscate it unnecessarily. Anyway, sorry for the OT, I went and asked for sources on wikipedia so I'll take it there.
__________________
Jedes Herz ist eine revolutionäre Zelle |
24th October 2009, 14:07 | #54 | Link |
BluRay Maniac
Join Date: Dec 2005
Posts: 2,419
|
Ok guys sorry for troll you are right, I do not know where my mind was I tested this combination last night and everyhing is as on table.
so here is: maxrate > 15mbps, 1 second GOP Progressive: 1080p 23.976, 24fps = --keyint 24 720p 23.976, 24fps = --keyint 24 720p 50fps = --keyint 50 720p 59.940fps = -- keyint 60 Interlaced: 1080i 29.970fps = --keyint 30 1080i 25fps = --keyint 25 480i 29.970fps = --keyint 30 576i 25fps = --keyint 25 maxrate <= 15mbps, 2 seconds GOP Progressive: 1080p 23.976, 24fps = --keyint 48 720p 23.976, 24fps = --keyint 48 720p 50fps = --keyint 100 720p 59.940fps = -- keyint 120 Interlaced: 1080i 29.970fps = --keyint 60 1080i 25fps = --keyint 50 480i 29.970fps = --keyint 60 576i 25fps = --keyint 50 |
24th October 2009, 14:57 | #56 | Link |
Registered User
Join Date: Mar 2005
Location: Finland
Posts: 2,641
|
No, unless you want to encode at a constant bitrate. VBV maxrate is set according to target device limitations. 1/2-pass bitrate is a user setting for average encoding bitrate, somewhere below the maximum rate.
|
24th October 2009, 23:25 | #57 | Link |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,752
|
Everyone follow after me:
480i30 is NTSC interlaced 576i25 is PAL interlaced 720p50 is PAL 720p 720p60 is NTSC 720p 1080p24 is film 1080p 1080p25 is PAL speedup 1080p film 1080i25 is PAL 1080i 1080i30 is NTSC 1080i These are your digital broadcast/disc formats in wide use, with non-ambiguous nomenclature. Of course, of those, we really only need 720p60 for sports/news/action stuff, and 1080p for movie/entertainment stuff. Everything else is a weaker alternative. |
24th October 2009, 23:47 | #59 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
NTSC with 29.97 interlaced/weaved frames per second equals 59.94 fields per second.
So it can be defined as either "i30" (referring to the number of interlaced frames per second) or as "i60" (referring to the fields per second). Both definitions are valid in a way, but we must a agree on one to avoid confusion. I tend to prefer the latter, as it better reflects the temporal resolution. Also it is highly questionable whether video with a resolution above 720x480 pixels should still be called "NTSC"
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
25th October 2009, 00:19 | #60 | Link | |
Registered User
Join Date: Mar 2006
Posts: 272
|
Quote:
what i get from that page http://tom.niko.users.sbb.rs/gop.jpg seems simple enough, and we are talking about trying to make it as easy as possible, so as to try and help everyone actually Clearly visualise the intent of the spec. is: it doesnt matter if there are, or are no widspread i50 or i60. the Only thing that matters is: that IF your bitrate is 15Mbit/s or less then you Can use a 2 second or greater? GOP IF you want to, but you dont have to, you can still use a 1 second GOP if you like within the standard. less is more here it seems yet again... to get a valid --keyint value you do the SIMPLE THING, if its Less than 15Mbit/s you simply take the FPS or 'frame rate value[Hz]' if you prefer calling it that , round it up* to the nearest int, and then double it. if its More than 15Mbit/s then you Do NOT double it, but rather just use the nearest rounded up int of the FPS/'frame rate value[Hz]'. so your i50 or i60 (or even p50 p60) would use a --keyint value of 100 and 120 If their bitrates were 15Mbit/s or less, or 50 and 60 if they were using faster bitrates! now we Might have a slight problem here, in that if your after Encoding a future SD/HD high speed camera footage to 15Mbit/s or less, with an FPS of something like >1200 fps at QVGA. lets say a fixed 10Mbit/s at an fps of 1200 ,then that means you would use a --keyint = 2400 , does --keyint allow for this high a value ? and were can we get some high quality and high speed footage to try this.... the reason i picked 1200 fps or greater is the fact the HW SOC can apparently capture and encode at these extremely high frame rates for some modes of operation, so if its not here yet, generally , it will sooner or later... http://www.imgtec.com/news/Release/index.asp?NewsID=440 *because the US etc cant be bothered to just use the simple and set standard BBC PAL int's of 24,25,50,100, and one day 200 TV standards.... Last edited by popper; 25th October 2009 at 00:36. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|