FFAStrans forum

Hi Steinar,

I apologize for all the upcoming questions, which I have quite a few now that we have basic transcoding working. I've attempted to attach my workflow, the forum didn't like the .xml extension, so I've renamed it to png. Hopefully that is ok. There are a few dangling nodes in our workflow that we were using for testing.

I've encountered 2 types of video which claim that %i_interlace% = 0.

This is;
1) a .dv file, which mediainfo says is BFF.
2) an MP4 file which mediainfo claims is BAFF.

Also another related question, I have a file which is incorrectly marked as progressive but is definitely interlace. Is there a way to detect these and correct the interlace flag?

Thanks
Mark

Just keep all the bug reports coming but I would prefer if you post it under the "Bug report" section.
The attachement is not there. Try renaming to .txt or .ini or just zip it.

Are you using the "A/V media"-decoder in your workflow that shows wrong field detection?

-steinar

I'm not sure if these are bugs or something that I'm doing wrong. The one thing I will complain about is the documentation
Hope the attachment worked this time.

Do you know how boring it is to write documentation when no one is paying you to do it!?!?

No, joke aside!
I see now that some of the media variables need a bit more documentation. And that goes especially for metadata like aspect ratios and interlacing that get lost when converting the clip to an AviSynth script. I will take a more carefull look at this for one of the upcoming releases.

The correct workaround is to store the "%i_interlace%" variable in another user variable PRIOR to the "A/V media"-decoder. Use the user variable to evaluate interlacing after the decoder.

-steinar

saving the interlace variable has resolved the interlace issue.
Also pixel aspect ratio gets clobbered after the AV Decoder.