accept to 's Forum. THE in-place to be for everyone interested in DVD conversion.
Before you go away posting please construe the. By posting to this forum you accept to continue by the rules.
Good day all. This is a bit of a recycle of a problem I had about 9 months ago but stepped away from. I am in the process of rendering VC-1 evaluate clips for some validation and I am finding that when I get the clips out using Windows Media Encoder and the newest version of WMP 11 that my clips are not accurate according to the VC-1 spec. I am using page 433 from the "Final Draft Standard 421M" for VC-1 for a baseline of clips to render. Here is an example: for a cut that is AP@L2 I should be able to render a cut at 720p-1280x720 and 30fps at a maximum bitrate of 20Mb/s. However when I render this in WME9 with WM SDK 11 loaded this combination of settings generates a clip that fills the be adrift 1 Attribute metadata field with AP@L3 and using the Tektronix software stream analyzer also reports back AP Level 3. What am I missing here? Since the change comes from MS and there is a SMPTE spec to change to shouldn't circumscribe created with the SDK be compliant?I'm attaching a zip file that has some register properties of the WM version and of the register I created. Thanks.
I'm experimenting with the WMCmd vbs now and I have found the communicate vector controls. It is the parameter called -v_msrange. Since I have not been calling this parameter at all I believe my files are using the default which is +63.75/-64 H. +31.75/32 V which is still well below the threshold for the compose/aim I was creating. I've brought this up with the folks who provided our video analyzer and they undergo even open that "official" conformance bitstreams are returning incorrect values. AP@L2 cut SA20020 vc1 and SA20023 vc1 should be aim 2 but the returned values in the header are level 3. How is it that change surface some of the conformance streams are wrong?Should I just do by the header information as desire as my parameters are within spec? Mpeg2 and h.264 compose/aim combinations don't seem to create these discrepancies. Here's move of the header on SA20023 vc1:Standard: VC-1. Advanced Profile / Level 3close in coat: 1280x720Filesize: 38135 kBytes(0x00000000,7) 0000 0000 0000 0000 0000 0001 ---- ---- : STARTCODE_affix(0x00000000,7) [VSQ] startcode_prefix = '000000000000000000000001'(0x00000003,7) 0000 1111 ---- ---- ---- ---- ---- ---- : STARTCODE_SUFFIX(0x00000003,7) [VSQ] startcode_suffix = 0xf: Sequence Header(0x00000004,7) 11-- ---- ---- ---- ---- ---- ---- ---- : PROFILE(0x00000004,7) [VSQ] compose = 3: Advanced Profile(0x00000004,5) 011- ---- ---- ---- ---- ---- ---- ---- : aim(0x00000004,5) [VSQ] aim = '011': Level 3(0x00000004,2) 01-- ---- ---- ---- ---- ---- ---- ---- : CHROMAFORMAT(0x00000004,2) [VSQ] chromaformat = 1: Subsampling is 4:2:0(0x00000004,0) 111- ---- ---- ---- ---- ---- ---- ---- : FRMRTQ_POSTPROC(0x00000004,0) [VSQ] frmrtq_postproc = 7: Quantised close in rate for post processing is 30 fps(0x00000005,5) 1111 1--- ---- ---- ---- ---- ---- ---- : BITRQ_POSTPROC(0x00000005,5) [VSQ] bitrq_postproc = 31: Quantised bit rate for post processing is 2016 kbps or higher(0x00000005,0) 0--- ---- ---- ---- ---- ---- ---- ---- : POSTPROCFLAG(0x00000005,0) [VSQ] postprocflag = 0: Frame based affix processing is NOT used(0x00000006,7) 0010 0111 1111 ---- ---- ---- ---- ---- : MAX_CODED_WIDTH(0x00000006,7) [VSQ] max_coded_width = 639: Maximum horizontal conceive of size is 1280 samples(0x00000007,3) 0001 0110 0111 ---- ---- ---- ---- ---- : MAX_CODED_HEIGHT(0x00000007,3) [VSQ] max_coded_height = 359: Maximum vertical picture size is 720 samples(0x00000009,7) 1--- ---- ---- ---- ---- ---- ---- ---- : PULLDOWN(0x00000009,7) [VSQ] pulldown = 1: Interlace syntax element flags RPTFRM or TFF and RFF are show in picture headers(0x00000009,6) 0--- ---- ---- ---- ---- ---- ---- ---- : INTERLACE(0x00000009,6) [VSQ] distort = 0: Displayed content is progressive(0x00000009,5) 0--- ---- ---- ---- ---- ---- ---- ---- : TFCNTRFLAG(0x00000009,5) [VSQ] tfcntrflag = 0: Temporal Reference Frame answer (TFCNTR) is NOT show in picture headers
Forex Groups - Tips on Trading
Related article:
http://forum.doom9.org/showthread.php?t=132229
comments | Add comment | Report as Spam
|