Difference between two profiles

[supergirl123]

I'm using XviD 1.1. final and discovered two profiles: home theatre and cinema plus. What are the differences between these profiles? What should I use for a (quite old) standalone DivX-DVD player? :confused:

Greetings.

Steffi

[boombastic]

I'm not an expert but i guess the difference is in the max bitrate allowed:4000 kbps for Home Theatre and 6000 kbps for Cinema Plus.You can just try and play a file encoded with cinema plus;if your standalone player hungs up in certain point you'd better to stick with Home Theatre.

[celtic_druid]

Actually from recollection, the max bitrate is the same. If you want 6000, you need to use a build with my MTK profiles. Cenema Pluss allows qpel and CQM's. So it is basically the same as my MTK profile, except it is also flagged as PROFILE_EXTRA. So still enforces packed bitstream, no bframes when interlaced, etc.

[supergirl123]

As far as I saw in home theatre quarter pixel and quantization type are disabled. So, if you leave quarter pixel disabled and the quantization type by default at H.263 the profiles are the same. Is that right?

[Lil' Jer]

As far as I saw in home theatre quarter pixel and quantization type are disabled. So, if you leave quarter pixel disabled and the quantization type by default at H.263 the profiles are the same. Is that right?

Sure, and unrestricted would be the same if you didn't use all the features blocked out by those profiles. What's your point?

[supergirl123]

Sorry, I'm a Newbie in XviD and there is so much to adjust. So for me the profiles are very helpful. But you can't get much information about them in Google. I only wanted to know if I understand the profiles correctly. That's all. :)

[kotrtim]

Some player's manual will explain what they support, like quarter pixel, GMC, and the fourCC code. It's good to refer to your manual

Noamally these are the only restriction factors
1. resolution/frame rate
2. b-frames
3. Quant. matrix
4. Quater pixel
5. GMC
6. Packed bitstream
7. Maximum Bitrate
8. FourCC

8 is what I could think, if 2 to 6 is disabled, I'm pretty sure it is compatible with most DivX player

Other the 8 i could thhink off, you can tweak whatever you like

[supergirl123]

My player is from asia. The manual ... Well, forget it. It's not very helpful. From my experience I know that the player doesn't support quarter pixel and GMC. With DivX b-fames are no problem, but with XviD I already had some trouble. That's why I want to know so much about profiles.

[xyloy]

With DivX b-fames are no problem, but with XviD I already had some trouble.
Just use the Home Theatre NTSC profile with 1 Max consecutive B-VOP:
http://membres.lycos.fr/xcomcmdr/XviD(HomeTheatre)2.png
You can use also thoses settings for a better motion estimation(=better quality than DivX, but slower encoding compared with "normal" XviD settings):
http://membres.lycos.fr/xcomcmdr/XviD(HomeTheatre)3.png
http://membres.lycos.fr/xcomcmdr/XviD(HomeTheatre)4.png
(be careful, the maximum I-frame interval in this screenshot is only for a source with 25 frames per second)
http://membres.lycos.fr/xcomcmdr/XviD(HomeTheatre)5.png
;)

[foxyshadis]

MPEG matrix + quant 1 do not go together. geez, set them to 2/31.

Oh, and in case you want to use those settings but want to know what to tweak, lowering the VHQ will give you more speed for the least quality loss (unless you lower it below 1).

Alternately, just see Teeg's xvid profile discussion, he goes very in-depth about different quality and speed modes.

[xyloy]

geez, set them to 2/31.
Theses are the default settings...

[foxyshadis]

They're only default because enough people complained about undersizing without understanding that they were saturating the codec. q2 min was the default for a long time and is still recommended. Only certain custom matrices can take advantage of q1.

[xyloy]

thanks for the info. That's why I had oversizing problems. :P
(I am aware of the sticky about this kind of problem, but I believed that default settings would be... I don't know.. suited for most situations, not for some ppl... <_< But I used x264 instead so the problem was no more :D )