Log in

View Full Version : NeroDigital Profiles


bond
10th December 2004, 23:10
as some might already know Ahead defined for its NeroDigital MPEG-4 encoder private profiles, just as DivxNetworks did for its DivX5 codec, for being able to do private certifications without having to care about the profiles defined in the MPEG-4 standard

in contrary to the DivX5 profiles, there are no informations about the ND profiles publically available. thats why i did some little research on the ND reference samples, which can be found here (http://www.nerodigital.com/enu/Trailers.html)

by analysing the VOLs of these files i found the following:

HDTV profile
Indicated MPEG-4 Profile: Advanced Simple Profile @ Level 5
Video Object Type: 17
VBV: bit rate 24500, vbv buffer size 5981, vbv occupancy 505274
Framerate: 25fps fixed
Size: 1920x1072
not interlaced
no GMC
QPEL enabled
Complexity Estimation enabled

Cinema profile
Indicated MPEG-4 Profile: Advanced Simple Profile @ Level 5
Video Object Type: 17
VBV: bit rate 24500, vbv buffer size 5981, vbv occupancy 505274
Framerate: 25fps fixed
Size: 1280x720
not interlaced
no GMC
no QPEL
Complexity Estimation enabled

Standard profile
Indicated MPEG-4 Profile: Advanced Simple Profile @ Level 5
Video Object Type: 17
VBV: bit rate 10000, vbv buffer size 2441, vbv occupancy 206215
Framerate: 25fps fixed
Size: 720x576
not interlaced
no GMC
no QPEL
Complexity Estimation enabled

Portable profile
Indicated MPEG-4 Profile: Simple Profile @ Level 0
Video Object Type: 1
VBV: bit rate 5000, vbv buffer size 1221, vbv occupancy 103150
Framerate: 25fps fixed
Size: 352x288
not interlaced
no GMC
no QPEL
Complexity Estimation enabled

Mobile profile
Indicated MPEG-4 Profile: Simple Profile @ Level 0
Video Object Type: 1
VBV: bit rate 1000, vbv buffer size 244, vbv occupancy 20613
Framerate: 15fps fixed
Size: 176x144
not interlaced
no GMC
no QPEL
Complexity Estimation enabled


anyone knowing what Video Object Type and Complexity Estimation is about?

SeeMoreDigital
10th December 2004, 23:34
Thanks for posting this info buddy!


Cheers

akupenguin
10th December 2004, 23:56
Originally posted by bond
anyone knowing what Video Object Type and Complexity Estimation is about?

Video Object type is almost equivalent to Profile, except that some profiles allow multiple video objects at once, and then they can mix types. But for all anyone ever uses, 1 = Simple, 17 = Advanced Simple.

Complexity Estimation is a purely informative piece of metadata that may sit in each frame header, and estimates the amount of CPU-time needed to decode that frame. So a sufficiently smart decoder on the edge of realtime speed might decide to drop B-frames only when it would take too long to decode them.

bond
11th December 2004, 03:22
thx a lot :)

SeeMoreDigital
11th December 2004, 11:45
Are these "Profiles" for regular Mpeg4 (ie: non AVC) encoding?

I see GMC is "disabled" for all of them. And Qpel is "enabled" for HDTV!

And.... just to confirm. What are the "bit-rate" settings/speeds measured in?

And.... Will there be a different set of "Profiles" for Mpeg4/AVC encoding?


Cheers

Soulhunter
11th December 2004, 15:45
Hmm, why has the HDTV profile a resolution of 1920x1072 and not 1920x1080... :confused:


Bye

thegeby
11th December 2004, 15:57
@SMD: The trailers on the Nero Digital Website are non-AVC. There must already me a different set of profiles including HE-AAC as they are listed in the options of Recode.

@Soulhunter: 1080 is not divisible by 16.

SeeMoreDigital
11th December 2004, 16:10
Originally posted by Soulhunter
Hmm, why has the HDTV profile a resolution of 1920x1072 and not 1920x1080... :confused: As you know, most Mpeg4 encoding applications use fixed 16x16 pixel macroblock seeking (although 8x8 is also possibe):-

http://www.envivio.com/images/products/h264_features_matrix.jpg

Most people decide to go up to 1088 but 1072 is probably a better compromise, if you are intending to play back your encodes via some of the proposed/up-coming high-def stand-alone players.

When it comes to generating encodes using Mpeg4/AVC, 4x4 pixel macroblock seeking is permissible, so it should be possible to generate "cropped" encodes with frame sizes much closer to the source. Not to mention encodes from HD 1920x1080 Mpeg2 sources!


Cheers

temporance
11th December 2004, 16:23
Originally posted by SeeMoreDigital
Not to mention encodes from HD 1920x1080 Mpeg2 sources!
... which are actually encoded as 1920x1088 in MPEG-2. In case you were interested :)

ATSC decoder chips can handle 1920x1088 so it seems fair to assume that MPEG-4 decoders should be designed along these lines.