Mainconcept MBAFF problem

[dattrax]

I'm using Mainconcept 2.1 to encode some interlaced material. I was orginally selecting 'interlacing' and setting the field order (which worked fine output to my 1080i display).

I then decided to try MBAFF as the encoding is supposed to be more efficient. Setting to MBAFF causes field order problems when I display.

As a quick experiment I encoded the same material as MBAFF in TFF and in BFF and dumped the output using a demo of elecard streameye and in both cases everything was identical.

The question is what happens in MBAFF to identify the display field order?

Jim

[Sergey A. Sablin]

I'm using Mainconcept 2.1 to encode some interlaced material. I was orginally selecting 'interlacing' and setting the field order (which worked fine output to my 1080i display).

I then decided to try MBAFF as the encoding is supposed to be more efficient. Setting to MBAFF causes field order problems when I display.

As a quick experiment I encoded the same material as MBAFF in TFF and in BFF and dumped the output using a demo of elecard streameye and in both cases everything was identical.

The question is what happens in MBAFF to identify the display field order?

Jim

at this time there is no way to specify field order for MBAFF through this application. All frames are marked as frames - not top_bottom and bottom_top.
there is only one way right now - to use pulldown encoding (ie 24->30 or 23.976->29.97), but it is a bit tricky.

[dattrax]

Thanks,

Yes you are correct, the SEI header for PIC_TIMING is always marked as frame (value 0) whereas it should be

3 top field, bottom field, in that order
4 bottom field, top field, in that order

depending on whether you selected top field first or bottom field first.

I'm going to mail them as this is fundamentally broken

Cheers

Jim

[bond]

I'm going to mail them as this is fundamentally brokenSergey A. Sablin is a developer of elecard/mainconcept ;)

[dattrax]

Its only a 4bit field, so hopefully it wont be too difficult. I'd already mailed their support before I found out that Sergey A. Sablin is a developer, so I guess it wont harm things if I push for a fix from both directions.

I thought about writing something to rewrite the headers but I'll wait until I get an idea of the length of time till a fix.

Jim

[Sergey A. Sablin]

Sergey A. Sablin is a developer of elecard/mainconcept ;)

now elecard only. so I already have no deal with encoder, so I can't help there. I can just say what's incorrect.

[Sergey A. Sablin]

Its only a 4bit field, so hopefully it wont be too difficult. I'd already mailed their support before I found out that Sergey A. Sablin is a developer, so I guess it wont harm things if I push for a fix from both directions.

I thought about writing something to rewrite the headers but I'll wait until I get an idea of the length of time till a fix.

Jim

you didn't get it - everything is working, but there is no way to specify it through application. So it is not a bug - it is lack of user interface.
Try to use BluRay preset for encoding and specify MBAFF + field order. I think this should help as needed parameter hardcoded in BluRay preset.